some time ago I wrote some of what I consider good code recommendations nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q
note1y9hfddyw2xrt3l50n9pystcc6qn8q5wl3tkg4aa9xky2hvqharkqhdk80q
some time ago I wrote some of what I consider good code recommendations nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q
note1y9hfddyw2xrt3l50n9pystcc6qn8q5wl3tkg4aa9xky2hvqharkqhdk80q
Yes, I like that!
TDD is 🤌
i am always writing tests because i very often mess things up and do a lot of encodings, but i haven't yet wrapped my head around this BDD style and other protocol correctness
to me part of the problems start before you even get to writing tests, with a protocol that is unclear or breaks domain boundaries or mixes concerns or creates ambiguities, especially ones that are likely to trigger a human to misunderstand even when the logs are printed out ad nauseum
We're solving the protocol issue, slowly. As long as that progresses, I'm okay with it being a bit messy.
Messy implementations are another thing because they send out corrupted events and burn the Nostr brand.