Live data from Hacker News

A trick to reaching flow: Leave your work broken

census.dev

131–140 of 196 posts

Re: A trick to reaching flow: Leave your work broken

#131

Earlier quoted context omitted.

I don’t usually leave notes, I just leave the last thing I looked at in whatever arbitrary failure state it was in, unsaved, with whatever undo history I stopped at. If the errors aren’t immediately obvious, a couple cmd-Zs is usually all it takes to jog my memory and at least start retracing my steps

What editor configuration are you using that saves undo history like that?

Any decent editor if you don't close it/hard power off the workstation.

Re: A trick to reaching flow: Leave your work broken

#132
Maybe off topic, but it's weird to see a post about flow and distraction start with a completely unrelated splash image as many posts do these days.

Are there studies linking this with better recall/comprehension or is it SEO related/purely aesthetic/trendy? It makes the posts signal 'I care about this' a bit more than your old school livejournal text only content, but I suspect in the vast majority of the cases it correlates with superficial and weak content.

Re: A trick to reaching flow: Leave your work broken

#133

Maybe off topic, but it's weird to see a post about flow and distraction start with a completely unrelated splash image as many posts do these days. Are there studies linking this with better recall/comprehension or is it SEO related/purely aesthetic/trendy? It makes the posts signal 'I care about this' a bit more than your old school livejournal text only content, but I suspect in the vast majority of the cases it c…

The photo of a mountain biker is not unrelated, you just aren't aware of how it's related.

Flow is a term used often in mountain biking, and in a similar way to programming and other pursuits. Garmin even have a metric for it: https://www.garmin.com/en-US/garmin-technology/cycling-scien...

Re: A trick to reaching flow: Leave your work broken

#135

Earlier quoted context omitted.

I don’t usually leave notes, I just leave the last thing I looked at in whatever arbitrary failure state it was in, unsaved, with whatever undo history I stopped at. If the errors aren’t immediately obvious, a couple cmd-Zs is usually all it takes to jog my memory and at least start retracing my steps

What editor configuration are you using that saves undo history like that?

I’m not who you’re replying to, but I hope my input will be helpful.

I just use Jetbrains IDEs on projects with the IdeaVim plugin (integrates so well with the IDE, it’s pretty much my only must-have plugin for any software, beyond uBlock Origin), and Vim for external files (scripts, etc., or when I want to use a specific plug-in for editing).

By default IntelliJ (PyCharm, GoLand. any Jetbrains IDE…) has a pretty large undo history, and that can be extended to however long you like. The real killer, however, is the extended local history for the file, which is arbitrarily (or at least seems to be) long. Combine that with the wonderful built-in git history (which can be a separate pane/window!), and you’ll never worry about changes you’ve made being lost, or overwriting other history, no matter how overzealous you were with said changes.

I find IDEA’s built-in tools so useful I barely ever even think of using git stash or git shelve anymore (or directly calling ~30% of git commands for that matter), and those are commands for which I still have 20+ aliases for in my .bashrc.

Re: A trick to reaching flow: Leave your work broken

#136
Another hack I had read about and found out it works for me is to write down any distracting thoughts while trying to focus.

Many times, when I try to focus on a particular task, I get ideas and questions about tangible or completely irrelevant (we need to buy bananas) topics. My primitive brain would drive me to first complete these irrelevant tasks first to get some dopamine reward.

Now I always have in front of me a small piece of paper, and when some distracting thought like that hits me, I just write it down, and I reassure my brain I will get back to it once done with the main task I am trying to focus on. It is nice to have these written down because I can completely empty my brain of them.

I know it is stupid, but it works for me :)

Re: A trick to reaching flow: Leave your work broken

#139

If I need to stop in the middle of something, I’ll often write directly in the source code, at the point where I stopped, exactly what I was working on and what to do next. I don’t comment out these instructions to my future self so when I sit down next, the project won’t even compile.

I also write in the code what I was doing so the code doesn’t compile. My only issue is that I don’t trust my computer, for me, if it’s not pushed in Git then it can disappear at any moment. If the work is not too important and I could easily re-create it from scratch the next day then I’ll leave it in my local Git. But if it’s important then I also want to push it.

Re: A trick to reaching flow: Leave your work broken

#140

Earlier quoted context omitted.

I don’t usually leave notes, I just leave the last thing I looked at in whatever arbitrary failure state it was in, unsaved, with whatever undo history I stopped at. If the errors aren’t immediately obvious, a couple cmd-Zs is usually all it takes to jog my memory and at least start retracing my steps

What editor configuration are you using that saves undo history like that?

Closing my laptop and leaving it on a charger. Wish I had a better answer. I use VSCode and it does restore undo history on relaunch for the most part, but I can’t remember if I configured it for that, and I definitely don’t trust or rely on it. I know it definitely doesn’t work if I accidentally invoke “reload”.
Post reply on HN