TJ Dhillon

Professional nap taker. Tap dance with Figma everyday. Write markup and JS like vaudeville in its prime

[TJ Dhillon @_terj]

@joshpuckett @adisingh The best thing at about following you is not just the content, but moments like these where you keep people honest

[Mario Zechner @badlogicgames]

recommended reading. entirely unsurprisingly, vicki also has good takes on agentic coding.

[Steren @steren]

Wow, it actually *is* DOM
(See me using Chrome DevTools to inspect the DOM)

HTML is <canvas> is going to open a new era of web UIs

[Chris Halaska @chalaska]

This echoes a lot of what I’m currently experiencing while implementing AI into our own and clients teams:

[Adrián Mato 🐙 @adrianmg]

The fact that this is considered a hot topic in 2026 is wild. This should have been obvious and the standard from day one

[TJ Dhillon @_terj]

@jamesm @_BoldPolitics I swear this is why we need reactions on Twitter. Thank you @jamesm

[TJ Dhillon @_terj]

@chalaska Here!

[Soleio @soleio]

“Quit drinking cocoa and get thirsty for blood” is a phrase I will repeat for the remainder of my tech career.

Thank you @samhenrigold

[Jakub Krehel @jakubkrehel]

How I Use Shared Layout Animations
https://t.co/Zen0mU7x7j

[shadcn @shadcn]

Every friend I talk to is overworked since AI. Working weekends. Always on their phone prompting. Kinda sad.

[Charly Wargnier @DataChaz]

🚨 You need to see this.

@addyosmani from Google just dropped his new Agent Skills and it's incredible.

It brings 19 engineering skills + 7 commands to AI coding agents, all inspired by Google best practices 🤯

AI coding agents are powerful, but left alone, they take shortcuts.

They skip specs, tests, and security reviews, optimizing for "done" over "correct." Addy built this to fix that.

Each skill encodes the workflows and quality gates that senior engineers actually use: spec before code, test before merge, measure before optimize.

The full lifecycle is covered:

→ Define - refine ideas, write specs before a single line of code
→ Plan - decompose into small, verifiable tasks
→ Build - incremental implementation, context engineering, clean API design
→ Verify - TDD, browser testing with DevTools, systematic debugging
→ Review - code quality, security hardening, performance optimization
→ Ship - git workflow, CI/CD, ADRs, pre-launch checklists

Features 7 slash commands: (/spec, /plan, /build, /test, /review, /code-simplify, /ship) that map to this lifecycle.

It works with:
✦ Claude Code
✦ Cursor
✦ Antigravity
✦ ... and any agent accepting Markdown. Baking in Google-tier engineering culture (Shift Left, Chesterton's Fence, Hyrum's Law) directly into your agent's step-by-step workflow!

`npx skills add addyosmani/agent-skills`

Free and open-source.

Repo link in 🧵↓

[claire vo 🖤 @clairevo]

I’ll say the thing no one is saying: design culture is broken in lots of companies.

Often design teams & designers are the most resistant to change org in the EPD triad, with highly vocal AI opponents, and little skill or interest in the art of campaigning for influence or resources. Won’t hold a number like a PM, not yelled at about timelines like engineering. While I have brought design topics to the board convo, not a single board has pressed me our design talent, strategy, or velocity. Most teams treat design like a tax they don’t want to pay, and those that *do* take a deep interest and want to invest in design get back big “get out of my figma” energy. And if you’re too precious about craft to dirty your hands with the dark art of corporate politics, good luck getting more headcount. If a PM or engineer can get 85% there with tailwind and a dream, you better come to the table with more than “I represent the user.”

Great designers are worth more than almost anyone on the team, and I’ve worked with lots of gems, but this is 0% surprising to me.

[Dylan Field @zoink]

https://t.co/fsYWgHN8ur

[DAN KOE @thedankoe]

https://t.co/FGLYHaRhRq

[Pedro Duarte @peduarte]

The Tailwind paradox is crazy. It's more popular than ever before, used by millions, and basically the default response to your style-related prompts.

Still, its revenue is down by 80%. They had to lay off 75% of staff. Documentation traffic down by 50%.

Chat has quickly became our primary interface for planning, researching, debugging, and building stuff. As a result, the need to go to other resources has significantly decreased.

Who needs to go to docs anymore? I mean, nobody really read them in the first place, right?! Who needs to purchase pre-built templates, when you can just feed a sketch to AI and have it return the built product?

AI is literally replacing people (like @simonswiss), AI is literally making businesses redundant (like Tailwind), and this is literally just the beginning.

I hope they can bounce back and figure out a new business model.

Worth listening to @adamwathan's raw thoughts below

[Hayden Bleasel @haydenbleasel]

how to 10x your output

[Adam Noffsinger @ANoffsinger]

Can't unsee

[Karri Saarinen @karrisaarinen]

The key belief at @linear has always been that the work matters more than the tool.

Now with AI, we approach it the same way. Agents should help you ship, not create more work to manage.

AI to cull duplicates in your backlog.
An agent should submit bug fixes autonomously.
Code reviews should be a breeze.
Make updates about the essense.
AI to fill in missing details and customer requests into something cohesive.

Bring clarity, not more noise.

Not a future where there are agents exist just to clean up after other agents.

AI that prunes, not proliferates.

We want your backlog to shrink.
Your focus to sharpen.
You to ship more, and decide less.

[Dima Belyaev @blvdmitry]

Using liquid glass in Figma for the release post felt like a cheat code ✨

[Ryo Lu @ryolu_]

the 9-9-6 local maxima trap

you can optimize for looking busy, hitting metrics, being “productive” – but you might be climbing the wrong hill entirely.

real breakthroughs happen in the spaces between. when you’re walking and your mind wanders. when you sit with a problem long enough that the obvious solutions dissolve and something deeper emerges. when you have the luxury of thinking “what if we’re approaching this completely wrong?”

my process is simple: i’ll open a Notion doc on my phone and just walk. sometimes for hours. the walking rhythm unlocks something – maybe it’s the bilateral movement, maybe it’s getting away from screens, but ideas start connecting in ways they never do at a desk. i’ll quickly jot stuff down as interesting thoughts pass.

then i come back and just sit with the problem. draw some pictures, build it out a bit. no rushing to conclusions. no pressure to ship something by end of day. just... what is this, really? what can it connect to or evolve into? what would this look like if it were in its most beautiful configuration?

once i see it clearly, execution becomes effortless. the focused bursts where you’re completely in flow – that’s when the real work happens. but you can’t force your way there. you have to earn it with the slow, patient thinking first.

the irony is that this “inefficient” approach ships better stuff faster than grinding 12-hour days. but it requires believing that thinking time isn’t wasted time. that walking isn’t procrastination. that sometimes the most productive thing you can do is to not do.

many teams don’t get this. they need to see keyboards clicking and meetings happening. but the best work – the stuff that actually moves the needle – happens in the flow moments when no one’s watching.