3 ms·
I don't see any reason that policy debates should be any more problematic than language debates.
by lisper 4y ago
I don't see any reason that policy debates should be any more problematic than language debates.
- mcherm 4y agoLanguage debates are over once a substantial amount of the code has been written. Policy debates continue eternally.
- spankalee 4y agoThis is silly. There are tools that enforce the types of policy we're talking here very well. In a TypeScript codebase you would not let CI pass if the TypeScript build fails. Locally you can still run the output. There's not much room for debate and I've never seen a TypeScript project that both has CI and allowed failing builds to be merged. I've also never heard of someone proposing that PRs failing to build should be allowed to be merged.
- hbrn 4y agoNot every team has eternal policy debates. Eternal debates indicate a deeper problem with the engineering culture. I'd rather have that problem become visible so that I could address it, than keep it hidden under a pile of irreversible decisions.
- peterashford 4y agoI do. Policy is up for debate. If your codebase is in <x> the debate is over