73 karma · joined February 18, 2015
This time they say they didn’t do it. That might be true or maybe that employees credential was compromised. We don’t actually have facts yet.
Not sure what this says about humans.
The best advice for the vast majority of users who can no longer easily prove an account belongs to them is to let it expire in a few months automatically.
In my experience with this format it isn't like you are coding for 9 hours. It starts with soft HR stuff, ends with a sales pitch to you, and most of the middle is just pleasant conversation with interesting people.
Seems like we need a fundamental challenge to the concept that you have any jurisdiction whatsoever.
"Couldn't this be stateless?" "Do you have a plan to be able to shard this?" - We will almost always pivot from the agents initial design but the agent is able to easily understand the reasons and benefits and align quickly.
If I was writing the code myself, I'd often have to make compromises between the ideal architecture and the level of effort required to implement it - now I can just always have the ideal architecture.
Sounds great to me.
A well authored CI review process is significantly better than any human could do. We have the AI review not only the changes but clone and investigate all related repositories that integrate with the code to evaluate interactions, check all open and historical issues that may be related, review production/development logs for the feature, etc.
It will then also go update issues/tasks to reflect the changes after the merge.
Similarly you can have automated agents watching post-deployment to mitigate risk in the "a new feature just went out" time-frame. Just having someone check the related logs in the hours after deployment can catch a lot of issues that otherwise would turn into a fire-drill.
When your equations are missing a number to work, you announce a new particle.
For your use case n8n may be a good fit, and Claude or Codex will be happy to set it up for you.
If you want this "messenger interface with computers for the agents" feature set Grok Bot is quite good and effortless to use. With Tailscale configured on its personal VM it can connect to machines on your network easily.
In May they had to solve for 30x growth overnight, and I would guess its closer to 100x by now. The reality is a centralized solution like this may no longer be a viable option with the scale of code generation.
It is uncommon to find engineers doing work they find trivial outside of some consulting niches.
I think perhaps the assumption that engineering managers should have any employees may be outdated.
I can imagine average and mediocre engineers equipped with tokens could create chaos and debt on a scale never before imaginable, so it’s easy to see how orgs who still have these employees around are struggling with the transition.
The reality is you need to get rid of them all, and replace them with the most experienced highest paid person you can find. In the near future that person will become obsolete too.
You need to be thinking about an entirely different form of life for all of humanity, happening in the very near future. Focusing on one specific field that may be earlier in the obsolescence chain is a distraction.
Merit based society based on intelligence or work of nearly any kind is about to cease existence.
For some reason it feels to me that this should make mathematicians feels better. :)
Did Anthropic just give up their entire momentum on this garbage in an effort to increase profitability?
The Intel ME chip is running its own OS on every single Intel chipset, even when the computer or laptop is shut down, and accessible directly through attached Intel WiFi or network cards. With full memory access, with no way to turn it off.
https://en.wikipedia.org/wiki/Intel_Management_Engine
The totality of reassurance we have about it is intel’s promise that they won’t put a backdoor in.