I've seen a few senior developers who weren't great programmers, but could communicate effectively, manage up and down, etc. So long as they were willing to defer to others on harder technical topics, they usually made pretty good team leads when/if promoted.

After 5-6 consecutive approaches fail, I need a reason to think the next one might work out to stay motivated.

Claude will keep burning credits trying new approaches until something sticks. That's a huge advantage in a field where most of the things you try don't go anywhere.

You need a JS trampoline to call your WASM and make browser primitives available to it, and IIRC calls into browser code incur some extra overhead, but those are pretty manageable.

Additionally: for high level languages, source code is _much_ smaller than compiled binaries. If your initial needs are simple, your users are likely downloading more than 10x as much code.

Job workers could query the parent table, no need to modify them.

https://esajournals.onlinelibrary.wiley.com/doi/10.1002/ecy....

You’re welcome to host it at your own venue. Or , I guess, to keep whining that you’re not being given free services by someone who dislikes your work.

Denser air carries more momentum, which means more frequent (and more severe) hurricanes.

Commit signing primarily exists because linux kernel development happens via email, which isn't a secure channel.

In that context, signing is used to prove provenance; a commit signed by someone with merge rights gets included, and if you repeatedly sign bad code you'll have your right to merge revoked.

> you can hold me accountable for that commit

I wouldn't personally want to be held accountable for a commit I'd never so much as read, so I would never sign (even locally) a commit until I'd looked at it.

"No antenna/modem I can't readily remove" might be _slightly_ more achievable.