Command line interface theptrk.com

Creating a simple 'did.txt' file  ↦

This post is a simple, step-by-step explanation of how Patrick created ‘an insanely simple “did” file accessible by terminal’. What’s interesting about it to me is not how to do it, but the idea of doing it itself. His motiviation:

Time flies by when you’re learning how to code. Its super important to take a second every once in a while to simple write down what you did during the past mental sprint. Writing down what you learned solidifies the knowledge.

This is a great truth, and one that applies far beyond learning how to code. Sometimes we need a did.txt just to recognize how much we’ve accomplished recently. For me, there are days when I get to the end and feel like I didn’t really accomplish much. If I’d catalogued my wins throughout the day as they occurred (no matter how small), I bet I’d feel different about that.

However, I’m both busy and lazy (a hellacious pairing) and wouldn’t keep up with this habit unless it were dead simple. Patrick’s ‘did.txt’ solution is about as simple as it gets…


Discussion

Sign in or Join to comment or subscribe

Player art
  0:00 / 0:00