In my daily work as a developer I always have this file which I call
todo.txt. It contains all the things that I plan to work on, currently working on, and those that I’ve already done in the past. They are ordered from the most recent day that I’ve worked on the project to the least recent. These todos are stored in their own folders, named after the name of the project. Here’s the general format that I follow:
1 2 3 4 5 6 7 8 9 10
This is the first file that I open when I start working. It gives me a quick overview on which things I’ve already finished and which things are left undone.
The items in the todo list often represents individual features that I have to work on. If the feature is too big (may take around 2-5 days to implement), I break it down into tiny bits to reduce the mental strain. Because holding one big feature in your short term memory is hard. I want to make my todo list as stupid as possible. So I can focus on writing the code and not needing to hold many details in my head. It would often look like a step by step procedure (algorithm) of sorts. Here’s an example from the booking app that I’m currently working on:
1 2 3 4 5 6 7 8
Of course it doesn’t end there, but you get the idea. Make every item or in this case sub-item as stupid to implement as possible. If you think it would help to break each sub-item down some more, then do it.
Aside from the features I need to implement, my
todo.txt file is where I also put details on the current project that I’m working on. As I’m primarily using Amazon ec2 instances on my projects, the details that I put on top of the file are the ip address, the domain name assigned to the instance and then the user and password for the database. Yes it would be more secure if I put them on a password manager such as keypass or lastpass but I prefer fast access over it. I just want everything that I need for the job to be in one place.
Lastly, when I’m doing research for the project that I’m currently working on. I also put in some relevant URLs which I could easily go back to later on once I implement a specific feature. When I find myself going back to access a specific page very often, I just copy the specific content that I need and paste it on the file. Here’s a sample snippet, these are the set of commands that I use when building a phonegap app:
1 2 3 4 5 6 7 8 9 10 11 12 13 14
That’s it! Having a
todo.txt file at my disposal is really helpful in my day to day life as a developer. It helps keep the mental load to the minimum by having all the details that I need all in one place.