tbeseda

@tbeseda.com

𓅓 Today's rainbow is tomorrow's tamale. Engineer at @sanity.io working on IAC and compute. he/him tbeseda.com #380,179

The "SOTA" acronym is really starting to get to me. It's not even good jargon. Arguably, "frontier" is interesting and sorta qualifying. But saying something is "state of the art" _and_ using an acronym... you're telling on yourself.

There's a 3-bay mechanic shop going up for sale in my small mtn town. I think it'd make a killer fly fishing + bike shop (summer) and ski/rental shop (winter). Right on the main road. Across from the reservoir/river. Put a coffee+taco truck in the lot...

Weird mountain town thing in 2026: be in hardware store, several phones ding with an ominous notification sound, look at each other, "that's downwind from here," relief. Wildfire weather.

On the back of AI hype train someone should reboot Rdio. Shove some LLM story in there to get the funding and build the music streaming app we all deserve. Apple Music just queued up Nirvana and Black Sabbath when I started an _Arctic Monkeys_ radio station. I love those bands! But this is aint it.

Most of what happens in a given software ecosystem revolves around a core group of authors. Not necessarily the main committers to a platform, but the contributions downstream from those changes. The same names pop up a lot. That's the stuff worth following and learning from IMO.

If your daily playlist doesn't include System of a Down while the US is doing some stupid shit in the Middle East, what are you even doing?

Coding models seem to have the best results in languages where there's good tooling for reference + module discovery and the body of marketing materials used in training is almost zero. Go/Gleam/Zig: A+ JS: shit show

godammit Apple Music. I've got a good station going with RATM, Pearl Jam, Nirvana, A Perfect Circle, and then Puddle of Mudd gets tossed in! What's next? Hoobastank?!

It's 2026, can we solve the everything bagel problem? I don't want to eat it over a napkin so I can funnel all the good stuff into my mouth after eating the bagel part.

PSA: #AWS #Lambda nodejs24.x can run #TypeScript without a build step. index.ts (your handler): export const handler = async () => ({foo: '.ts'}) index.mjs (one liner): export {handler} from './index.ts' NODE_OPTIONS=--experimental-detect-module AWS disabled this ↑ Other flags break execution.

It's wild that the Xcel page to check on an outage's status (not even view the map) is 28 MB. And it doesn't even handle the return key when I enter my phone number. Like you don't have power, so usually no WiFi, and you have to load and evaluate 21 MB of JS. Total img size is 109kB btw...

Many UI libraries "support" #customElements, but has work been done to go the other way? Use case: Have a future-proof, web-standards-based UI with a series of shiny #webcomponents; but (for reasons) I need to slam in a #React thing. No build step. Slow is fine. Wrap a blob in <react-thing>? 😶‍🌫️

Gusts nearly hit 100mph today. Weird when your ears pop just sitting on the couch. Still waiting for the power to come back. Wifi on battery backup. Got a good book for when that runs out. Fingers crossed no wildfires.

Wind readings: currently 43mph. Gusts hit 96mph today. Only 65mph yesterday.