wizzwizz4 on Nostr: nprofile1q…6eyyt Given the choice between "use a bad database design but have ...

nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqhxf96n4sv94q46mrk29xquqwewwecl2083f9r5wdlnl5erc5nf7qf6eyyt (nprofile…eyyt) Given the choice between "use a bad database design but have something to show" and "take the time to design the database properly"… see if you can't mock that short-term deliverable up in PowerPoint. In a week's time, nobody will care about the proof of concept, but that bad schema will haunt you for months (and that's if you manage to replace it).

Anything that becomes the model by which teams communicate is especially important. The rest of your architecture pales in comparison.