Lately, I’ve been toying with the idea of developing a bunch of tools that will make my professional life just a little bit easier to manage. \u00a0The most important of these is a timesheeting system and an automated invoicing system.<\/p>\n
The initial idea for these were actually sparked by what I saw and used while I was working in Black Sheep Creative<\/a>, back in New Zealand. \u00a0Why did that experience spark an interest in building my own tools? \u00a0Well, I came to realize that while there is a lot of software out there that does what I’m looking for, alot of that software either comes with functionality I don’t want or wouldn’t use, or it is missing one or two pieces of functionality that I really want. \u00a0True, I could just write the added functionality into the software, but that would like mean adjusting something else somewhere in the system and past experiences with osCommerce<\/a> has taught that this often ends in tears. \u00a0If it doesn’t, you often get locked down to a specific version of the software you’re using.<\/p>\n So after about 2 years of thinking and um-ing and ah-ing, Timeline was born. \u00a0It’s still very much in development, but the plan is to create a piece of software that tracks your time, relative to an active project and at the end of whatever billing term you have, outputs an invoice (format undetermined at this point) and emails it to the appropriate client.<\/p>\n So far, I’ve written all the database management classes (MySQL<\/a> of course, MySQLi and SQLite<\/a> to come) and written the intial database schema for the application. \u00a0I will soon start working on the classes to handle the time tracking, project management and invoice output, then the real work begins with the boot strapping code and main engine.<\/p>\n