Building alone what happens when the friction disappears
A month of shipping a backend, design system and three launches solo is a useful gut-check on whether the tools you've adopted are buying you rest or just raising the bar for how much one person should do.
Agentic Systems why speed and ease breed fragile architecture
The warning that agent-assembled systems rot the way unarchitected code always has is worth applying to anything you've let an agent scaffold without review.
Doherty's threshold moves from answer to acknowledgment in AI products
Reframing slow AI as a front-end acknowledgment problem rather than a model problem gives you a concrete lever—fast feedback that keeps users alert enough to catch errors—for any AI feature you're designing.
Thinking Orbsanimated states for what agents do
A tree-shakeable library of agent-state animations (thinking, searching, retrying) saves you from reinventing generic spinners the next time you need to show what an agent is doing.
Figma Weave turns design system tokens into campaign assets
Figma Weave turning design-system components into generative campaign assets shows where governance and generative output are starting to merge, which changes what a systems team is expected to own.
CSS Anchor Positioning enables smooth transitions for resizing form fields
A pure-CSS technique for animating textarea resize is a small, concrete craft upgrade you can drop into any form today without touching JavaScript.
The Index #200 CSS layout, state, scroll animation, and overlap detection
The roundup keeps you current on scroll-triggered animation and overlap-detection patterns worth testing in your next interface pass.
Airbnb's inside-out AI using internal tools to reshape product speed and customer experience
Airbnb's approach of using AI internally first before shipping it to users is a strategy worth citing the next time a client wants AI as a headline feature rather than a velocity tool.
Apple Full Disk Access gets new friction for AI agents
Apple tightening Full Disk Access because of autonomous agents is an early signal that any tool you build with system-level agent access will need an explicit consent flow, not an implicit one.
Amazon Kindle sells back the buttons it removed
Amazon selling Kindle's buttons back as an accessory is a clean cautionary tale for when minimalism strips out something users actually needed for the core task.
Building alone what happens when the friction disappears
A month of shipping a backend, design system and three launches solo is a useful gut-check on whether the tools you've adopted are buying you rest or just raising the bar for how much one person should do.
Open the NN/g piece and check one agent-assisted part of your own stack against its "temporary scaffolding vs designed architecture" test.