It’s always this tired argument. “But it’s so much better than six months ago, if you aren’t using it today you are just missing out.”

I’m tired of the hype boss.

> The lower-bound estimate represents 18 percent of the total reduction in man-hours in U.S. agriculture between 1944 and 1959; the upper-bound estimate, 27 percent

I'm not seeing that with LLMs.

I feel like at some level that would remove the possibility of making a “just as good as humans but basically free” arguments and move discussion in the direction that feels more productive: discussing real benefits and shortcomings of both. Eg, loss of context with agents vs HR costs with humans, etc…

> If AI agents help each support employee handle 30% more tickets, that's like adding 30 new hires to a 100-person team, without the cost.

I think this is an oversimplification designed to make LLMs seem more profitable than they actually are.

Longer reply:

I have on-call experience for major services (DynamoDB front door, CosmosDB storage, OCI LoadBalancer). Seen a lot of different philosophies. My take:

1. on-call should document their work step by step in tickets and make changes to operational docs as they go: a ticket that just has "manual intervention, resolved" after 3 hours is useless; documenting what's happening is actually your main job; if needed, work to analyze/resolve acute issues can be farmed out

2. on-call is the bus driver, shouldn't be tasked with handling long term fixes (or any other tasks beyond being on-call)

3. handover between on-calls is very important, prevents accidentally dropping the ball on resolving longer time horizon issues; handover meetings

Probably the most controversial one: separate rotation (with a longer window - eg. 2 week) should handle tasks that are RCA related or drive fixes to prevent reoccurrence

Managers should not be first tier on any pager rotation, if you wouldn't approve pull requests, you shouldn't be on the rotation (other than as a second tier escalation). Reverse should also hold: if you have the privilege to bless PRs, you should take your turn in the hot seat.

May you all have a happy new year, and many more!

https://www.tabletmag.com/sections/news/articles/red-pill-pr...

Loaded associations.

It really only took us one session to figure out the major mechanical systems in the gameplay, and a few we are still learning about. The major component remains the role playing experience which is the same, no matter which dice you throw to decide outcomes of situations.

I think Hasbro will soon realize that while the social impact of the name D&D is deep, the stickiness of the system is much lower than they gambled on. It's unlikely that any of my member group will soon buy anything new from them.

I don’t mind the idea of trying and failing because the market isn’t there or my execution sucks, but trying and having my earnings be trapped in an algorithmic black hole with no customer support - no thank you. I don’t think there’s any other kind of business interaction that works in this way.

Eg, I can’t imagine one day waking up to my electric company unplugging my house and refusing to talk to me ever again.

Ie, it's undeniable that the final program works much faster, but the article should really be called "a smarter memoization trick."

In general, I don't care about the people behind the article content. They have their own lives that should be private, and the articles should be able to stand on their own merit.