3 ms·
I honestly don't really like the "let's slow down" approach. It's hard for me to buy into the idea that simply slowing down will increase product quality. But I
by resonious 2y ago
I honestly don't really like the "let's slow down" approach. It's hard for me to buy into the idea that simply slowing down will increase product quality. But I think your comment already contains the key to better quality: close the feedback loop so that engineers are responsible for their own bugs. If I have the option of throwing crap over the wall, I will gravitate towards it. If I have to face all of the consequences of my code, I might behave otherwise.
- isametry 2y agoSlow is smooth, smooth is fast?
- samarthr1 2y agoGreetings, Phil Dunphy
- smoothisfast2 2y agoSlowing down doesn't mean going slow. There's more to software development than vomiting out lines of code as quickly as possible.
- no_wizard 2y ago>Slowing down doesn't mean going slow. There's more to software development than vomiting out lines of code as quickly as possible. Tell that to seemingly every engineering manager and product manager coming online over the last 8-10 years. I first noticed in 2016 there seemed to be a direct correlation between more private equity and MBA's getting into the field and the decline of software quality. So now you have a generation of managers (and really executives) who know little of the true tradeoffs between quality and quantity because they only ever saw success pushing code as fast as possible regardless of its quality and dealing with the aftermath. This lead them to promotions, new jobs etc. We did this to ourselves really, by not becoming managers and executives ourselves as engineers.