Rather than using one of the pre-existing authentication libraries in kitolab, which I find bloated and generally so-so, I’ve decided to write my own. I’ve also decided to share the core of the library for all to use. It’s intentially minimalist, and provides only the bare essentials so you can use it as a starting point to build out our application specific user library needs.
To download and get more information, check out the user library project page.
Just a quick note, if you’re interested in being notified when kitolab launches, or wish to participate in the closed beta test, please go to www.kitolab.com and sign up. You can also follow @kitolab on Twitter of course.
After weeks of brainstorming, domain searching, forceful premature balding and sleepless nights, I’ve finally decided on a name for my upcoming project management app.
What’s in a name?
For the longest time I was intensely frustrated that I couldn’t find available domain names in the project management realm. Before long I found that I was starting to settle for names that didn’t really mean anything, and were hardly memorable.
Then I started to take a more systematic approach to finding a name. Aside from all the standard naming criteria, I decided that I wanted the name to represent:
- More than just tasks. What I’m building is not a to-do list manager, it’s a much more intelligent project management assistant (a lab partner, if you will).
- More science than art. Typically, project management is a lot of guess work. I aim to replace much of that guess work with tangible, data-supported analysis.
- Simplicity & fun. Ok, it’s not likely that managing projects will ever be “fun”, but if it’s not “painful”, that’s a start.
Continue Reading
This post is slightly geekier, and more hands on than most of my recent posts, but it follows the same theme: efficiency.
The life of a developer is fraught with repetition. Minimizing said repetition makes me very happy. The other day I noticed that whenever I start working on a project I start with the following routine:
- Open Terminal
- cd to the working folder for the project so I can pull the latest files from the Git repository
- Open the working files in TextMate.
After these steps, the process diverges, but those first three steps are constant. I keep my project files well organized so I have a hope in hell of remembering where things are, so even changing directories to my working files follows a pattern (cd projects/projectname.com/working). Continue Reading
I try to ask myself this on a fairly regular basis. I feel it keeps me focused on building the right tool for the job, rather than just the shiniest one in the box.
Consequently, the more I’ve thought about this question, the more keep coming back to another question: How long? This seems to be the most prevalent question in project management, and is the basis for nearly every project management decision we make. How long ago did they ask for this? How long will it take to do? How long have you been working on it? How much longer until we’re done? Then, when we’re done, we ask: How long did that take? How much longer is that than we thought it would take?
There are dozens of “how long” questions in project management, and this is simply because managing a project, is managing time. People, budget, service these are all just tangible realizations of time. The distillation of nearly every facet of a project, to its most basic unit, leaves time.
So, it seems clear to me that a tool designed to make project management easier, should place great emphasis on reducing the effort required to answer these “how long” questions. Odd that I’ve yet to see one that does.
What does good project management mean to you?
