I'm in the industry (albeit not a 20-year old), and agree that the domain itself is incredibly dry.

The tech is quite interesting, thankfully.

From a customer perspective it's interesting - compliance sucks so much that even a slight improvement/automation goes a long way

I don't know exactly how to measure bang for buck, but my Sony XM4s have been holding up well, sound good, are decently comfortable for a day's work, the battery life is good, etc.

They do have some annoyances like not always sleeping correctly when left connected to my laptop, but overall they are easy to recommend

I'm building a very casual daily price-guessing game for my mum. Every day she gives me feedback, and I'm using it as a chance to de-rust my CSS/React + see how daily games tick.

https://scandle.co.za

Peter was quite vocal on twitter about _only_ using Codex to develop OpenClaw, but Claude is what a majority of people were (are?) using to run the tool itself.

At least both of those threads contain a healthy amount of skepticism in the comments

AI compute costs far outweigh storage costs.

That's the first I've seen of 4k77 and related projects, thanks for sharing. A true labour of love.

Spam

I'm not sure what the distinction between "execute" and "run" is; is there a difference?

No, I don't think there really is. But to be execute is even more clear that it's just... executing the code, whereas I could maybe understand someone being confused that run implied some level of type checking.

Node is just inline transpiling the TS into JS, then running the JS.

This is misleading. It is not transpiling TS in JS, it is transpiling a subset of TS into JS. If my normal TS code can not be "executed" by Node, then it is not executing TS per definition but something else. If you are good with Node supporting and "executing" only a subset of TS and lacking useful features, that's fine. But don't tell people it is executing TypeScript. That's like me saying my rudimentary C++ compiler supports C++ while in reality only supporting 50%. People would be pissed if they figure it out once they try to run it on their codebase.

It's quite close to 100%. It makes one extra-strictness toggle mandatory. Saying it's not TS is much more misleading.

Having a typo in "pendantic" is a masterstroke

Seeing that my comment was against pedantry, no contradiction there!

> "pendantic"

Genius!

One more time and it's pentadic. But imagine someone finding a way to bikeshed anti-bikeshedding tools. "Take with food."