> <i>Welcome to the software development world" only to find out they've been working as a software developer for over a year and a half already.</i><p>Ugh, you think 18 months is a long time? Programming is hard, just the technical part takes a lot of reps, but navigating the long term implications and social/business interfaces are what make the difference between an effective tech lead and an NNPP.<p>Here’s a tip: stop worrying about labels. Spend a decade obsessively honing your craft. Think from first principles. Ask difficult questions. Move around and find the smartest programmers you can to learn from. Confidence comes from hard-won abilities, not playing mind games with yourself about titles.
Alright this is an OK-ish motivational piece to never let anyone put you in a box I guess...<p>> In fact, I was just a step below architect in a quarter-billion dollar organization only 4 months after graduating from university.<p>Oh, come on, Kent. Really? Can we qualify this guy's blog as spam yet?
I would also add: Don’t be an expert beginner. At some point you have to focus on solving real business problems as opposed to mastery of tool usage or configuration.
I feel this article is not very good. It focuses too much on externalities.<p>One thing that I often find is that there is too much self doubt and impostor syndrome in the modern generation of kids and I think that is warranted.<p>A big part of why they feel that way is because they haven't really thought how a computer works, haven't build large enough systems, haven't written enough code to understand why Uncle Bob and Clean Code are bad solutions.<p>Once they start looking at hard skills instead of managing up or other things at the office, that's when I feel they will think and act like a senior.<p>There is no way of shortcutting it. You have to pay your dues in terms of understanding why certain code is bad and certain code is good and that only comes with writing largish systems and testing your theories. Also build stuff outside of web dev.<p>If you feel like a junior or have impostor syndrome, it might well be because you are one.
This is just like, my opinion, man but I think titles are just food for our egos. I think developers should focus on two things: 1) doing work that you enjoy. 2) take a good long hard honest look at yourself and determine your value, then find an employer that agrees.<p>The only advice from the article I liked was:<p>> Even if it's just "hey, can I come sit in on that meeting?" Take notes for yourself of anything you're unfamiliar with and ask about those things later.<p>I love sitting in on meetings just to take notes. Recently some Sr Developers and our DBA set up a weekly meeting to discuss overhauling our database schema and I asked to sit in. Even though most of what I heard aligned with what I already knew I still got a lot of value in just listening to other people's opinions. The DBA was a fountain of knowledge when it came to the nuances of using SQL Server.
> I felt like I had to leave the company I was with to get up to the level I wanted to be with. I probably could have managed it with the company I was already with if I had been more patient.<p>Ah there it is. Nothing is more junior than seeking this advice.
not being junior doesn't mean being updated with any new, fast, shiny technology. Means having the right attitude toward the job and the matter. That, only experience gives. One year and a half, depending on the person, might be enough, but not for all.
Sometimes you get to be a junior in a company that uses A,B,C but then you upgrade, move to another company, but they say that to be a senior, you're lacking your expertise in D,E,F. What then? Just jump 'til it fits?