It's quite hard work with developers that are founding members, usually, they aren't the best technically, and even stupid things that they do are praised by the CEO/CTO, my way to solve this problem in one of the companies that I worked before was delegate less technical tasks to them like be the team scrum master or tests task.
I couldn't agree with you more. But just to make sure that we're on the same page, I wanna make clear that when I talk about "older" programmers, I'm talking about far more people than just founding members.
There's a whole other post here. But I've found most founding members to be a complete PITA. Their legacy solutions are cobbled together and based upon whatever tech they learned 20 years ago. But if you say even the slightest thing to imply that the legacy solution is somehow less-than-perfect, they get needlessly defensive. In other words, their crappy solution becomes their "baby".
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.
It's quite hard work with developers that are founding members, usually, they aren't the best technically, and even stupid things that they do are praised by the CEO/CTO, my way to solve this problem in one of the companies that I worked before was delegate less technical tasks to them like be the team scrum master or tests task.
I couldn't agree with you more. But just to make sure that we're on the same page, I wanna make clear that when I talk about "older" programmers, I'm talking about far more people than just founding members.
There's a whole other post here. But I've found most founding members to be a complete PITA. Their legacy solutions are cobbled together and based upon whatever tech they learned 20 years ago. But if you say even the slightest thing to imply that the legacy solution is somehow less-than-perfect, they get needlessly defensive. In other words, their crappy solution becomes their "baby".