Re:Ask HN: Where to learn about driving engineering change i...
by codingdave on Thursday August 29, 2019 @10:39AM
(#20829870)
> I’m talking about a software company with dozens or even hundreds of engineers, with large amounts of technical debt, that has a giant, monolithic codebase that’s highly-coupled and poorly tested, a release process that is slow and brittle.
I think you may have a flawed view of large software organizations. While I'm sure some companies exist that match the above description, I've more typically seen numerous siloed teams, with their own codebases, with both loose and tight coupling to other teams, with a variety of processes, and therefore a variety of quality around the teams.
So it is not as simple as just picking a universal pain point and transitioning to a new process. It is about understanding the drivers and history that got each team to where they are, picking apart which of those drivers is still relevant, and looking for shared pain points between teams that are now open to change due to changes in the business since things were set up.
Because of this, I'd focus less on the technical side, and more on communications and business, as those are the rabbit holes you'll need to go down to build consensus from multiple teams to mutually move to a better place.
I think you may have a flawed view of large software organizations. While I'm sure some companies exist that match the above description, I've more typically seen numerous siloed teams, with their own codebases, with both loose and tight coupling to other teams, with a variety of processes, and therefore a variety of quality around the teams.
So it is not as simple as just picking a universal pain point and transitioning to a new process. It is about understanding the drivers and history that got each team to where they are, picking apart which of those drivers is still relevant, and looking for shared pain points between teams that are now open to change due to changes in the business since things were set up.
Because of this, I'd focus less on the technical side, and more on communications and business, as those are the rabbit holes you'll need to go down to build consensus from multiple teams to mutually move to a better place.