But there is also the case when one starts looking beyond just coding and thinking 'big picture' enough to see that being a 'senior developer' is not the way to go either and there other paths beyond just being another engineer.
Coding for 20 years | Working for startups for 10 years | Team leader and mentor | More information about me: https://thevaluable.dev/page/about/
Twitter: @Cneude_Matthieu
Agree on that. At the end of the day, 'senior developers' are just a part of a bigger system, the company they work with. On top, they're the last part (they "produce" for most people, even if what we do is mostly design). Which means that if anything goes wrong before the implementation, the developers will get the consequences in the face.
What kind of consequences? Complexity impossible to deal with (sometimes, most complexity comes from the business), micro-management, bad hiring process, bossy managers, under estimation of complexity and entropy, short deadlines without possiblity to change the scope, agile and scrum used to pressure the developers... The list goes on.
Additionally, in my experience, people in a company don't listen to developers, because they're hired to do (again, 'to produce'), not to advise.
Being independent can solve some of these problems I guess.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
But there is also the case when one starts looking beyond just coding and thinking 'big picture' enough to see that being a 'senior developer' is not the way to go either and there other paths beyond just being another engineer.
Agree on that. At the end of the day, 'senior developers' are just a part of a bigger system, the company they work with. On top, they're the last part (they "produce" for most people, even if what we do is mostly design). Which means that if anything goes wrong before the implementation, the developers will get the consequences in the face.
What kind of consequences? Complexity impossible to deal with (sometimes, most complexity comes from the business), micro-management, bad hiring process, bossy managers, under estimation of complexity and entropy, short deadlines without possiblity to change the scope, agile and scrum used to pressure the developers... The list goes on.
Additionally, in my experience, people in a company don't listen to developers, because they're hired to do (again, 'to produce'), not to advise.
Being independent can solve some of these problems I guess.