4 ms·
I think it's a result of how inexperienced the majority of devs are. At 10 years in, you're more effective doing architecture and dealing with high-level stuff
by claudiulodro 5y ago
I think it's a result of how inexperienced the majority of devs are. At 10 years in, you're more effective doing architecture and dealing with high-level stuff to set up newer developers for success, but if everyone you worked with had 10+ years of experience they couldn't all be architects! :)
- maxdoop 5y agoThis does seem to fit what I've seen. I often have this weird imposter syndrome, where I sit on calls for 2 weeks and create some detailed end-to-end design. I then take that design and present it to a a team of engineers are are tasked with actually implementing it. It feels strange to be doing that, and not having a hand in the implementation (i.e. coding). But then, those same engineers are the ones who come to me for the high-level questions.