> I got a notification from Home Assistant that a fart was detected in the driveway. My neighbor was walking by my house on his nightly walk and ripped one as he passed by the driveway and the fart was detected.

I'd have to disable notifications for this in my neighbourhood to avoid alert fatigue.

> You can't out-cog a robot

This is such a great way to summarise the issue facing rank-and-file employees. If your job is predictable, repeatable, systematizable then you're "competing against the price of electricity [and GPUs]"

> people who can't do 2+2 and ones that can't understand the question without rephrasing it three times

We resorted to filtering candidates in-person with 5 basic technical questions on pen and paper. And I mean _really_ basic questions.

This was surprisingly effective because it filters for many non-technical skills like being able to read and write English, follow instructions, and show up to the office, on time, and appropriately dressed.

The number of candidates that failed these basic skills was astounding. We had candidates show up 20 minutes late, or email 2 minutes before the "interview" asking for a Teams link even though the invitation stated the meeting was in-person (highlighted in yellow). Others couldn't write their own name legibly on the paper.

A candidate that cannot answer basic technical questions has no hope of being able to prompt an AI effectively or review the code it produces.

We don't go that far. From the small sample I saw, I noticed that people who can't answer the basic questions are ones that can't use AI effectively either and don't understand that interview is for them to showcase their skills, with AI or without.

> When the cost of building goes to zero

Where are they getting all those free tokens from?!? I don't like this rhetoric. It still costs money to write code, only now that wealth gets transferred to Anthropic instead of to individual contributors.

And even ignoring the token costs, that is just not true.

Sure, for some cases, the cost is going down. I and others on my team "one-shotted" impressive features in an hour of agent work that would have taken humans probably a month if done completely manually.

I've also seen agents going in circles for an hour on a fix that would have taken even a junior 3 minutes to get right (after it was struggling for 10 minutes, I wanted to see if it can ever get it right as an experiment).

And when taking a look at the whole organization, orgs still just aren't really shipping that much more quality features to their users as the impressive one-shot demos would make you think.

> orgs still just aren't really shipping that much more quality features

Writing code was never the bottleneck at large enterprises.

Nor was product quality the goal. Principal agent problems abound. The large org's behavior follows the thousandfold incentive gradients of the individual employees in their own career, CV building, promotion paths, budget allocation, etc.

Same, but with GitLab pages.

Every hotel I've stayed at in Hawaii charges one - usually to the tune of $50+/day - even if the hotel has no resort-like facilities. It's a bullshit fee.

> a light grey text on a white background

This makes the page SO hard to read. Why are "designers" still doing this? Have they no respect for their readers?

> Maybe add a dedicated clear button.

It's tedious to have to hit DEL 6 or 7 times towards the end of the game. Maybe ESC could clear the whole word?

This.

100%. It deserves more detail, too.

I've spent many hours explaining how idempotency is supposed to work, and why it's important. Most teams understand the need for it, but very few thought about it up front.