News for hackers. Stuff that matters.
Re:Ask HN: Is there a better way to document complex softwar... by josephg on Sunday November 25, 2018 @10:16PM (#18530780)
Counterpoint: If small design decisions require global SQL schema changes, it slows you down. And small barriers to change will, in aggregate, kill you.

Eg, over a month of iterations: "Can we add another field to user registration? It should be free text. Oh, they should select from a list. No wait, make it a date. Actually a date and a text field. No wait, dump the text field."

Sometimes slowing down these changes is a good thing. But often, being able to ship each iteration along the way will help your design team converge on the best solution. If you need to write a schema migration for every iteration, it kills the ability of your team to experiment and explore the space of "what should our product actually look like".

Faster iterations = more iterations = better product in the long term. Sometimes the best long term result requires some random stuff getting crammed into a big JSON field in your database in the short term.

Re:Ask HN: Is there a better way to document complex softwar... by enimodas on Monday November 26, 2018 @05:45AM (#18532406)
Sounds like the real problem is that there's too much friction with schema migrations.