🚀 Software Engineer | 6+ Years Experience | Passionate about coding & creating innovative solutions | Sharing new opportunities | Let's connect! 👋
Nigeria
Joined January 2012
- Tweets6.1K
- Following837
- Followers525
- Likes1K
Considering everything we’ve been hearing about AI looking for ways to outsmart humans, writing code human beings won’t understand will be the beginning of an end we don’t want to see.
Now this is amazing
Introducing shadcn/lint. An agent-first linter for Tailwind design systems.
You define what’s allowed. When an agent breaks a rule, the error explains what’s wrong and how to fix it using your components, variants and theme.
There’s a lot you can do with this. Let me show you ↓
github.com/shadcn-ui/lint
👑 Chilo retweeted
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
👑 Chilo retweeted
You won’t believe what astronomical event took place on April 3rd, 33AD. Seriously, look it up
👑 Chilo retweeted
If you are longing for a simpler time that is now gone forever, this video will likely hit HARD…
🥲
Simple rule: after the test, no matter how little the fix is, if you won’t test it properly after it’s deployed, don’t push it. You can do without it.
👑 Chilo retweeted
Add this paragraph to the CLAUDE.md file to turn Claude Code into Claude Teacher. Every project is a lesson to become more technical.
"For every project, write a detailed FOR[yourname].md file that explains the whole project in plain language.
Explain the technical architecture, the structure of the codebase and how the various parts are connected, the technologies used, why we made these technical decisions, and lessons I can learn from it (this should include the bugs we ran into and how we fixed them, potential pitfalls and how to avoid them in the future, new technologies used, how good engineers think and work, best practices, etc).
It should be very engaging to read; don't make it sound like boring technical documentation/textbook. Where appropriate, use analogies and anecdotes to make it more understandable and memorable."
