No log off, How to become an AI Designer, vibe coded portfoliosA roundup on always-on burnout, becoming an 'AI designer,' and portfolios built with vibe-coded tools.
- Always-on culture: 'No log off' pushes back on the expectation that designers stay perpetually connected and responsive.
- AI Designer as a role: The piece maps what it now means to reposition yourself as an 'AI designer' — a title fast becoming its own specialization.
- Vibe-coded portfolios: Designers are increasingly building portfolio sites using AI coding tools rather than traditional workflows, changing what a portfolio even signals.
- Why it matters: Hiring managers and design leads should expect candidate portfolios and self-positioning to look noticeably different than even a year ago.
For design
When reviewing portfolios or job titles, expect 'AI designer' framing and AI-built portfolio sites to become the norm — factor that into how you evaluate craft vs. tool fluency.
Stop using OKLCH lightness for your color scaleOKLCH is great for generating colors but its lightness value doesn't reliably predict contrast.
- The problem: OKLCH's perceptual lightness looks even to the eye but doesn't map cleanly to WCAG/APCA contrast math, so color scales built on it can fail accessibility checks.
- The fix: The piece recommends anchoring palette weights to a contrast-aware metric rather than raw OKLCH lightness values.
- Why it matters: Teams that adopted OKLCH for its nicer color math may have unknowingly baked contrast bugs into their design tokens.
- Bottom line: Worth an audit if your design system switched to OKLCH-based palettes in the last year or two.
For design
Have your design systems team run an accessibility audit on any OKLCH-generated palettes — contrast issues here compound across every surface using those tokens.
Nobody wants a blank page. Nobody touches a perfect one.UX Collective
DesignProduct
A short essay on why people freeze at empty templates but also won't touch something that looks finished.
- The paradox: Blank pages intimidate people into inaction, but polished, finished-looking work makes them equally reluctant to contribute or edit.
- The sweet spot: The implication for tools and templates: leave visible 'unfinished-ness' to invite participation rather than aiming for polish upfront.
- Relevance to AI tools: This explains why AI-generated first drafts — imperfect but structured — tend to get better engagement than blank canvases or fully polished outputs.
- Why it matters: Useful lens for anyone designing collaborative tools or AI-assisted creation flows — the goal is 'good enough to edit,' not 'blank' or 'done.'
How complex systems failA classic framework on system failure — latent flaws, hindsight bias, operator adaptation — reframed for product teams.
- Core idea: Failures in complex systems are rarely one single cause — they're usually multiple small latent flaws lining up, not front-line 'operator error.'
- Hindsight bias trap: After an incident, it's tempting to blame the 'obvious' mistake in hindsight, which obscures the real systemic conditions that made failure possible.
- For product teams: Useful as a postmortem lens for outages, launch failures, or AI-agent mishaps — look for accumulated small gaps, not a single villain.
- Why it matters: As teams ship more autonomous, agentic features, this kind of systems-safety thinking becomes directly relevant to product reviews, not just SRE teams.
For product
Next incident postmortem, resist pinning blame on the last person who touched the system — use this framework to map the latent conditions that let the failure happen.