I'm a junior dev working for freelance clients and working on my own projects. I've noticed that in the recent couple of months, I've not progressed as well as I hoped I would.<p>Yes, I gained experience and whenever I'm going to work with framework x again, I'll be a lot quicker. However, I don't have full insight in the tradeoffs that I'm making when chosing a certain architecture for example. I'll just code what seems logical in my head, and build further upon that.<p>I'm mostly coding in OO languages. Should I focus on programming concepts? Should I dive deeper into API methods?<p>Also, Since I'm able to 'build', there's the fact that spending more time on figuring out what approach is best, I'm developing on a lower pace.
If you want to grow as a developer the best thing to learn is normally always the same.<p>Data Structures.<p>Nothing will help you more in interviews, day-to-day dev work, general problem solving, and even application planning. The goal is eventually to transition your mindset into thinking about structures holding your data, and how they act, and interact. Once you do this the optimal architecture, and what you need to write as code becomes clear as day (really regardless of the language).
Just to counter everyone who says "learn another language like Haskell", I completely disagree.<p>You're at the point where you know some language and OOP at a decent level. You now need to invest time learning things like data structures and algorithms that are APPLICABLE to your work.<p>Keep adding incremental knowledge, but make sure it is having a direct benefit to your work at all times.<p>The "learning paradox" of having to master languages repeatedly is a waste of time at a junior level. You'll continuously invest in a new language without ever finding it applicable (eg. "learn java, learn JS, learn CSS/HTML, learn python, learn ruby, learn haskell, learn rust, then learn x-framework for each language, learn y-framework cause someone on the internet said x-framework is too bloated, learn this, learn that ...").<p>As your questions on line 3 asks, I say invest in the higher-level concepts that work across languages. Focus on a domain (some language, 1 or 2 frameworks, a DB) and stick with it.<p>And, as others have said, find a mentor. If you want to keep freelancing, you'll find a mentor at a meetup. You will definitely gain a lot from experience over a book/tutorial in certain situations.
> I'm a solo junior dev, what should i focus on?<p>Beyond technologies-- Focus on building a solid consulting practice, client management, how to prospect & pitch new business. Recommend reading Alan Weiss, <a href="http://www.goodreads.com/book/show/260218.Million_Dollar_Consulting" rel="nofollow">http://www.goodreads.com/book/show/260218.Million_Dollar_Con...</a>
Depends on your planned career path- do you want to run a business, or be a developing badass? Few can do both extremely well-
If its development, move towards learning more about Software architecture, including SOLID principles, Patterns, best practices(as it pertains to Computer Science as a whole, not a particular technology or framework). While doing this, blog about it so your current and future clients can see your humble nature (rare for up-and-coming- to experienced developers) and progress.
More importantly, if you think about doing a personal project or have an idea for an app- don't focus on making money, focus on the knowledge and experience gained through the work itself.
I think the best way to learn to be a better programmer in your position is to find a more stable job with a good team of people. Learn from other people's experiences and mistakes. Working as a freelancer early doesn't have many advantages if you want to build a career, in my opinion.<p>Other than that - Keep trying different things. Go deeper with the frameworks and libraries you use to understand why do they work the way they do. Read about things that are interesting to you and you have some use for. When you have a problem, don't just "fix" it, understand exactly where, why and when it's happening.
You need a mentor.<p>Freelancing as a junior dev is not a good move. Find a full time position somewhere that will train you and give you access to more experienced developers.
Get involved in the open source community. You will be able to see how bigger systems are built. Right now you know what you know and you know what you don't know. But the gaping hole is that you don't know what you don't know! Unfortunately working solo can be a bit of a trap in that regard.