perkovsky

3 ms·

1. 1.▲
   Show HN: NGB, an open-source .NET platform for document-driven business apps(github.com)

   2 points by perkovsky 3mo ago|0 comments
2. 2.▲
   by perkovsky 4mo ago

   I like the “claim-driven” framing. For stateful systems, tests named after setup details often get weakened over time. Tests named after the claim they are trying to falsify are harder to water down. The part I’d be most interested in is ho
3. 3.▲
   by perkovsky 4mo ago

   Agree. Postinstall scripts should be explicit opt-in, not ambient capability. Most packages should not need arbitrary code execution during install. And when they do, that should be obvious during review. The default should probably be: ins
4. 4.▲
   by perkovsky 5mo ago

   I agree with this. Moving the git repo is easy, moving the whole project surface is the hard part. Issues, releases, CI, docs, security advisories, search and discoverability all tend to get coupled to GitHub over time. For open-source proj
5. 5.▲
   by perkovsky 5mo ago

   Yes. I’d add: design the module boundaries before splitting deployment. A modular monolith still forces you to name ownership, data boundaries and invariants, but without making every mistake a networking/ops problem.