I thought something was wrong with my VS Code setup.
Turns out nothing was wrong with VS Code.
It was my brain.
Or more specifically:
my brain had been trained for decades by Explorer UIs.
The Tiny UI Convention I Never Questioned
For years, my folders looked like this:
001_start.md
002_notes.md
003_update.md
...
011_latest.md
Newest files at the bottom.
Why?
Because almost every file explorer since the 90s silently taught us:
Top = old
Bottom = new
I never consciously chose this model.
I inherited it from operating systems.
Windows Explorer.
Finder.
Nautilus.
VS Code.
Everywhere.
And after enough years, the pattern stops feeling like UI design and starts feeling like “reality”.
The Moment I Noticed It
I’m currently building a structured “Brain” system for my projects.
Daily discussions.
Architecture decisions.
Research logs.
Codex files.
Chronological project memory.
The structure itself was fine:
2026-06-03/
001_initial_discussion.md
002_structure_notes.md
003_final_codex.md
But every time I opened the folder, something felt inefficient.
Why was the newest context always at the bottom?
Especially because every other modern information system already solved this differently:
chats → newest first
notifications → newest first
logs → newest first
Grafana → newest first
journalctl → newest first
monitoring dashboards → newest first
timelines → newest first
Modern operational systems prioritize recency.
But file explorers still largely inherit a document-era mental model.
A model optimized for printed paper stacks instead of living information streams.
The Weird Part
When I finally enabled reverse sorting in VS Code:
"explorer.sortOrderReverse": true
my first reaction was:
“This feels wrong.”
Not because it was wrong technically.
Because my brain had been conditioned.
That realization was honestly fascinating.
A single UI convention had quietly shaped how I thought about:
chronology
importance
navigation
recency
workflow structure
information access
for almost two decades.
Then Something Unexpected Happened
After about 15 minutes, the new layout suddenly felt obvious.
My folders now looked like this:
2026-06-03/
011_latest_context.md
010_previous_step.md
009_older_note.md
And immediately:
active work became easier to access
current context became visually dominant
scrolling decreased
cognitive friction dropped
Most importantly:
the explorer now matched how my brain actually works during development.
File Explorers Are Not Neutral
This is the interesting part.
Developer tools don’t just help us work.
They train us.
Quietly.
Continuously.
Over years.
We usually think about programming languages shaping thought.
Or frameworks shaping architecture.
But UI conventions shape cognition too.
And because they are subtle, we rarely question them.
The Bigger Lesson
Sometimes workflow optimization is not about adding tools.
It’s about noticing invisible assumptions.
The defaults we inherited.
The patterns we stopped questioning.
The mental models installed by software we used every day.
In my case, the solution was literally one setting:
"explorer.sortOrderReverse": true
But the interesting part wasn’t the setting.
It was realizing how deeply a tiny design decision from old Explorer UIs had programmed my perception of “correct” chronology.
And honestly?
Now I can’t imagine going back.
Top comments (0)