I like Cursor's design mode for this, but for it to be fast, the model has to be fast as well. I'd love to be able to batch tweaks though in one go - since I usually want to tweak multiple things at the same time
codebases have always contained slop. we have always been okay with this because code rarely needs to be perfect, outside of mission critical "hard" (eg embedded) software.
swe is a unique form of engineering because you're often building something that constantly evolves and is almost organic - user tastes change, your mental models evolve, and features come and go.
admittedly, i and many others who've been coding for a long time were initially (like back in 2024) skeptical that agents would write production code. "but what about all the slop that would enter our beautiful codebase?".
well, even before, we had human slop, and there was a lot of it! if we're being truthful, most people call "code i didn't write" slop. the reality is that 99% of people (i include myself in that number) don't even know what Good Code looks like, let alone be capable of writing it. i would propose that Good Code is:
• correct
• bug free
• fast and cost efficient to run
it has always been exceedingly difficult and expensive to write truly Good Code, because for the longest time (maybe @bendlang will change that), code was not something you could cheaply and formally guarantee to have all 3 of these properties. this is why writing hard software is much more difficult and expensive, because depending on the use case, you may only get one chance and so you have to be right from the start.
but the vast majority of software we use does not need to be Good Code to provide value to users. in fact, it is very likely that most software we use is not formally verifiable! we accepted some bugs in exchange for velocity and progress, so we rely on tests and o11y instead and have adopted a more incremental approach. this is a good thing!
agents help us move faster, and if you're open to the idea, are capable of helping us write better code. it won't be Good Code (that is still expensive), but it is likely to be much better on average at scale.
the new craft of swe is to figure out how to do this. it's your job now! if your productivity with and without agents is not significantly different, you're doing something wrong. but it's not too late to embrace it and use it as an opportunity to learn a whole new skill tree
Zoaib Khan retweeted
Instructions are a last resort.
Want to enforce a coding standard? Configure or create linting rules.
Want to avoid the LLM copying an existing anti-pattern? Refactor the bad pattern and make it a build error if it happens again.
Want to explain a confusing or insistent design? Fix the design and be consistent (it’s easier than ever with AI!)
Want to run a process after each file edit or when the model stops? Use a hook.
Want to describe a process like opening a PR or doing a code review? Create a skill.
Instructions are rarely the best option.
They’re “soft”.
They bloat context.
They’re often ignored.
And they often paper over problems.
Fix the root causes. Use deterministic tools.
Each time I see the agent make a mistake I ask, “how can I make this mistake impossible?”
Instructions are just a suggestion. The techniques above create *certainty*.
That’s why instructions are a last resort.
I have the same sentiment. While models might not be there yet, but they will eventually from the trajectory.
We're finding ourselves moving up the abstraction ladder bit by bit every day and it can be disorienting.
I try to focus on the new possibilities that offsets this doom
Replying to @ThePrimeagen
I've been reflecting on this. I'm generally a very optimistic person, but lately I've been feeling a strange sense of sadness that coding has been "solved".
I can, and have, made many caveats to "solved"... but I also know that in five years none of them will matter. It will be solved.
Building things is still fun, but a different kind of fun. It doesn't activate the same parts of my brain as trad coding did.
I think it's okay to mourn the thing we loved doing being different now. Software was the first job to go through the five AI stages of grief, which means we're also some of the first to internalize that this will happen to many other jobs.
It was the best of times, it was the worst of times.
New Grok @Bot features!
Here's what's new in Grok @Bot this week
0:08 Voice calls and voice memos
0:35 1Password vault for Grok Bot
0:53 Inline forms
1:07 Inline drafts for email and Slack
1:31 Account switching
1:40 Route traffic through your desktop
What's new in Grok Bot - Sept 23, 2026
What's new in Grok Bot - Sept 23, 2026
I don't use the "official" plan mode myself, but I do come up with an implementation plan based on grilling session and coding standards.
That has been enough for me
Mental note: Use this on the material theme builder.
I find the latest models write a lot of unit tests. Most of them restate the code they were written after, so they always pass and catch almost nothing. They run fast, but they break on every refactor and the agent burns time fixing tests instead of the feature.
The prompt I used to clean out mine, adopted from Ansh is:
"This repo is full of low-signal unit tests. Delete every one that wouldn't catch a real bug our E2E tests miss. Fan the work out across parallel subagents.
Then add these rules to AGENTS.md so future agents stop writing them.
- Never write unit tests after you write code.
- Highly prefer E2E tests as the sole testing mechanism. Use them to verify complex features work. At the end of E2E tests, produce a verifiable and repeatable artifact.
- If you must test a system in isolation, first write down all the ways it could fail, then write the code."
Zoaib Khan retweeted
#Angular 22.2 is out!
It seems everything is AI nowadays, but it is still so important that we have frameworks. They compress so much wisdom, best practices and hard work that no AI can simply guess.
github.com/angular/angular/r…
Growing more and more fond of @cursor_ai Projects and @bot as I get to use it more on my own projects.
It's so freeing to have shared context about BIG projects in one place rather than passing things around here and there between different agents.
Simplifies work a lot!
I haven't been using PR's that much because I usually work as a solo developer, but I'm warming up to it. It's not necessary to use it of course, you can very well ask the cloud agent to just use a feature branch and push to it instead.
Must watch!
here's how i shipped 2,500 PRs last month to production
this was originally supposed to be for Cursor Compile in London. i couldn't make it since i was livestreaming for Grok @Bot Galaxy so i'm making it available for free here on X! watch it on 2x speed, i talk slowly
✨ Added a "Linear" inspired built-in theme to the Angular Material Theme Builder.
And in the process I'm also building a repeatable process to add such themes using Grok Bot.
Also giving me ideas - can we generate themes with AI + a reference image?
buff.ly/aMpERNZ
So here's a process that I'm trying to "templatize" in @bot :
- Ask the agent to choose a target theme
- Get its seed colors for basic color theme
- Get sources where we can look at its components
- Map both above to material design tokens
I'm surprised it works quite well!
✨ Angular’s official Agent Skills are the antidote to outdated AI Angular code — this video covers them end to end!
I start with the basics of angular-new-app and angular-developer, then we scaffold an Expenses app and run a real code review
youtu.be/YMzRMWS0WhA











