3 ms·
>The general success ingredient is putting a small team of veterans on making the new system. I don't disagree with this approach. But one thing I find is: S
by duxup 3y ago
>The general success ingredient is putting a small team of veterans on making the new system.
I don't disagree with this approach. But one thing I find is:
Sometimes those veteran teams are heavily invested in existing concepts, tools, and approaches. It makes sense, they have seen these things work and they're proven to some extent.
But it's always not the best choice.... and while the veteran teams often start these projects they often aren't the people to "finish" them as they get pulled away. And it is oh so easy to start projects and make decisions if you never see the outcome / have to deal with the fallout.
- HumblyTossed 3y ago> But it's always not the best choice.... I think it comes down to the personality of the veteran. If they're the "i've seen some shit, so I'll 'architect' the fuck out of this to handle any type of change" type veterans, then it's likely to fail. But if they take their knowledge of how the system has grown over time and architect to handle the types of changes they've seen, then there is likely a greater chance of success. Personally, I think a having some junior and mid-level engineers on the rewrite is good because it's a good way to see how the system is all put together (as opposed to just one area) and they'll be able to have conversations with the veterans about how the system has evolved as it grew and that is valuable information.
- liquidpele 3y agoMeh. I’ve met brilliant juniors and worthless veterans. I think it’s more important to recognize brilliance in people… That spark of hard work combined with vision and creativity.
- willvarfar 3y agoYeap, good point, tenure != expertise. If I could edit the post I'd insert a qualifying "expert" before veteran, where the expert veteran meets my definition of the 10x developer :D Any veterans who aren't gonna get the project done quickly _and_ properly aren't the kind of veterans I have in mind.
- mjr00 3y ago> Sometimes those veteran teams are heavily invested in existing concepts, tools, and approaches. It makes sense, they have seen these things work and they're proven to some extent. This is very closely related to why these veteran teams end up successful. Existing concepts, tools and approaches should be the default; if your company uses Python with MySQL you better have a really, really good reason for your new project to use Rust and CockroachDB. > while the veteran teams often start these projects they often aren't the people to "finish" them as they get pulled away. I disagree with this. The veterans are veterans because they've already spent time maintaining the existing systems. They've handled oncall, major bugs, and seen all kinds of stupid shit that happens with software. They'll get pulled onto other projects eventually, sure, but they have a higher chance of getting a system into production in front of users, IMO.
- duxup 3y agoI disagree. There's no magic to being on call that means you understand something well enough. That's simply not automatic. Following through with something from start to "finish" is far far more valuable than fixing one off bugs and then doing something else, and then something else. If anything I think it can lead to a lot of poor assumptions based on very skewed experience.
- Aeolun 3y agoI think the implication is they’ve seen all problems before and can engineer their new system to solve them.
- mjr00 3y agoDepends on the nature of your oncall. If your oncall is just following documented restart procedures when your app gets stuck, you won't learn much. If your oncall involves deep investigation into your system and how it interacts with other components (services, databases) etc you'll learn a lot. per some sibling comments though, years of experience != veteran, to be clear. There's certainly people who have been working for 10+ years, sometimes even at the same company, and don't really understand what they're working on.
- 3y ago