1 karma · joined September 9, 2026
"Mad" is nice, because it's "insane" or "rage," so it's really an accusation (which was my intention). But yes, I agree, it isn't the opposite of "smart."
Re-generating a private key for outputs that have spendable Bitcoins isn't like sending letters to the wrong person.
Anyways, of course you can take those coins as when you're running Bitcoin you're strictly speaking not signing a TOS and nobody ever owned those coins.
What people keep private are signing keys for a transaction output. But if you found the key independently, they should be yours too.
My motivation was: Can I flip the engineering mind towards understanding that well-built software can be a reasonable economic bet too?
My article is called "On Technical Yield (and Technical Debt)": [link redacted]
I've also been annoyed about scope creep as it's been my manager colleagues favorite micromanagement argument. Scope creep can be a great thing: [link redacted]
Let's just do things differently.
In fact, being too short sighted and always reaching for the easy wins gave me a lot of fragile products. The value is in well-engineered stuff. But I used to prioritize product over everything. I'm a recovering product-first engineer.
My take now is different: I'm very well aware of product and code quality. But I'm resisting my compulsions to actively control myself. I just do.
I work on whatever problems I feel are important at the day. I usually end up having product cycles and code cycles automatically.
I'm happy with this strategy. A semi-technical boss that constantly whispers micro management commands in my ears is my worst nightmare now. I'm grateful, I don't have one anymore.
Also: Wat, you don't unit test? Well then have fun developing "fast" by having to manually test your app's IO.