Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@inawhile ++ for crayons, but age has nothing to do with seniority..
IMO even switching codebase (new job, new project) will knock your seniority rank a bit, but keep in mind, seniors with proper mileage will have a lot less of a struggle to grasp the new environment & how it all clicks together than the ones that just earned that rank.. -
@sladuled and once you have a few Lang’s/environments under your belt, facing a new lang/environment should be a setback of days or weeks, not months or years.
The truth, whole truth, and nothing but there truth.
You must be really senior to pull this off 🤣🤣
Yes, senior developers get stuck just as much as junior developers do, the difference is that they get stuck in places that junior developers can’t even access. That is partially because senior developers are expected to do so much more than just simple coding, they need to also grasp and untangle client requirements, communicate clearly and thoughtfully with the team, be some sort of guiding/mentoring/leading figure, make sweeping architectural decisions, and so on and so forth.
A junior developer is struggling with making relevant columns of a table a nice shade of purple. A senior developer is struggling with making sure that implementing new client requirements will not have a destructive impact on the current infrastructure, there will be no regressions elsewhere in the system, tries to pinpoint what prior assumptions the new stuff breaks (it inevitably does), and how to reconcile everything.
rant
senior developer