Cut through the noise on the latest web development tools, libraries, and frameworks.
Joined April 2025
- Tweets 313
- Following 11
- Followers 68
- Likes 109
39 Photos and videos
Build with AI by Packt retweeted
Jun 11
🚨 GIVEAWAY ALERT 🚨
Enter to win 3 AI bestsellers from Packt. 🤖📚
3 winners will each receive PDF ePub copies of all 3 books. 🏆📄📱
Giveaway closes June 30. ⏰ Winners announced July 2. 🎉
👉 landing.packtpub.com/giveawa… 👈
2
4
194
🚨 GIVEAWAY ALERT 🚨
✨Enter to win 3 AI bestsellers from Packt.✨
📚3 winners will each receive PDF ePub copies of all 3 books.
⏰Giveaway closes June 30. Winners announced July 2.
Enter now 👉 landing.packtpub.com/giveawa…
2
1
75
We tested the viral claude.md workflow across real production projects.
Some rules made AI dramatically better.
Some quietly broke projects.
And one critical rule was completely missing. 🧵
1
1
1
95
7/ The most important missing rule we added:
“Always preserve and create the essential project structure required for a maintainable, production-ready codebase.”
This changed everything.
1
10
8/ The best AI workflows don’t come from blindly copying prompt templates.
They come from understanding: • what to KEEP • what to DELETE • what to ADD
Better rules → better code.
10
Are you still a “Traditional” SWE?
Or are you becoming an AI-Native SWE?
We analyzed 100 recent software engineering JDs.
Here are the 6 skills separating future-proof developers from the rest 🧵
1
3
42
6/ Performance Tuning
Traditional SWE:
Time complexity, space complexity, and memory profiling.
AI-Native SWE:
Token economics, context window efficiency, and cost-aware AI system performance.
The shift:
Token optimization is becoming the new Big-O for AI-native applications.
1
1
35
Traditional SWE skills still matter.
But AI-native SWE skills are becoming the edge.
The future-proof developer won’t just write code faster.
They’ll know how to architect, guide, validate, and optimize AI-assisted systems.
The AI-native era is already here.
1
13
1/ Claude Code vs Codex is the wrong debate.
The real question is:
Where does each one fit in a developer workflow?
After a few tests, the answer became obvious 👇
1
1
3
148
8/ Cost matters too.
Claude spends more because it reasons more.
Codex is leaner for repetitive work.
So the practical split is:
Codex for volume. Claude for value.
1
1
39
9/ Final verdict:
Don’t choose one.
Use Claude Code for: Planning, architecture, refactors, unclear problems.
Use Codex for: Execution, tests, fixes, PRs, repeatable tasks.
The best AI-native developers will know when to switch.
1
1
52