Moving to @[email protected] soon (tm).
Just so you know.
Lawyers think I’m a developer, and developers think I’m a lawyer. Both are wrong.
Previously #FSFE, now building trains 🚊🚞🚄 Views mine.
Toots in 🇬🇧🇩🇪 on whatever strikes my fancy - #FOSS, #kayaking, #privacy, #bread. Easily amused.
If I’ve offended you, it was almost certainly unintentional. Please reach out, and I’ll try to do better.
Follows welcome, but if you displease me in any way, I´ll block you without the slightest hesitation. My timeline, my rules.
| Baking | Sourdough, yeast |
| Whitewater kayaking | Rarely more than class III |
| Pronouns | He / him |
Moving to @[email protected] soon (tm).
Just so you know.
Look at the way we build software and systems that simply must not fail: Code for the Voyager space probes. Control systems for airplanes, trains and similar stuff.
It’s slow, painstaking, expensive, and boring. But in the end, you get a piece of software that will exactly what it’s supposed to.
Compare that to the haphazard way in which „smart contracts“ are slapped together.
The two approaches couldn’t be more different.
If you publicly express your faith in anything involving „smart contracts“, you’ll look to all the world like a stuffed turkey right before Thanksgiving dinner:
A juicy bite there for the taking.
Contracts always contain ambiguities. This has caused us as a society to build a system of civil courts, lawyers etc.
Software always has bugs. Always. Yes, yours does, too.
Oh my.
Anyone who believes in „smart contracts“ has never talked about real contracts with a lawyer.