In part three of my task management framework endeavor, I begin to flesh out the user experience that the implementation apps will try to accomplish.

I first want to determine how to handle task deadlines in a way that is intuitive, natural, and predictable for the end user.

This is part two of my quest to make a task management framework that is simple and extensible. In part one I included a list of high-level requirements. I also noted that I plan on implementing the framework in two reference applications, written in two languages, to help me self-evaluate the framework I've created.

This update focuses on the first draft of the serialization format, which is effectively the heart of the framework.

The OpenWeatherMap API has been making the rounds. It practically came out of nowhere with a simple and open way to access weather data. This inspired me to write a tool that spits out a single, simple line describing the current weather at a location.

I decided to revisit Python for this tool. I'll probably use Python as my obligatory second language in implementing a reference app for my task management framework, so I figured it'd be good to brush up on the pythonic way of doing things.

The task management app is almost a cliché at this point. I still consider it an unsolved problem, at least for myself. My requirements are probably peculiar. I'm looking for an elegant task-management framework more than a consumer-friendly application. This is a perfect scenario to try to tackle the problem myself.

I'll go into details once I start working through each component of planning and writing this thing. Here's a very high-level overview of what I'd like to accomplish:

  1. Simplicity in design and implementation
  2. A command-line app that I can use daily for work and personal task management
  3. A serialization format that is straightforward and easy to work with
  4. Extensible