Discover and read the best of Twitter Threads about #quadplay
Most recents (1)
When coding, I always maintain a journal in the repo (I happen to use Markdeep for this now) with a TODO list.
Tasks are at the level of one hour for "today" stuff, one day for next week, and then week- or longer level tasks.
I expand the details for the next week on Friday.
Tasks are at the level of one hour for "today" stuff, one day for next week, and then week- or longer level tasks.
I expand the details for the next week on Friday.
I expand the one-day tasks into one hour either first or last thing in a day, but ideally as my last action so that I start each day with clear direction.
When I start working on the top, ~1-hour item, on the list, I immediately expand it recursively until the subtasks are completely braindead to implement.
I do all of the hard part of programming here, in the TODO list, figuring out the library calls, designing the APIs, etc.
I do all of the hard part of programming here, in the TODO list, figuring out the library calls, designing the APIs, etc.
