
Weeklyish AI Engineering nugget: https://teapaw.org/t.co/VG1C5WG5i3 🧪 🚂 Organizing https://teapaw.org/t.co/r5S0ff9d5i & https://teapaw.org/t.co/MSDTORHjMk 🤖 AI navigation at @ClickFunnels since 2023
All over the place atm 🌍🤷
Joined October 2012
- Tweets1.2K
- Following9
- Followers419
- Likes1.3K
Rich Steinmetz retweeted
Tabletist just passed 50 stars on GitHub. Thank you to everyone who tried it and sent feedback.
Next goal: Homebrew's official casks. They take an app at 225 stars when its author submits it, so if Tabletist is useful to you, a star helps.
github.com/igor-alexandrov/t…
Ooops, I think I automated myself out of an amazing 3.5-year ride at ClickFunnels. 😅
Today was my last day and, as with all endings, my first question is: what's next? Which AI-centered team needs someone who enjoys product work, community work, wears different hats (sometimes quite literally), can still read PRs and assess them with a sharp product focus, but lets AI write (and, frankly, often rewrite) the code?
If that sounds like your team, or you know one, I’d love an intro :)
🤖 Made with AI
Rich Steinmetz retweeted
Last week I launched an AI support agent for Overskill named Riley.
6 months ago “good” would have been the equivalent of level 1 support.
Riley has the title VP of Customer Support. “She” will be the entire department.
This is one of the better litmus tests for whether you’re pushing your use of AI enough or not.
Up until maybe six months ago probably the best you could do with AI was pull off something you already would produce, but just doing it a little faster. But now we’re entering a point where the output of working with AI can and should dramatically exceed what you would been able to do before, in a fraction of the time.
The product prototype should not only be fully functional and interactive, but it should probably have meaningfully better features than it would have had before. The engineering architecture should be able to deliver performance gains that you wouldn’t have been able to go after otherwise.
The research for a project should consume every single fact on the subject across every dimension of analysis possible. The business process you implement with AI should operate entirely differently and learn from all its past failures in a way no human could.
We’re unquestionably entering a period where AI will be smarter than us on most axes. Perhaps not on every dimension that matters (intelligence is still very jagged), but at least on enough dimensions that when we combine it with what we’re good at, you get qualitatively different outcomes.
So the simple test is: if you could have done what you’re doing before AI, you’re likely not pushing it enough.
I don't know, man. I've seen a Spanish dude with a newspaper in the sauna. Since then, I think everything is possible.
Why video QA is better than screenshot-based or text-report QA. True story, the bots are gonna lie to you. It's gotten much better over the months and years, but it's still true.
Rich Steinmetz retweeted
Replying to @Kimi_Moonshot
@elonmusk should just buy moonshot as well.. the name fits
If you are one of those engineers who are craving back the art of engineering now that you don't write code anymore (and don't care about it for certain types of products), owning your agent through Pi could restore the spirits. Pi Durable is the next evolution of this: It's separate from the Pi harness right now, but gives your agents a persistence layer to be run (and killed) anywhere anytime.
youtube.com/watch?v=DNDYYHsy…
Rich Steinmetz retweeted
I have over 100 agent sessions running locally. Today I gave them all an MCP to reach me over Telegram. Feels like publishing my phone number on the internet for anyone to call.
If you need to see someone obsessed with loops, in a few minutes, swyx briefly touches on engineering loops, human loops and the highest loop of all loops. 🧠
youtube.com/watch?v=Fva8hFos…
If you are tired of your brain and you would like to fry it one last time, start a few parallel /grill-me sessions. Thank me later.
Makes sense to me, Software Engineering Now == Factory Engineering == Software Making Systems.
youtube.com/watch?v=tUPPVhBB…
I've been paying OpenAI $100-$200 for Codex over the past few months and seem to have accumulated ~$2,100 in credits, which is cool, plus all the resets I'm getting during the month, like 5-6 at least.
So, not complaining, but I noticed that tokens started melting seemingly faster yesterday. Time to pull some agent analytics and see hard proof of what's going on.
I have a bunch of commands that start as a Raycast keyboard shortcut to automatically paste a text snippet I use frequently. If I need to type the same thing 2-3 times, it becomes a Raycast snippet. If I keep using that snippet frequently, it might become a skill or a memory.
That way, I don't spam my skills too much and still give enough room for automation before graduating an idea to something the bots will be able to use autonomously or on demand later.
Mutation testing for Ruby to make your code more bulletproof. Haven't tried, but hearing good things:
davidteren.github.io/mutinee…
If you crave a security layer for your local agents managing credentials, it’s just one reason to check this out! ✨
Eldar: A computing environment for doing serious work with AI. This is my personal system published as a reference. Borrow what you like. Send me feedback!
github.com/benjaminwood/elda…
When do engineers still read articles or watch technical videos if anything can be asked in the magic box and served with some kind of answer these days?
The last time I batch-read technical articles was about a year ago, when I needed to implement an MCP server (it's also when I realized that like 80% of written content was AI slop). Apart from that, I only read from people I trust to allow in my inbox (newsletters), and sometimes I skim some of the relevant aggregators like Ruby Weekly or APIs You Won't Hate.
If I have time to watch a video during my lunch break, I will watch something to understand a new concept, like Jev or software factories, and to see how others have solved what I'm trying to solve right now.
"Without a spec, you'll get a wreck". The wreck, in most cases, is a stuck pipeline: Either the robots need to get back to you to clarify, or they implement things the wrong way, so you have to iterate way more than necessary or start from scratch. (only relevant for critical projects, no need to write specs for your pet project imo)
Prepare for a Rails.Builders rebrand in 2027 then!? Rails Hustlers (a good hustle still going to be important) or Sales on Rails or…
Replying to @RichStoneIO
yeah I feel like both "rails" and "builder" are outdated now.
"rails" - tools don't matter. however "rails" stays relevant as a group of like-minded ppl.
"builder" - building is not the bottleneck. validation, distribution, growth is!! 🚀













