03 Jul 2019, 18:42

Maintaining state in long projects

As a programmer, I often want things to be just right, finding that balance between maintainability, extensibility, and plain ol’ get-‘er-done. Today, banging my head against unexpected walls while trying to spin up a virtual machine with Vagrant, I had to keep my focus on the goal at hand: Keep the website up while migrating from PHP 5.7 on Ubuntu 14 to PHP 7.2 on Ubuntu 18.

In this case, the task seemed simple. Write an email to Client so they know the status of the project.

The tip for today is to keep a stack of tasks written down so I can recall where I am headed.

  1. Write an email
  2. Estimate price of RDS
  3. Make sure I can test MySQL locally
  4. Spin up local instance of Ubuntu 18
  5. Upgrade Vagrant
  6. Upgrade local copy of Ubuntu 18
  7. Install latest copy of website source
  8. Run tests
  9. Install test framework
  10. Need to install PHP modules

I ran out of time around that point, and still had not done the first item on my list. Fortunately, I still remember what I was trying to do, and can come back to it with fresh eyes tomorrow.