5 ms·
Useful things for those in the struggle... Deep Work, by Cal Newport. An excellent book on how to work on really big ideas/projects effectively, without losing
by beat 8y ago
Useful things for those in the struggle...
Deep Work, by Cal Newport. An excellent book on how to work on really big ideas/projects effectively, without losing your humanity in the process. This is a must-read for anyone serious about work.
Pomodoro Technique. This is well-documented with lots of apps and tools online, but it's pretty simple. Set a 25 minute timer. Work, without interruption, for 25 minutes. When the timer goes off, do not-work for 5 minutes - exercise, web surf, whatever. When that timer goes off, set another 25. It's nice because it does the boundary stuff this article talks about in a manageable way. It's not "I'm going to work hard all week", but rather "I'm going to work hard for 25 minutes".
- amorphous 8y agoMy biggest problem I have with deep work is not that it makes undoubtedly sense and leads to interesting results but to find what to work on. I can't find my deep work. Finding a niche and sticking to it is much harder than performing deep work.
- amorphous 8y agohonest question, why does this get downvoted?
- beat 8y agoBeats me. I mostly get downvoted for violating the political status quo of "What's good for young educated white men is good for everyone" that drives HN. But downvotes happen for all sorts of weird reasons I don't understand.
- nbeleski 8y agoChoosing somethind to dedicate time and effort is consistently one of the hardest decisions one can take. Choosing something (or sometimes someone) can mean you are giving up on an (almost) infinite number of other options. I encouter this pretty frequently between people getting into serious cientific research.
- comboy 8y agoThat's your deep work then (if you are striving for one) - finding it. Focus on that.
- mroll 8y agoAny programmers here use pomodoro? I expect 25 minute interruptions would do more harm than good for my focus when writing code, especially the continuous expectation that I will be interrupted. I don’t have a pressing interest in finding productivity tips, just curious to hear about programmers who have tried this technique
- ai_ia 8y agoI use pomodoro but with 45 mins instead of 25. I am usually tuned to deep focus playlist on YouTube/Spotify. In the five minutes, I listen to my current favorites song for full five minutes. Every day I aim for 10 pomodoros. Earlier I was able to do 3-4 and was left unmotivated. Now I have been able to crush 10+ everyday for last eight days.
- wonthegame 8y ago25 mins is too short for certain types of work. I find 45-50 mins of work with 10-15 min breaks works the best for me. Starting with 25 minutes is mentally easier when you are first starting a task and then once you get the hang of it you can adjust. Sometimes I would go longer because I was really in the zone.
- rhacker 8y agoI did pomodoro for about a month once. It was actually helping a lot. I think I got lazy after a while and stopped doing the entire stop-watch thing, thinking I would continue doing it by just looking at the clock. I think I will try pomodoro again today and see if I can get back that juicy tomato timer goodness.
- undreren 8y agoI have more or less the same experience. I used tomato-timer.com. It’s really good.
- blue1 8y agoI've found that pomodoro solves two problems. First, 25 minute is a small, non-frightening investment of time that you CAN do; so it facilitates starting an activity. Second, since 25 minutes is indeed a short span, the clock usually stops before you have completed the activity (meaning that you know what to do next) and also before you are tired. So after a little rest it is also easy to start another pomodoro. And so on. You keep momentum.
- Loic 8y agoDeep Work is maybe the first book I wanted to through out of the window in a long time. The complete book can be resumed in a sentence: "Secure big chunks of time to reach and be in the flow state". But of course you cannot write a full book out of one sentence, so it repeats itself until it achieves to contradict itself by telling you that if you are a writer/journalist you can achieve the state of flow in chunks of 10 minutes spread over the day and happily switch tasks. So, no, really, you can save yourself this book.
- tc7 8y agoContrariwise, I just read and loved Deep Work: it's made me more purposeful about directing my attention, and aware of how my environment and lower desires work against this focus. The journalistic model of doing deep work does seems different than the others, but he's not recommending it, just pointing out that there are outliers who can train themselves to reach intense focus states quickly and do deep work in short periods of time. Not sure why this would bother you -- if it doesn't apply to you, ignore it! I felt like there was a ton of value here. Recommended for all!
- Loic 8y agoGlad it helped you! In my case, as I was already exposed to the concept of being in the flow[0] while coding and the basic rule of reserving the biggest chunk of time to my most long term or important work in my day, it was a waste of time. [0]: https://en.wikipedia.org/wiki/Flow_(psychology) https://en.wikipedia.org/wiki/Flow_(psychology)
- jcbrand 8y agoI'm glad to have read your comment. I almost thought of buying the book. I read "So good they can't ignore you" from the same author and was really underwhelmed by it. It came across as repetitive and formulaic (i.e. have some basic principle, then interview interesting people who employ this principle somehow).
- throwaway82729 8y ago