It's surprising how many devs are trying to overoptimize for productivity with various fancy tools and techniques, when it actually comes down to simple basics. Here is what I rely on as a founder who does a lot of context switching: - a never-ending text file for todos and work journal [0] - calendar for planning (and blocking focus time) - website blocker - turned off notifications [0] https://news.ycombinator.com/…
What website blocker do you use?
Use a work journal
191–200 of 305 posts
Re: Use a work journal
#192I keep a stack. Whenever I am interrupted, I push a task onto the stack. When I finish a task, I pop it from the stack. Each task has an associated journal file. Sometimes I reorder the stack.
Re: Use a work journal
#193Re: Use a work journal
#194I use GitHub Issues threads for this and it works amazingly well. Any task I'm working on has a GitHub issue - in a public repo for my open source work, or a private repo for other tasks (including personal research). As I figure things out, I add comments. These might have copy pasted fragments of code, links to things I found useful, quoted chunks of text, screenshots or references to other issues. I often end up w…
Re: Use a work journal
#195Reminds me a lot of Cal Newport's ideas re: Slow Productivity. He talks a lot about how Context shifts are death for knowledge work and that a lot of offices operate via a "hyper active hive mind" that doesn't allow or value deep work.
I have too many meetings to get anything done. I'll go weeks, or months, without actually doing anything of real value. Eventually it comes to a head and I need to get things done to avoid going crazy. I go on do-not-disturb in our chat app, quit Outlook completely, and turn on a focus mode on my cell phone so people can't even call me. I'll end up working for 8-15 hours straight with no real breaks. I go to the bath…
Re: Use a work journal
#196Earlier quoted context omitted.
> solidify the mental model into a concrete branching of possibilities that is tightly coupled to the specific problem. Your work becomes traversal and mutation of this tree. I wrote a program (used from a CLI, but I mostly use the GUI I developed for it) to do something similar for my own use: https://github.com/lelanthran/frame/blob/master/docs/FrameIn... I use it daily.
It's low-tech, but I've been using notebooks (not too thick, stapled usually). I write a header for each day when I start and then a line or two as I work on tasks and I try to note each time I switch tasks. I keep the notebooks but rarely look at them once they are filled. Maybe once or twice as I switch to a new notebook and then once again when it comes to yearly review time. A couple of times I have rifled throug…
Re: Use a work journal
#197The benefit of journaling is not just reentry, but that you begin to solidify the mental model into a concrete branching of possibilities that is tightly coupled to the specific problem. Your work becomes traversal and mutation of this tree. Several benefits accrue: you begin to see gaps in the tree, and can fill them in. You begin to have confidence in your mental model, recovering the time you used to spend going o…
If I'm working on something particularly complex I basically just do the journaling in a code comment adjacent to what I'm working on. So the first commit may be three lines of code and a huge long winded rambling comment of what I've already tried or thought about. By the time the task is done I've pared away the more speculative/rambling elements of what I wrote, and what's left is typically some extremely well com…
Re: Use a work journal
#198Re: Use a work journal
#199The benefit of journaling is not just reentry, but that you begin to solidify the mental model into a concrete branching of possibilities that is tightly coupled to the specific problem. Your work becomes traversal and mutation of this tree. Several benefits accrue: you begin to see gaps in the tree, and can fill them in. You begin to have confidence in your mental model, recovering the time you used to spend going o…
Re: Use a work journal
#200The benefit of journaling is not just reentry, but that you begin to solidify the mental model into a concrete branching of possibilities that is tightly coupled to the specific problem. Your work becomes traversal and mutation of this tree. Several benefits accrue: you begin to see gaps in the tree, and can fill them in. You begin to have confidence in your mental model, recovering the time you used to spend going o…
> Perhaps the greatest barrier to using it is akin to envy. We see others who apparently do this without written materials, in their head. I think we see this as evidence of intellectual superiority and harbor the doubt that using an aid like a journal means we are somehow lacking in skill or ability. To add to your "this is wrong": These others may have themselves solved the problems we are now trying to solve, like…
The professors were in fact not gods of problem solving, they just had the answers. Not just of the problems they brought along (obviously). But also of the handful of problems we’d tend to invent. Of course, if you really catch them flat-footed, they can provide circumspect and sagely advice, and then quickly check Wikipedia to see if anyone has solved your problem.