farfatched

I'm sure GitHub Actions are more intensive, but that doesn't make it harder to scale, which is what martinald said.

> Scaling actions is VMs, networking, imbalances in load, memory, insuring that folks aren’t running VM training against your infrastructure.

That infra scaling is what the cloud provider can easily offer.

Meanwhile, GitHub repos/issues/PRs is all the business logic that they've written, evolved over time.

Many coupled distributed DBs, indexes, consistency concerns, etc.

That's trickier to scale.

I try this, but it has issues.

* Sometimes I'm in flow state, and so breaking at 17:00 breaks that.

* 17:00 is rush hour, so if so leave then, my commute goes from 60m to 90m. So I leave at 16:00, and catch up later. But now I'm context switching more.

* If it's 14:30 and I know I'm leaving at 16:00, then I'm hesitant to work on something that might need more focus/debugging.

All these are workable, and many parents are testament to that, but at least for me, it's all contributing to less productivity.

Yeah, work is now my time for tranquility.

My passion for tech remains, and now work is the time I spend on it, but not on my assigned priorities, sadly.

> "The only people who will remember you worked late are your kids."

I really need to kick my engrossing tech hobbies. :(

And yes to the wider point. There are many people more capable people than me, but sometimes it's about priorities, and top achievers in fields will usually be sacrificing something else.

Free time will return!

Not much, but some evenings will soon be available!

Do we really know?

Do we understand the mechanism behind any hallucinations?

Link? (To any of the above.)

It's just a little fun.

Safe needle practices have been known for decades, it's really not that hard.

If I say I'm going to borrow a needle and just look at it, you should just trust me. If I use it, I make sure to sterilize it before returning it.

I don't think this is a fair critique.

The author of the post uses standard terminology like entropy coding and arithmetic coding, and cited a paper "in 2023, Google DeepMind released a paper arguing that language modeling and compression are two views of the same thing" which discusses it further.

This blog post is great. Well explained, and clearly took a lot of effort.

I don't interpret it as them claiming to have to discovered it independently.

What does "burn out" mean?

Doesn't the CPU throttle if the phone gets too hot?

Or maybe some parts like the eMMC aren't spec'd for things like constant logging?