>I primarily work in elixir but have side-project aspirations in JS and react. I'm scared now, because my skills seem to be growing slowly at work but otherwise

>I primarily work in elixir but have side-project aspirations in JS and react. I'm scared now, because my skills seem to be growing slowly at work but otherwise be stuck in "tutorial hell" as is sometimes discussed elsewhere on HN. If I were in your situation, I'd drop the side projects and totally commit to the work codebase and own it all, build tooling for the team, add in whatever is missing: from issue templates to tests, from docs to monitoring, from automatic deployments to refactoring. Then think about the whole product, from design to the value it creates. Think of how you can build that organization and make it a success. Hiring, operating. Divided attention seldom gets you anywhere, so focusing on what will make that startup a success, whatever that is, is the way to go in my opinion. You'll get good faster and, ironically, you'll have more time for other activities. But the other way isn't that effective: being spread too thin, not up to the task at work, and wanting to improve at something else. Being good at things compounds and frees up time to expand and explore more meta things. It's hard to be on multiple fronts, especially with your predicament. Sequential gets things done. You'll also be given more latitude in your job because you deliver and add value. Yes, this may be terrible career advice because one might argue that side projects are good for a résumé and you want to start a company. I'd argue that being distracted is harming both your career and your prospects of starting a company. I'd say commit. Commit to doing a great job with the company you're in right now. Climbing up the ladder, as you say, will be a consequence if you're at a good company.