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.
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.
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.
Many (most? idk) governments that employ the cops (city, county, whatever) do have insurance for this, and grant police qualified immunity. There are some attempts to hold cops liable as well - https://leg.colorado.gov/bills/sb20-217. The City Council in my town immediately restored qualified immunity for their police. Don't underestimate the level of absolute blind support for cops that exists among the US population.
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?
> Highly skilled early- to mid- career engineers, technologists, and innovators join NASA for focused term appointments, typically 1–2 years with the possibility of extension, to solve complex...
is somewhere in that word salad. I think it's an internship?
Given the list of very large companies in the "glasswing" project - it is likely every competent state actor and criminal organization already has access to Mythos in one way or another. Meanwhile the opensource volunteers responsible for the security of the entire internet don't have access.
> t just sounds like a giant scheme to burn through tokens and give money to the AI corps, and tech directors are falling for it immediately.
This is exactly what's happening. The top 5 or 6 companies in the s&p 500 are running a very sophisticated marketing/pressure campaign to convince every c-suite down stream that they need to force AI on their entire organization or die. It's working great. CEOs don't get fired for following the herd.
If you're a billionaire there's no risk to "sticking to principles", so there's nothing to admire. Also that's not what they're doing. These are calculated moves in a negotiation and the trump regime only has 3 years left. Even a CEO can think 4 years ahead.
It's probably in Anthropic's interest to throw grok to these clowns and watch them fail to build anything with it for 3 years.
I don't know if I've seen "tech debt" do serious damage to any company, and I've been around a long time. I've definitely seen whole teams grind to a halt in pursuit of someone's idealized vision of the "perfect way to organize code" though. They always couch it in the language of tech debt, but really it's just the loudest person's preferred way to shuffle files around - and usually in the direction of more complexity and not less.
Sure, the world will still burn, and the economy will collapse, and the managers will still blame the doers. But it's something.