3 ms·
> That approach works much better for more experienced senior devs. I don't think we're talking about junior developers here since the counter-example is a Cel
by diggan 2y ago
> That approach works much better for more experienced senior devs.
I don't think we're talking about junior developers here since the counter-example is a Cello player in orchestras and symphonies, those have to be considered "senior" as well no?
> I've been in it for around 15 years and feel pretty comfortable picking up a new language and jumping around between stack, frontend/back end/db, and languages.
Yeah, but that's comparing it to a musician switching instrument, instead of just a musician switching the place they play. The comparison then would be that a desktop app programmer does a todo app, or they do a calendar app. Both involving still the same instrument/area of programming, but different environments of sorts.
- _heimdall 2y agoI do agree with your points here, but they don't align with the original quote I was responding to. > But programming is exactly the same. A programmer knows how to program. This would be akin to saying a cello player knows how to orchestra, and changing instruments wouldn't be a problem. Software development in the frontend, backend, database, etc are very different skills especially when at a non-junior level. Expecting someone to jump between them without much to any training is like expecting a cellist to jump over to the violin.