jacobsenscott

The upside will mostly be the schadenfreude we'll get when, coming in Q4 of this year, the managerial class is finally called on to show ROI for the $100,000+ (depending on company size) per employee they shunted to anthropic and openai.

Sure, the world will still burn, and the economy will collapse, and the managers will still blame the doers. But it's something.

It cannot be uninstalled

You never need to write "fix", or "prevent" if you write a good message. Nobody says "fixed the car by changing the flat tire" or "Go prevent engine wear by getting an oil change today. You say "Change the flat tire", or "Change the oil".

You can do the same when you write commit messages. "Wrap user and account update in a transaction" - "Delete temp files after use".

None of this is as good as "free array memory before it goes out of scope". This is better than `fix: memory leak` - which is what most people would do. It's also better than `fix: free array memory...` because `fix:` is redundant when you have a good message. I get people want to build automation around this stuff, but just do that in a footer of a commit message where humans don't need to see it.

This is what a changelog is for

There's no benefit to any of this. Just write like human. It will be clear if it's a fix, or a refactor, or ?. Typically it isn't just one of those things.

The "Just Say No" engineer is a person who knows what existing tools can do, while more junior people don't know what their tools can do. So junior people are constantly proposing new types of yak shaving (new architecture, new storage backend, new framework, etc) that must be done before solving the problem at hand. This is all wasted resources and time, even if LLMs let you shave yaks faster. A good JSNE focuses your resources on solving problems straight away, not pouring them all into a bottomless pit of busy work.

Reading a well written programming book will put you ahead of 99% of other programmers using that language. Most programmers learn some subset of a language to get things working, and never learn more than that.

When a cop does millions of dollars of damage they only choice is for tax payers to pay, or for the victims to get nothing. Definitely the cops should also face consequences though.

Can't you just build the source and run it without giving them any information? Or does the editor itself require information and phone home while running?

These are called co-los (co-location facilities). Probably any medium to large city has a few.

> technology, ai, screentime

Significant parts of our society and government are actively hostile to education. Blaming the students is convenient, but probably not accurate.

> They'll never accept intentionally "slower" development for the greater good.

That comes post Chernobyl.

> ...for a few days, access is granted to this work. The number is extremely limited. The window only lasts four days. Will you answer the call?...

What? This sounds like a phishing email from before phishing emails got good.