“I always worked until I had something done and I always stopped when I knew what was going to happen next.” — Hemingway via https://www.goodreads.com/quotes/856460-i-always-worked-until-i-had-something-done-and-i … This works well even for writing code /1
Have something done even if it may not matter for project This gives sense of accomplishment and makes me look forward to next day Know what to do the next day. Preferably, by writing code midway. A common writing advice in books such as the Writer’s Source Book /2pic.twitter.com/8C7PF9m1Hr
-
-
e.g. I finished closing about 4 issues yesterday. Then to prepare for today, I brain dumped tasks that I want to finish today. Find the easiest looking one — a bugfix. Then purposely write the code halfway with the uncertain part left as ?? /3pic.twitter.com/K9n15GC62U
Prikaži ovu nit -
Another thing I learn from creative types is when to focus on the output (progress in project) and when to focus on the input (effort) From this interview https://www.esquire.com/entertainment/movies/a55985/christopher-nolan-interview/ …, Christopher Nolan mentioned he looks at progress only at end of week /4pic.twitter.com/89SEIddzfy
Prikaži ovu nit -
So combining everything I get, 1. Progress by end of week, Effort by end of day 2. Finish one thing a day 3. Stop midway today for easy next day
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.