🅰️ Senior Angular Engineer | Teacher | Builder Building https://xitter.cf/t.co/fULXu3EzsD 🎨 My templates: https://xitter.cf/t.co/qEdYR8ztjq

Karachi, Pakistan
Joined August 2020
Zoaib Khan retweeted
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
331
409
145
5,588
787,546
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.
28
28
1
208
11,780
Zoaib Khan retweeted
Elon Musk
@elonmuskSep 23
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
1,564
2,308
155
27,257
41,549,764
#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…
3
25
2
184
8,432
Introducing /visual-plan - a skill to generate rich, visual plans for Claude Code and Codex. Plan mode in Claude Code is incredible. But I always find my eyes glazing over when it gives me this huge markdown essay in my terminal. I found I can make much better visual plans with reusable components. So I made a skill called `/visual-plan`. It generates plans as MDX with visual, interactive components. Diagrams, interactive API specs, schema design changes, annotated code, and even pan and zoomable wireframes. So for any UI work, you can look at a wireframe first, comment on it, iterate, and then have the agent work. I’ve found this to be a much more intuitive interface for reasoning about what the agent is doing. It’s somewhat inspired by that popular post about how HTML is better than Markdown. But HTML can be slow and verbose to write. And it doesn’t look good checked into a repo. This has really made me feel like humans and engineering are entering a new abstraction phase, where we reason about things at the plan level. As long as the plan is good, agents are getting more and more reliable at executing on it. Almost to the degree that we trust the C compiler to compile to assembly reliably. Plans are the new intermediate representation. I also made a skill for the reverse of this, called `/visual-recap`. After the agent works, it gives you a recap of everything it did. Same idea: wireframes, interactive API specs and diffs, schemas, annotated code, etc. So now when you’re reviewing what the agent did for you, or looking at a pull request of somebody else’s code, you can see a visual recap instead of just reading a wall of text. It’s all free and open source. You can find it on my GitHub. Will link to it in the reply because we all know how dumb these algorithms are with links.
83
179
11
1,787
126,850
Zoaib Khan retweeted
Matt Pocock
@mattpocockukJun 5
A context engineering metaphor I've been playing around with: - Primary source: the source of truth. Raw data. Transcripts. Code. - Secondary source: one step removed. Summaries. Compactions. Documentation. For instance, compaction takes a primary source (the conversation history) and turns it into a secondary source (the summary). This is lossy, but means the secondary source can fit into a smaller space. If you want to know what your codebase does, your code is a primary source. Your docs are a secondary source. Loading primary sources into context is expensive, but provides richer context. Secondary sources are cheaper to load into context, but may be information-lossy. Any context engineering will involve managing the tradeoffs between both.
45
20
2
476
31,405
Zoaib Khan retweeted
I empathize with this. What helped me turn a corner: I focus on the things I've gained: I rarely get stuck anymore. I don't have to type tricky syntax. I can improve UX faster than ever. I can easily automate tedious tasks. I don't have to manually look things up. I have a new "pairing" partner that's always available. I can implement and compare multiple options quickly. I can try big ideas that were previously out of reach. I can use the best tool for the job instead of the one I know best.
Replying to @housecor
All of the the agentic stuff makes me sick. I've been doing dev since 2004 and this is making me want to find another career. This is no longer software dev and I want no part of it.
11
5
115
12,782
Zoaib Khan retweeted
Matt Pocock
@mattpocockukMay 21
You asked for it, so here it is: a deep-dive on my new /handoff skill. It's an alternative to /compact that gives you WAY more flexibility with your context window. - Think of an idea, handoff to another agent to implement - Grill, handoff to prototype, handoff BACK Enjoy:
43
68
12
1,174
103,855
Zoaib Khan retweeted
Cursor
@cursor_aiMay 18
Introducing Composer 2.5, our most powerful model yet. It's more intelligent, better at sustained work on long-running tasks, and more reliable at following complex instructions. For the next week, we’re doubling the included usage of the model.
905
1,285
976
13,091
20,291,268
Zoaib Khan retweeted
Matt Pocock
@mattpocockukApr 23
A talk I gave a few weeks ago. Software fundamentals matter more than ever. Here's why: youtube.com/watch?v=v4F1gFy-…
37
142
33
1,307
318,036
Zoaib Khan retweeted
OVERRATED: running tons of agents in parallel; working on too many things at once; perpetual context-switching; opening lots of low-quality PRs that may never land. UNDERRATED: using one or two agents at a time; focusing on the task in front of you; thinking deeply; finishing stuff; making your code works in prod.
220
389
83
4,927
248,480
Zoaib Khan retweeted
This little illuminated dragon is very happy about Pretext. He's too busy having fun to care about people's "hot takes" on how "it's not that special." (This little dragon also only works on desktop right now but maybe I'll do mobile later) illustrated-manuscript.verce…
Cheng Lou
@_chenglouMar 28
My dear front-end developers (and anyone who’s interested in the future of interfaces): I have crawled through depths of hell to bring you, for the foreseeable years, one of the more important foundational pieces of UI engineering (if not in implementation then certainly at least in concept): Fast, accurate and comprehensive userland text measurement algorithm in pure TypeScript, usable for laying out entire web pages without CSS, bypassing DOM measurements and reflow
403
4,694
309
41,499
2,088,547
Zoaib Khan retweeted
Build the thing that feels too ambitious. If you're using agents to do exactly what you were doing before - just faster - you may be thinking too small. Ambitious is the right size side-project.
Cheng Lou
@_chenglouMar 28
My dear front-end developers (and anyone who’s interested in the future of interfaces): I have crawled through depths of hell to bring you, for the foreseeable years, one of the more important foundational pieces of UI engineering (if not in implementation then certainly at least in concept): Fast, accurate and comprehensive userland text measurement algorithm in pure TypeScript, usable for laying out entire web pages without CSS, bypassing DOM measurements and reflow
26
45
6
478
68,342
What happens to your codebase when you stop reviewing your agents' output
155
153
56
2,802
477,130
Zoaib Khan retweeted
But what if you want to customize Angular Material Components using design tokens? I've got you covered as well - with 33 components and close to 901 tokens - change any of them and see the result in real time! Early access live now: materialthemebuilder.com
1
1
64
If you’re feeling behind on AI, do two things: First, open Claude and tell it everything about your job. Everything you’re responsible for. All the tasks you do throughout the week. Then ask for ideas on how you can start using AI to do your job. Second, at least once a week, ask Claude what’s new in tech and AI. Ask about what new tools people are talking about on social and tech media. Then go play around with those tools.
85
492
11
6,433
496,823
Zoaib Khan retweeted
Introducing Agent Skills for Firebase 🔥 Agent skills are specialized instructions you can give to your favorite AI agents to help them better understand Firebase and then execute tasks more effectively. This means more accurate code, fewer token usage, and more money saved 💰
18
56
5
407
31,377
Zoaib Khan retweeted
Debugging just got a major upgrade. We’ve officially launched Resource Visualization in Angular DevTools. Now you can gain even deeper insights into your app's lifecycle and dependencies directly in your browser. See it in action and check out the details here: github.com/angular/angular/p…
7
58
5
328
26,534
Zoaib Khan retweeted
Congrats to the Vercel team for getting this out! Hashbrown has been doing this for 9 months, with a better dev experience around streaming props into components. Check it out: hashbrown.dev
Glimpse of a world of fully generative interfaces. AI → JSON → UI: github.com/vercel-labs/json-…
25
19
2
385
85,079
Zoaib Khan retweeted
✨ An AI-based Form Builder in Angular? So I had a crazy idea to add AI to my Dynamic Form Builder App in Angular - so that users could let the AI design great looking forms for their users. And it turned out pretty nice! Video soon on my channel buff.ly/mbF3v3U
1
165