3 ms·
Yeah, to me this kind of thing is much better than the carefulness knob. Delaying or just not doing certain features that have low ROI can drastically shorten
by whstl 2y ago
Yeah, to me this kind of thing is much better than the carefulness knob.
Delaying or just not doing certain features that have low ROI can drastically shorten the development time without really affecting quality.
This is something that as an industry we seem to have unlearned. Sure, it still exists in the startup space, with MVPs, but elsewhere it's very difficult. In the last 20 years I feel like engineers have been pushed more and more away from the client, and very often you just get "overspecified everything" from non-technical Product Managers and have to sacrifice in quality instead.
- TylerE 2y agoI had one today that with one email went from "I want this whole new report over our main entity type with 3 user specified parameters" to "actually, just add this one existing (in the db) column to this one existing report and that totally solves my actual problem". My time going from something like 2 days to 15 minutes + 10 minutes to write the email.
- whstl 2y agoFor me the biggest one lately was due to miscommunication and bad assumptions. The designer was working in a redesign in their own free time, so they were using this "new design" as a template for all recent mockups. The Product Manager just created tickets with the new design and was adamant that changing the design was part of the requirements. The feature itself was simple, but the redesign was significantly hard. Talking with the business person revealed that they were not even aware of the redesign and it was blocked until next year.