AlexMoffat

Listen to your customers but ignore what they say. “Treat your customers like a kindergarten class. If they’re all asking for a snack they’re hungry but perhaps they really need a nutritious lunch instead.”

Claude’s prompt heavily pushes it towards grep. We have an internal cross repo semantic search mcp and to get Claude to consistently use it a skill and prompting was not enough. A pre tool use hook is the answer. Claude will even write one for you if you describe the problem to it :)

It's just you. Something about your comment seems AI-generated. See how that works?

I ask it to write a markdown file describing how it should go about performing the task. Then have it read the file next time. Works well for things like creating tests for controller methods where there is a procedure it should follow that was probably developed over a session with several prompts and feedback on its output.

As for reasons, in the US it's probably related somehow to trying to get in good with the current administration.

The genre of random internet commentary by people who’ve played a video game and thought about a subject for 5 minutes after skimming an article vs actual professional who has read deeply in the original sources is fascinating.

The counterpoint is that if you don’t adopt a framework you end up with a “framework” you built yourselves that people outside your team don’t understand, is generally poorly documented and needs constant work to add features existing frameworks already have. There are common features needed on the FE and common problems to solve, why not at least start with something instead of nothing?

The words you're looking for aren't conservative or reactionary they are bigoted and asshole. Best software engineer I've ever worked with is a woman, the rest had exactly the same range of ability as the men. Overall though a much lower level of entitled ignorance than "guys like us".

Can't you, and shouldn't you, just add appropriate comment / annotation to tell the linter to ignore the next line? That way you make it clear to others reading the code that you know what's going on.

The answer is in the article.

How do you square this with your advice to use S3? Apple bad but AWS ok?

Lombard Street?

+1 That's a great book.

Their comment history supports that hypothesis.