@hobdaydesign Also some playlists play music straight away when you tap them, others bring you into a list of tracks. It’s sometimes quite hard to predict what tapping on a playlist card might do.
Mutually Exclusive, Collectively Exhaustive (MECE) is a useful concept, but overused in UI design. An action or setting should be accessible from anywhere one would reasonably expect it to be.
With our visual rebrand, each element and design choice has a clear purpose rooted in how we want users to feel when building with Windsurf, reinforcing a brand built on flow and momentum.
Let’s take a deep dive into our new visual identity. ↓
We need LLMs everywhere.
We're past the "can we afford it?" phase - LLMs are now fast, cheap, and capable enough to be foundational infrastructure.
Examples of where we should just use LLMs instead of rigid systems:
> CSV imports that auto-format your messy data instead of rejecting it
> Shopping filters that understand "comfortable running shoes under $100" not just dropdowns
> Error messages that explain what actually went wrong in plain English
> Git commit messages generated from your actual code changes
> Customer service that routes intelligently instead of phone tree hell
> User onboarding that enriches profiles naturally vs death-by-form-fields
> Code reviews that explain WHY something is problematic, not just flag syntax
> Expense categorization that knows "coffee with Mike" = business meal
> Travel booking that gets "flexible dates, fewer connections" without 47 clicks
We're shifting from Software 1.0 (anticipate every interaction, code every edge case) to Software 2.0 (understand intent, handle context dynamically).
The question isn't "should we add an LLM here?" anymore.
It's "why wouldn't we have an LLM here?"
I'm excited for a future where LLMs become so foundational, ubiquitous, and well integrated, that people stop perceiving LLMs as unpredictable and experimental, and start seeing them as core building blocks of software.