Applied cosmology toward machine precise solutions to replace humans with autonomous systems in all domains.

Frisco, TX
Joined June 2009
As AI agents become more capable of accomplishing real-world work at human-equivalent competencies, we will need to reorganize our division of labor. Some changes will disrupt how a job role is performed. Other changes will change what job roles are needed or how many people are needed to do the work. AI agents that automate tasks can be seen as tools for accelerating a person's work. A person can do more and they can do it faster with AI tools. However, the job role remains firmly the human's responsibility, because their know-how, judgement, and accountability are irreplaceable. AI agents have no moral or ethical grounding. An AI agent cannot be held liable. The buck cannot stop at an AI agent. A human job role exists for those purposes. As work is accelerated, we will see responsibilities roll up and concentrate into human job roles that have expanded scope of control. Work bottlenecks are primarily due to the slow speed of knowledge transfer, collaboration, and consensus-building between humans. The more that multi-person collaboration can be replaced by solo work, the more efficient thr work becomes. Job roles will become more multi-disciplinary, as responsibilities concentrate into solo work for improved efficiency. If coders no longer write the code and they no longer read the code, the job of engineering software shifts from coding to overseeing requirements, design, quality assurance, and building machines that do those activities along with doing the coding. This disruption and displacement is emotionally taxing. Egos get bruised. It's very difficult for highly-paid professionals to accept that their knowledge, skills, and competencies can largely be automated. Their experience remains valuable, but it needs to be applied differently. Instead of toiling as they used to, the knowledge, skills, and expertise need to be directed into training, building, and running machines that do the job role they used to do by hand.
147
I got fed up with /implement pushing tiny commits to create a pull request containing slices of one or two tests with barely any functionality. I asked why its slices were so tiny. The agent answered that it was minimizing risk. I never asked it to minimize risk. I am now asking it to accept higher risk. Be ambitious. Aspire to be like an X games competitor jumping off the edge of the world in a squirrel suit. Fly and be free. Yolo!
1
1
196
Because software architecture and design are all about trade-offs, you will start to hear me repeat the following: Why are you chasing a 140+ IQ frontier model to perform a 100 IQ use case?
1
3
246
In the long term, I believe that tokens will be commoditized so that 99% of usage will target 100 IQ inference targeting 100 IQ human audiences. Only the remaining 1% of tokens will need 140+ IQ inference for all other use cases.
Replying to @TokenGremlin
Who is 'everyone'? That perspective represents those seeking the strongest models at the frontier. It does not represent enterprises with enormous agentic transaction volumes that require only modest inference, and the goal is cost-effectiveness. Let's say an enterprise with millions of customers needs bill explanations or customer care assistance.
1
114
Ben Eng retweeted
that tailworm site reads like gigaslop, i call bullshit on the framing. the ssh bug is basically: authorized nonroot access can become root via unix socket forwarding. serious, but propagation follows ssh policy. this concerns tailscale’s opt-in ssh server, not ordinary openssh. the path also requires the attacker (yourself) to be added to your tailnet, enabled tailscale ssh (not enabled by default), configured forwarding (not default).
16
35
4
348
22,006
Tailscale is great software, so it's unfortunate to see so many people sharing this as "Tailscale got hacked.", which is misleading. This is not about unauthenticated attackers breaking into random Tailscale nodes. It's what attackers can do after gaining authorized SSH access or compromising an already trusted device. If I understand correctly, you are secure if you only use Tailscale for your own devices and don't grant anyone else access, which is how many people use it.
‼️ Researcher Erica Windisch skipped coordinated vulnerability disclosure and published 11 unpatched Tailscale flaws. In her lab, Tailscale SSH race conditions let one hacked device get root on other servers and add a rogue node.
Readers added context they thought people might want to know
The Tailscale SSH findings require prior authorized access on the tailnet per the researcher's report; Tailscale stated issues concern post-authorization behavior only and did not recommend disabling SSH for everyone. tailworm.com x.com/IntCyberDigest…
26
75
7
475
32,103
Hey @mattpocockuk, /implement-spec doesn't seem to choose by default to prioritize the success path, which enhances features functionally to deliver the most value, ahead of failure handling and edge cases. I have to explicitly guide it to do so. Nice tweak to the skill?
1
95
For projects with containerized deployments, after a while you will notice very poor hygiene with regard to containers and images that accumulate. The process of determining which images should be retained and which ones should be deleted is tedious. There ought to be a skill. More sustainably, there ought to be a way to specify rules for hygiene, so the normal life cycle operations prevent this from becoming a problem.
1
99
My wife and I went from paying over $300/mo for television packages from the local cable provider to now only paying for Netflix and Hulu. I also used to buy ESPN+ along with a NHL package. When a subset of games needed subscriptions to other providers, I got fed up and cancelled everything. If I cannot purchase a single subscription for all games of interest to me, I won't pay at all.
1
72
I need to purchase a track pad or mouse jiggler to prevent the MacBook from blanking the screen and disconnecting the VPN, so that long-running tasks in Codex can run uninterrupted without needing me to babysit only to manually jiggle the pointer.
1
3
168
What is going on at Anthropic with high profile contributors to Claude Code exiting before the anticipated IPO? Seems like these individuals are foregoing a ton of personal wealth without an obvious opportunity as motivation. Their public statements remain positive toward Ant, so there is no obvious disenchantment. Very curious.
4
8
421
The industry has grown too soft and comfortable with orderly disclosure of security vulnerabilities. This chaotic and dangerous environment will hopefully awaken the development community from complacency.
1
1
4
289
What I mean is that instead of being coddled to think that we can run to the government begging for false safety, instead we will arm everyone with a zero-refusal frontier model behind every blade of grass for lethal self-defense.
1
27
How many generations of humans have existed since homo sapiens split from our common ancestor with other homo species? «Roughly 20,000–30,000 generations, most plausibly around 20,000–25,000» -Grok If we take science seriously and we take the story of genesis seriously without pitting one against the other, we must interpret these as telling the same history with consistency. Using different styles and words, but two perspectives witnessing the same truth in reality.
Replying to @Timcast
Biology and God tell us that we all have a lineage that follows from a common ancestor, whether that is a prehistoric primate or whether that genesis is Adam and Eve. Perhaps those two scenarios are the same. You can ew to pooh-pooh that, but apparently that stance would be anti-science and anti-Biblical.
1
161
We need a software revolution around how to maintain the secrecy of secrets. AI enabled exploits of security vulnerabilities will continue until we get this under control. The biggest weakness in the face of attacks is the lack of adequate protection for secrets.
1
62
Don't trust me, bro. Rely on machine verification of evidence.
Replying to @cometaj2
My point here is that the process involving humans is slow and difficult. More importantly it relies on trust in expert opinions based on reputation, experience, and wisdom. This inferior to relying on implementing working code that can produce evidence. Implemention and evidence can be produced by an untrusted junior and AI agent. I'm one of the foremost and most trusted experts. I'm saying don't trust me bro. Go with the evidence instead.
39
Humans are exhausting because of how time-consuming it is to reach a shared understanding, consensus on decisions, and agreement to move forward. Each human has their own biases. Most problematic is that each person has their own hidden agenda and value system (ranked priorities). You can't define the acceptance criteria as an acceptance gate and apply a spec-driven approach to perform red-to-green test-driven development to accomplish human work. It's tiresome.
2
1
3
141
At some point, we will realize that you don't need right or ten human experts across disciplines to decide together what to build and how to build it at a cost of a million dollars. A solo dev can do it better and faster at a cost of $100k and a few hundred dollars of tokens.
1
28
If you disagree, it is precisely this kind of disagreement that demonstrates How I am correct. Human disagreement that gates forward progress is an impediment to schedule acceleration and hill-climbing toward the goal. Machine iteration is the way.
11
You really expect me to create a 12 character password for encrypting a file, and be able to remember it into the future, after never needing to use it on a regular basis? You are crazy. After forgetting my Obsidian vault sync password, I am well aware of how impossible it is to manage these kinds of secrets.
1
1
73
Tibo is responsive, timely, and polite to the toxic and rabid customer base that inhabits this platform. The majority of replies to his posts are rude and disrespectful. People are so shitty.
There were reports of usage draining faster than anticipated for some users over the weekend. We've identified approximately 40,000 accounts that had an inconsistency on which usage limits where the actual usage that was applied did not correspond to their actual selected plan. We are reaching out individually to all these users and have corrected the issue. If this affected you, we'll add credits to your account. Sorry we got this wrong.
34