News for hackers. Stuff that matters.
Re:Why Not Comments by zo1 on Wednesday September 11, 2024 @12:24PM (#41512859)
I really have to push back against this "design document" stuff. Unless you're writing some sort of uber-complicated, mission-guidance-systems-level code with multiple standards and audit compliance and and and, then you don't this.

Alternatively, if your org or reach for this feature is so large that you need to communicate and decide its internals with a lot of people and as such require something like a design document, then you've already failed and you have way too-many cooks in your kitchen. Design by committee is always doomed to failure.

Thirdly... if you need a design document to communicate your feature to "management" then that means you don't have autonomy to design this feature as an expert, and again, you have too many "fingers" in your pie.

Does this mean you should go into a basement and design your feature like a hermit? No, but a design document shouldn't be your answer, it should be a better team and process around you, as well as a clear business specification.

Re:Why Not Comments by david-gpu on Wednesday September 11, 2024 @01:36PM (#41513547)
We did and it worked great.

The process led to not only better designs, but also better visibility for all stakeholders, from technical leads to individual contributors.

I'm talking about products that shipped on billions of devices, products that you have most certainly used. It worked.

Re:Why Not Comments by bccdee on Monday September 16, 2024 @01:39AM (#41553081)
> Design by committee is always doomed to failure.

If you need to communicate your design to a lot of people, that's probably because a lot of people are depending on the output of your work, and they want to make sure it suits their needs. That's not design by committee—that's just designing something that will be widely used.