I’m pretty AI pilled. This loop stuff is slop. I respect @steipete for his innovation - but openclaw is a bloated unstable pile of garbage because of stuff like this.
I’m all for loops of crons and webhooks where an AI agent wakes up and performs some task like cleanup, or updates the docs or triages errors. I think these are great for standard well defined tasks with a fairly deterministic route (a.k.a workflows).
I think what these guys are talking about now is jumping the gun. The models need to be guided, and you want to atleast skim their output so you don’t end up with slop. Humans are far better planners and architects than models.
You absolutely shouldn’t delegate away prompting and reviews in my opinion. this encourages the creation of crappy buggy unsafe software that actually hurts adoption.
Every single enterprise will have its own AI lab within 3 years.
Companies are already training their own models on open source foundations using their own data and getting state of the art performance on their specific tasks at 50% of the cost of OpenAI or Anthropic.
40 years ago, no company had an IT department. Then suddenly everyone did. The same thing is happening here.
Malte is right btw
Most people landing these positions are coming from a similar one
And there's still a "glass ceiling" for most people trying to break into these, unless you are focused, DYOR and make a strategy + plan to get into these places
https://t.co/grryYwYbXJ
When we first demoed Claude Code internally, it got two reactions on Slack.
A year after GA, @_catwu and I sat down to talk about what's changed: why I use auto mode instead of plan mode, how routines fix bugs before I see them, why I do most of my coding from my phone now, and where the product is going
Brutal Truth: If your AI company isn't a rocket ship, your best team members are likely already interviewing for roles at other companies. Opportunity costs are too high.
“How do you convince other engineers? You're not their manager”. @kelseyhightower, former Google Distinguished Engineer, on using Empathetic Engineering to win over peers:
“The one thing that I tried to do was: how do you convince other engineers? You're not their manager. How do you get them to trust you? I started these empathetic engineering sessions. The first one was like, get the Kubernetes team in one room, all of them at an engineering offsite.
I want you all to install Kubernetes, but you can't use any scripts. And remember, some of them are Distinguished Engineers and Principal Engineers. Some of them worked on Borg. Some of them are the original creators of Kubernetes itself.
And it was so fun to watch them struggle because it's like: do we install Docker first? What version of Docker? Can we put this on Ubuntu? Or does it need to be Red Hat? An hour goes by, teams of four are like, nah, man, this doesn't work.
I was like, great you all can stop. I'm going to show you how I would do it. And of course, I know how to do this: I get to prepare, right? So it’s not a knock against them. I'm just like, all right: ‘Debian, tune the kernel this way, put Docker on there, put etcd, put the API server, put all these things. There you go. That's how you do it.’ I mean, of course you had to prepare, of course.
And so the question then was, from an engineering perspective, how will we make this better? And then people were like, well, if we had OS packages, this could have been `apt-get install`, and we could have just used local machinery. I was like, that's a good idea. Someone was like, we will make that happen.
And so it was that empathetic engineering that helped me make a huge impact on cloud because I can go to every team, every org, and instead of guessing what their roadmap should be - given someone who would spend time in the field, given someone that had this enterprise background and hands-on experience across lots of tooling - I knew where people were coming from.”
Notion didn’t have a board until two years ago.
Becoming cash-flow positive early allowed us to raise several rounds of financing without diluting ourselves too much or giving up board seats along the way.
That gave us a rare opportunity: to build our board from scratch, much like you would build an executive team.
Over the past two years, @ivanhzhao and I met with some of our heroes. We’re delighted to share that Jonathan Chadwick, Gretchen Howard, @gradypb, @chrispa, and @pdhsu have joined @NotionHQ's board of directors. (Welcome y'all!)
I spoke with @alexrkonrad to share what we learned through the process. Hope it’s helpful if you ever decide to do this for your own company.
Imagine you had the energy, metabolism, and mental agility of your younger self - without the aches and pains that come from aging.
That’s what we’re attempting to build at @NewLimit and it will be one of the most important achievements in human history ever if it works.
We're on the cusp of this being tractable given the rise of AI to test more hypotheses in-silico, along with the rapidly falling cost of single cell sequencing, etc.
We announced our Series C and upcoming human clinical trials this week, so still a long, long way to go, with many risks. But with hard work we've got a shot at making this a reality.
matches my experience, we have deployed chinese models for a bunch of tasks for our clients
they provide a decent output for the cost
and most of them are self hosted, so no issues about data leaving the premises!
Today, @i_am_holt becomes @ElevenLabs Field CTO - working side-by-side with customers around the world to bring frontier AI into production.
Alex joined as one of our earliest employees and has helped build our products, deployment function, and most of all, the culture as we’ve grown to over 500 people.
He represents the best of ElevenLabs - always running toward the hardest problems, helping others, taking ownership, and operating with exceptional integrity. I’ve known Alex for nearly a decade, and one thing hasn’t changed: he keeps raising the bar for himself and everyone around him.
We are thrilled to have him take on this role as we continue building the next chapter of ElevenLabs!
Incredible because developers are already doing this
- Building fake features
- Running useless CI checks
- Creating markdown plans files
- Tracking lines of code produced
a whole bunch of companies that had good primitives but never figured out DX just got saved by AI
i'm using all these things that were too rough to use before
SIPRI report suggests that Nuclear-armed states ramped up arsenals in 2025
China: expanding its nuclear arsenal faster than any other country
India: slightly expanded its nuclear arsenal
Pakistan: continued to develop new delivery systems & accumulate fissile material
it's unclear if tech people yet realize that perspectives on ai usage differ dramatically depending on if you are token rich or token poor.
the idea of looping comes from a place of incredible privilege.
recommending that someone who works at an ai startup with unlimited token budget try looping makes complete sense.
however, that same idea told to someone with only a $2k/mo token budget would seem completely implausible.
what happens when millions of people start evaluating jobs based on what their token allowance will be? what happens to the longtail of administrative paper pushers that don't adapt? what happens to low throughput artists, engineers, or even lawyers and actuaries that can't be trusted to allocate spend?
every form of individual knowledge worker is going to be evaluated from the perspective of "do i trust this person to allocate tokens effectively?"
there are going to be massive investments into new hiring processes. organizations will need to rearchitect their structures to find orchestrators like Peter
my near term recommendation is to do everything in your power to work somewhere that trusts you to spend tokens.
you're ngmi if you only have $2k/mo to play with.