Mark DiAntonio

This depends on the size, situation, and maturity of the company that you're working with. You need to tailor your approach accordingly. In general, make sure you measure team efficiency, product quality, and common velocity metrics. Start a common language around scoring user pain. If its important, measure it and set a goal against improving it. You'll be amazing how rapidly you find your balance then.

Read what you can from tried and true sources like Martin Fowler, but the best way to learn is to build with others. Spend time in their pull requests and ask questions. Go beyond things a linter or an autoformatter can do for you.

I'm not sure a framework or a library improves your problem-solving skills. A framework is a tool or a set of tools to accomplish a job. As you build with various frameworks, pay attention to patterns that they teach. Ask yourself why they are built the way they are, go through and read the code, don't just implement the functions.

Don't get too exotic. If you're working on iOS, you're going to be using xCode; for android Android Studio. There are a bevy of other options out there for other languages or frameworks, but I'd prefer VS Code for its flexibility and extensibility

This world is going to change quite a bit with AI breaking new ground every day, but the soup-de-jour is Figma. It allows for easy collaboration for remote teams and is improving its toolset for integrating the needs of the development team alongside product design.

I'd suggest using the lightest possible tool for Project Management. A lot of teams can get away with just a whiteboard or a Trello. If its more of a mature project or a larger group, I'd look at JIRA which is also popular in the QA world for bug tracking. This allows you to manage the variety of tasks for your devs in one spot. Word of warning though, JIRA Admin and setup isn't always intuitive so you could waste time managing your work instead of doing it.