3 ms·
It pretty much is "when you feel comfortable and are productive working alone". However, there's a lot to unpack in that statement. In particular, it requires
by nostrademons 12y ago
It pretty much is "when you feel comfortable and are productive working alone". However, there's a lot to unpack in that statement. In particular, it requires being able to understand trade-offs, knowing what to do when there isn't a clear "right" way to do things, and understanding that often the "right" way is situationally dependent.
If you're still focusing on the "how?" and "what?" of programming, you're still junior. If you're starting to look more into the "why?", "who?", and "when?", then that's an indication of a transition to a more senior role.
- cblock811 12y agoThanks for the feedback. Part of why I say that I'll be a junior for a while is that I need to pick up a lot of best practices and general intuition on projects. Learning alone sort of blocked me off from that experience early on. Just gotta put in the time.