I didn't write that it's exclusively her fault. If it wasn't her, it would've been another captured developer, so obviously her employer is at fault as well.

You are still responsible for your actions.

If I were offered to pilot an airplane but knew I wasn't qualified I'd decline the job offer.

If I accepted the job offer and crashed the airplane because I'm incompetent, would my employer be exclusively at fault, or would I carry some responsibility as well.

The same applies to ruining a mission-critical project such as Bitcoin. You aren't absolved of responsibility because your employer offered you a job without you being qualified.

And as I already wrote, it is mostly our own fault for allowing ~100% of nodes to run a single implementation for so long.

nostr:nevent1qvzqqqqqqypzqvtw30knexxgwasss0qwafnz68hdx6u25xwpclsz4750ez46qpx2qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcppemhxue69uhkummn9ekx7mp0qywhwumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctv9uqzpc503hwqjk0p3d6fzfsmmxa6hgg57zlxt48mm5fe48xktgray8zwky8glv

Reply to this note

Please Login to reply.

Discussion

Sure, but flying an airplane is much more of a binary thing. Everyone on on a given plane wants pretty the same thing out of the ride.

Bitcoin, on the other hand, so many groups that each want different things from it, from every aspect of it. She could rightly conclude she's qualified under the demands of one of those groups, and so fair enough to her.

Yes, if the community cannot widely agree on what Bitcoin is (which seems to be the case), then she's not at fault and her employer is also not at fault. They just adopted the arbitrary data storage definition for Bitcoin so that's what they're optimizing for.

This is basically the coordination tax I wrote about in my last article.