4 ms·
> “Developers are trying to ship value to customers.” I’ve also seen this be fairly rare. Devs shipping nothing - not even aware if what they're merging will t
by gonehome 4y ago
> “Developers are trying to ship value to customers.”
I’ve also seen this be fairly rare. Devs shipping nothing - not even aware if what they're merging will turn on.
They write something they haven’t really tested, merge it, and call it done - a user may never see it and they don’t have any knowledge about how the thing actually gets built and shipped.
Obviously this is worst-case, but in my experience this is a common default. The complaints about friction are because they’re actually forced to reason about how the machine works in order to ship something beyond merge.
- Aeolun 4y ago> They write something they haven’t really tested, merge it, and call it done This is a problem of incentives. For all intents and purposes, the dev organization ceases to care the moment something is merged. Nobody is rewarded for making sure everything is fine all the way to production. Now if you ship two extra Jira tickets this sprint however...
- dhzhzjsbevs 4y agoI don't generally make a habit of basing my software development lifecycle methodologies on the lowest common denominator engineering org. Some shops ship value to customers with tests and metrics every day.