logoalt Hacker News

hibikir • yesterday at 9:14 PM • 0 replies • view on HN

Nobody bothers to write down what it's supposed to do because nobody thought about it enough for a full spec to be conceivable, let alone written. In a lot of modern development, you have a committee of non-technical product people who might, at best, own a single flow, but they sure don't own, and don't care, about the interactions across flows. And then you have development teams that live and die by KPI, and thus draw the edge of their responsibilities in the narrowest form possible. I was told by a subscription team in a certain very large company that they just own the subscription platform, not anything about the data in it, or the relationships mapped in the data. Bundling? Data. Billing? data. They are just 40+ people whose responsibility is to keep a database up, and therefore no outcomes other than inability to retrieve the data was ever their problem.

So who owns outcomes? Usability across the board? General customer experience? Nobody. The actual software that people pay for, is orphaned, and anyone trying to track down problems is just asking to be blamed for them. Thus, most of what happens is undefined behavior, like if we were writing an old C standard. Having someone that has the responsibility to make the product as a whole do something, and thus maybe be able to write the spec eventually, would already be an improvement.