I've found mostly the opposite. Some well arranged windows are quite a nice anchor, I'm working on what's there in front of me. It's like bowling with bumpers in place, instead of the ball going in the gutter, the structure keeps it in the lane. I've found it necessary to devote time to cleaning and clearing windows, and sometimes I forget what's going on, and as I'm closing out the windows because I forgot what was going on, oh! there's this half finished thing that I actually really want finished.
What am I working on, what's in progress? The work space is the map. The terrain is changing as the task progresses, and so must the map, but the map is useful, even if it takes a bit of redrawing here and there.
The desktops (multiple, 3-7) are the map of the work. Part of the work is keeping the map accurate, not wadding it up and throwing it in the trash.
I suppose different things work for different people, but I started with the suggestion here and came around to skillful use of space as the work map itself.
Cleaning and updating are continuous, not a 'big bang' clear-the-desks event, mostly. But if it's not continuous, the big bang is probably better.
Some spots are problem spots, like digital notebooks, desktop icons. When I notice a problem spot, I create a recurring task to remove one X per week, or in some of the worst cases, one X per day. I have a rule of clearing out the oldest two days of email each day. I miss some days if I'm busy, but on average rate out = rate in, because I will always catch up within a day or two applying the rule that the oldest two days of email need eviction (make a task out of it, archive it, whatever) every day. Rate out = rate in
Every day I work on my main project, I clear my desk completely, take out a small notepad and write my overriding goal, and my next step goal, and then make a list of tasks for that next step goal.
Then I work.
Writing the major goal every day is important to not let sub-goals overshadow it. Writing the immediate goal every day is important because together the two goals create a very clear direction of action with a clear next step.
I have my screen mounted on the wall, and have side end-tables for pens, papers and notes I need, etc. so my desk is absolutely clear.
My desk is a half circle, but not that deep, because that optimizes the usefulness of the surface for work (not storage).
Alas, I think it is far more likely that there is no secret to any of this. Different strokes will arrive at the same place for a lot of people. All the more true for things that are even remotely creative in nature.
Not to say that routine and form can't get results. It is hilarious how much of the current fascination with LLM writing can be summarized by "actually filling out a routine template will satisfy a ton of requirements." People that are surprised with how well some output works, but would have scoffed at filling out a lot of boilerplate in previous technologies.
So, yes, try it. But do not become attached to it. If it works, rejoice in that. But do not count on it always working. If it stops for a time, feel free to leave it for a time.
But I will loose it all, that's why you should bookmark everything, have terminal bookmarks of paths, use git worktrees to allow leaving workspace messy. Use a lot of notion docs, .md docs, notebooks. Places where you organize stuff, so that you can come back easily when you need it again.
A running txt file for each project/work capsule has been wonders. Then common txt files for anything you learned or, things you need to learn, notes/todos, etc.
I think I would be half as productive as I'd like without this.
Yes, I do believe you own the correct answers - however, can you make a long form blog post about this and share it on Hacker News? We need the rest of the information.
My room should be messy when I come back to it - how else would I find anything if it wasn’t where I left it?
I started working on a task management app that could handle the massive amounts of context switching I do on a daily basis - aggregated over slack, iOS reminders, Jira, linear, and obsidian... I'm glad I'm not alone in having such crazy environment.
When I write book chapters I write, throw away, write, throw away. Mostly with no a-priori outline
But eventually I get to a point where all the failed attempts crystallize and it flows out of me start to finish in one sitting. Every piece of knowledge from those failed attempts crystallizes into one gestalt of how it’s supposed to be.
Those final “easy” 20 pages always come after 100 pages of discarded, frustrating, exploratory work that feels like it’s going nowhere.
Having the right context is far more effective. Context-switching cost is a major component of procrastination. At least for development work, having the right set of tabs open, the right project loaded in the IDE with the right console windows open is far better than "Nothing".
I think that's sort of what I got from the article - open the right tools for what you're actually working on, not everything you might need for all the tasks in your backlog.
I have a system for electronics projects where a new project gets a labeled container to store extra parts, papers, spare PCBs, weird cables I might need later...
It works pretty well, especially when I want to take a project to a meetup.
Unfortunately, I also have a bin labeled "Projects".
I believe we clutter our workspaces because we suck at keeping iterations short. We always want to add one more feature, tweak one more thing, etc.
Eventually, some external pressure (boss, client, IM, whatever) causes us to open a second context simultaneously. Then it happens with a third, a fourth, etc
This is happening because the world is expecting shorter and shorter time to results due to better tooling in the last 10 years, but most have not figured out that all the LLMs and agents in the world won’t shorten the loop, only the person using them can do that.
I find that for any given problem, if I don’t see results in 30 minutes, it’s time to stop that problem and likely reshape it. If I don’t actually get the result in 90-120 minutes, I’m doing something wrong.
Every morning I close all work browser tabs from prior day. 99% of them I don't need again/can just reopen if I need. The 1% I'll note on a todo list or keep open somewhere.
This is my focus protocol. Whenever I find myself having trouble trying started on a task, I create a new desktop and open windows related to the task only. DnD on. Pick a next step. Execute.
Um, I guess this might useful to some number of readers, but I don't think it's universal and I don't think it's a secret—more like its one of a few dozen pithy focus hacks that regularly make their way through the blogosphere and social media for those interested in "productivity".
To try my hand at reductive advice, I would say this: know your strengths and what work you do has the most value. The structure exists to serve the work and not the other way around. Habits and processes can serve the work, but can quickly become a form of procrastination for certain types of personalities. Reading about productivity on the internet will not generally make you more productive. Only through honest self-reflection can you actually improve your personal productivity and impact.
Meh. This just sounds like all the interface theory stuff we users have to deal with, where useful things are removed in favor of a 'clean' and empty interface that makes you work harder to get your actual work done.
Then there's Adobe who remove features to add feature and justify it's next version; or clones it into a separate product so they can justify it's next subscription rise; or moves it into a different product so they can justify it's subscription expansion.
Yup been doing this for a while it works great, and really forces the work onto the organizational layer and search layer. Now if only I could be better at that.
The end of every night should start with an empty page
and then start every morning with an empty page
It's pretty simple.
As a data hoarder something like onetab is amazing, there is still a lot of room for improvement though in browser ergonomics, session resets that force you to log back in and refind your place, it's nice to see some tools like data bricks that will at least let you reauth in a new tab.
So I'm one of the people who shuts down their computer at the end of the day and starts fresh. I don't use any type of session resume at the OS level or in the browser, I don't like it.
But! I've learned to harness the power of ending the day without complete closure. I stop work when I know the next step I'm about to do fully. Then the next day it's completely obvious what to start with, and I'm back in the flow without procrastinating as much.
It took some attempts to get comfortable with this; NOT finishing can be kind of excruciating if you're not build for work/life separation. But once I learned to delay my gratification in this regard, I found it set me up for many other things that require daily habits. I also balk much less at "this will take daaaaays" scenarios in general. I'm more comfortable now with things that stretch over longer periods.
I've found mostly the opposite. Some well arranged windows are quite a nice anchor, I'm working on what's there in front of me. It's like bowling with bumpers in place, instead of the ball going in the gutter, the structure keeps it in the lane. I've found it necessary to devote time to cleaning and clearing windows, and sometimes I forget what's going on, and as I'm closing out the windows because I forgot what was going on, oh! there's this half finished thing that I actually really want finished.
What am I working on, what's in progress? The work space is the map. The terrain is changing as the task progresses, and so must the map, but the map is useful, even if it takes a bit of redrawing here and there.
The desktops (multiple, 3-7) are the map of the work. Part of the work is keeping the map accurate, not wadding it up and throwing it in the trash.
I suppose different things work for different people, but I started with the suggestion here and came around to skillful use of space as the work map itself.
Cleaning and updating are continuous, not a 'big bang' clear-the-desks event, mostly. But if it's not continuous, the big bang is probably better.
Some spots are problem spots, like digital notebooks, desktop icons. When I notice a problem spot, I create a recurring task to remove one X per week, or in some of the worst cases, one X per day. I have a rule of clearing out the oldest two days of email each day. I miss some days if I'm busy, but on average rate out = rate in, because I will always catch up within a day or two applying the rule that the oldest two days of email need eviction (make a task out of it, archive it, whatever) every day. Rate out = rate in
Every day I work on my main project, I clear my desk completely, take out a small notepad and write my overriding goal, and my next step goal, and then make a list of tasks for that next step goal.
Then I work.
Writing the major goal every day is important to not let sub-goals overshadow it. Writing the immediate goal every day is important because together the two goals create a very clear direction of action with a clear next step.
I have my screen mounted on the wall, and have side end-tables for pens, papers and notes I need, etc. so my desk is absolutely clear.
My desk is a half circle, but not that deep, because that optimizes the usefulness of the surface for work (not storage).
This kind of daily goal setting reminds me a lot of this podcast, if of interest. https://podcasts.apple.com/us/podcast/invest-like-the-best-w...
Alas, I think it is far more likely that there is no secret to any of this. Different strokes will arrive at the same place for a lot of people. All the more true for things that are even remotely creative in nature.
Not to say that routine and form can't get results. It is hilarious how much of the current fascination with LLM writing can be summarized by "actually filling out a routine template will satisfy a ton of requirements." People that are surprised with how well some output works, but would have scoffed at filling out a lot of boilerplate in previous technologies.
So, yes, try it. But do not become attached to it. If it works, rejoice in that. But do not count on it always working. If it stops for a time, feel free to leave it for a time.
Absolutely. "One size fits all", doesn't. Doesn't even fit one, all of the time.
But I will loose it all, that's why you should bookmark everything, have terminal bookmarks of paths, use git worktrees to allow leaving workspace messy. Use a lot of notion docs, .md docs, notebooks. Places where you organize stuff, so that you can come back easily when you need it again.
A running txt file for each project/work capsule has been wonders. Then common txt files for anything you learned or, things you need to learn, notes/todos, etc.
I think I would be half as productive as I'd like without this.
Yes, I do believe you own the correct answers - however, can you make a long form blog post about this and share it on Hacker News? We need the rest of the information.
My room should be messy when I come back to it - how else would I find anything if it wasn’t where I left it?
I started working on a task management app that could handle the massive amounts of context switching I do on a daily basis - aggregated over slack, iOS reminders, Jira, linear, and obsidian... I'm glad I'm not alone in having such crazy environment.
When I write book chapters I write, throw away, write, throw away. Mostly with no a-priori outline
But eventually I get to a point where all the failed attempts crystallize and it flows out of me start to finish in one sitting. Every piece of knowledge from those failed attempts crystallizes into one gestalt of how it’s supposed to be.
Those final “easy” 20 pages always come after 100 pages of discarded, frustrating, exploratory work that feels like it’s going nowhere.
Also a deadline helps.
Having the right context is far more effective. Context-switching cost is a major component of procrastination. At least for development work, having the right set of tabs open, the right project loaded in the IDE with the right console windows open is far better than "Nothing".
I think that's sort of what I got from the article - open the right tools for what you're actually working on, not everything you might need for all the tasks in your backlog.
I have a system for electronics projects where a new project gets a labeled container to store extra parts, papers, spare PCBs, weird cables I might need later...
It works pretty well, especially when I want to take a project to a meetup.
Unfortunately, I also have a bin labeled "Projects".
My work day starts with "what must I accomplish today?"
Then I tackle that list.
Sometimes the list changes.
"Focus work" happens as pressure vs desire mingle.
The real question is "what is expected of me in the next four hours?" And suddenly my work is structured.
I believe we clutter our workspaces because we suck at keeping iterations short. We always want to add one more feature, tweak one more thing, etc.
Eventually, some external pressure (boss, client, IM, whatever) causes us to open a second context simultaneously. Then it happens with a third, a fourth, etc
This is happening because the world is expecting shorter and shorter time to results due to better tooling in the last 10 years, but most have not figured out that all the LLMs and agents in the world won’t shorten the loop, only the person using them can do that.
I find that for any given problem, if I don’t see results in 30 minutes, it’s time to stop that problem and likely reshape it. If I don’t actually get the result in 90-120 minutes, I’m doing something wrong.
Every morning I close all work browser tabs from prior day. 99% of them I don't need again/can just reopen if I need. The 1% I'll note on a todo list or keep open somewhere.
This is my focus protocol. Whenever I find myself having trouble trying started on a task, I create a new desktop and open windows related to the task only. DnD on. Pick a next step. Execute.
Um, I guess this might useful to some number of readers, but I don't think it's universal and I don't think it's a secret—more like its one of a few dozen pithy focus hacks that regularly make their way through the blogosphere and social media for those interested in "productivity".
To try my hand at reductive advice, I would say this: know your strengths and what work you do has the most value. The structure exists to serve the work and not the other way around. Habits and processes can serve the work, but can quickly become a form of procrastination for certain types of personalities. Reading about productivity on the internet will not generally make you more productive. Only through honest self-reflection can you actually improve your personal productivity and impact.
Meh. This just sounds like all the interface theory stuff we users have to deal with, where useful things are removed in favor of a 'clean' and empty interface that makes you work harder to get your actual work done.
Then there's Adobe who remove features to add feature and justify it's next version; or clones it into a separate product so they can justify it's next subscription rise; or moves it into a different product so they can justify it's subscription expansion.
Why does a personal blog need a comically large cookie spam popup?
Yup been doing this for a while it works great, and really forces the work onto the organizational layer and search layer. Now if only I could be better at that.
The end of every night should start with an empty page
and then start every morning with an empty page
It's pretty simple.
As a data hoarder something like onetab is amazing, there is still a lot of room for improvement though in browser ergonomics, session resets that force you to log back in and refind your place, it's nice to see some tools like data bricks that will at least let you reauth in a new tab.
So I'm one of the people who shuts down their computer at the end of the day and starts fresh. I don't use any type of session resume at the OS level or in the browser, I don't like it.
But! I've learned to harness the power of ending the day without complete closure. I stop work when I know the next step I'm about to do fully. Then the next day it's completely obvious what to start with, and I'm back in the flow without procrastinating as much.
It took some attempts to get comfortable with this; NOT finishing can be kind of excruciating if you're not build for work/life separation. But once I learned to delay my gratification in this regard, I found it set me up for many other things that require daily habits. I also balk much less at "this will take daaaaays" scenarios in general. I'm more comfortable now with things that stretch over longer periods.
"Some people say a cluttered desk is the sign of a brilliant mind. Hogwash. A cluttered desk is the sign of a lazy mind." —Tim Bryce
He didn't do any actual proper engineering; might take advice from politicians on engineering next
Tidy desk, tidy mind. Empty desk, empty mind.