What does it look like when a lead developer builds his browser around how he actually works?
For Jonathan, it looks clean, structured, and intentional. He’s deep in the code every day, shipping features, reviewing pull requests, and managing systems that require sustained focus.
His setup reflects that. No excess. No wasted space. Everything has a role.
Jonathan’s setup at a glance
Spaces: One primary Space
Apps: GitHub, Jira, Confluence, hosting platforms, Google Workspace tools
Layout: Fully customized modular layout
Favorite feature: Smart Link Handling and app-based organization
A layout that enforces clarity
Jonathan’s setup is built around one decision: keep everything in a single, fully utilized Space.
He tried splitting his work across multiple Spaces. One became overloaded. The other sat empty. Instead of creating clarity, it introduced friction. Tools got lost. Context broke.
So he simplified.
Now everything lives in one place, organized with intent. Dev tools on the left. Supporting tools on the right. Key apps and controls at the top. The omnibox sits centered, keeping navigation predictable.
I find it really nice to look at and everything is just where I want it to be.
That visual order matters more than it seems. When nothing competes for attention, focus comes easier.
The QA engineer who flipped his browser: the case for bottom tabs
Who says tabs have to live at the top? This QA Engineer flipped his browser and found focus in the bottom-right corner. Turns out, efficiency looks better upside down.
Read MoreStructure where it matters, flexibility where it doesn’t
This setup draws a hard line between what stays and what moves.
Apps are fixed. They define structure and don’t shift around. Tabs are temporary. They support whatever task is in progress.
Jonathan used to keep dozens of tabs open at once, most of them impossible to scan.
I was a real terrible tab abuser. I’d have tons of tabs open and never get to see page titles.
Switching to a vertical tab strip changed that. Titles stay visible. Tabs are easier to manage, easier to close, easier to treat as disposable.
They become a working layer instead of a backlog.
Keeping context intact
Most workflows break when links open. Tabs scatter across the browser, and context gets lost.
Here, links stay where they belong.
With Smart Link Handling, anything opened from an app stays inside that app. Confluence links open under Confluence. Everything stays grouped without extra effort.
It’s kind of like tab grouping on steroids.
That one behavior keeps the entire setup organized without adding process.
why layout is the real advantage
The most important part of this setup isn’t a feature. It’s the layout itself.
Every decision, positioning apps, centering the omnibox, aligning elements, reduces friction. You don’t think about where things are. You just move.
Most browsers lock you into a fixed structure. This flips that. The layout adapts to how you think.
Advice for building your own setup
Jonathan’s advice is straightforward.
If your work spans multiple roles or accounts, start with Spaces.
If you want immediate impact, start by customizing your layout.
That second step is where things start to click. Once your browser reflects your workflow, everything else becomes easier to manage.
The Drip
Jonathan gave his setup a name: The Drip.
It started as a visual idea, everything flowing downward across the screen. Over time, it became something more intentional. A layout where everything has a place and nothing gets in the way.
And that’s what stands out. This isn’t about adding more tools. It’s about arranging them in a way that makes work feel natural.
