Global Feed Post Login
Replying to Avatar Silberengel

I have never seen Nostr "smaller projects" not become the basis for the Nostr "larger projects". Even major rewrites don't help, for long, as the regressions immediately begin seeping in, and the entire architecture groans under the weight of its own inefficiency and ineffectiveness.

The crappy quality they begin with just stays that way, indefinitely, because those developers refuse to learn better engineering and are actively discouraged from doing so, by people who pay them to stay ignorant and amateurish, so that they can't steal the limelight from the Planned Winner.

Avatar
MichaelJ 10mo ago

It's worth slowing down, refactoring, and retesting as soon as you notice an architectural flaw. The early stages of the project is the best time to do that, because the more code you have, the more time, energy, and risk is required to fix a bad design pattern.

Reply to this note

Please Login to reply.

Discussion

No replies yet.