21–27 of 27 posts
If you are a good junior you already know most of the things you will know as a senior, the difference is you don't know that you know.
> 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. 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. Here’s a tip: stop worry…
Also, there is a real risk to learning if you "stop being a junior". Namely, the posers don't raise their hand and ask for help when they hit a wall, waste a ton of time drowning with things that senior engineers can figure out in 10 minutes, and are scared of learning from senior teammates as it requires them to be vulnerable in front of them. The ones faking it tend to be insecure and not fully dedicated to their craft, but their title first.
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. The only advice from the article I liked was: > Even if it's just "hey, can I come sit in on that meeting?" Take notes for yourself of anything you're…
> This is just like, my opinion, man but I think titles are just food for our egos. Yes, but that doesn’t mean that we should ignore the importance of what the title signifies. Titles may not be so important to you, but they are to others and they also help signify how others should treat you. If you were a very senior engineer, I would expect that you act very differently than a junior engineer, and the easiest way…
Alright this is an OK-ish motivational piece to never let anyone put you in a box I guess... > In fact, I was just a step below architect in a quarter-billion dollar organization only 4 months after graduating from university. Oh, come on, Kent. Really? Can we qualify this guy's blog as spam yet?
> 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. 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. Here’s a tip: stop worry…
Seriously, that jumped out at me. You do not know anything after a year and a half. You are a junior developer. Nobody is that special. Also, there is a real risk to learning if you "stop being a junior". Namely, the posers don't raise their hand and ask for help when they hit a wall, waste a ton of time drowning with things that senior engineers can figure out in 10 minutes, and are scared of learning from senior te…
> 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. 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. Here’s a tip: stop worry…
I feel this article is not very good. It focuses too much on externalities. 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. 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…
Why are uncle Bob and clean code bad solutions?