4 ms·
I see it like the most abstract up the ladder you get, the more senior you are. Anyone can fix a button's css. Not anyone can refactor big parts of a codebase
by tough 3y ago
I see it like the most abstract up the ladder you get, the more senior you are.
Anyone can fix a button's css.
Not anyone can refactor big parts of a codebase into something better, or help them create from scratch in a cohesive, modular, future-proof way.
Every time I get into a new job I get a various degrees of this.
The more business-context you have, the better you can solve business requirements with tech, the better tech toolset you have available, the better choice you can make on what solution to use or not to use to such problems.
True seniority means understanding how all the system works, regardless of getting into the grunt work of each of the steps, but being able to do so and understand it at the lower level too if/when needed.
It's a hard act.
- flagrant_taco 3y agoOne caveat I have is that companies are generally terrible at recognizing senior+ level independent contributors (ICs). Many companies don't even have a career path defined for this. I have worked with some of those individuals and they really are worth every bit as much as, if not more than, a systems-level thinker that enjoys mapping business needs to technical solutions. Most large tech companies I've seen promote standout ICs to either architect or manager, assuming that the skillset and interest largely transfers. I've seen this blow up many times, it's painful to watch and I really hate it for everyone involved.