For the past few weeks I've been giving Klok a spin. Last time I've mentioned Klok it was just after a quick install and neglect, but I did always intend on giving it a try. Then when its creator Rob McKeown commented on the post I knew there was no escaping giving Klok a try. So I started using it full-time to track my time, however odd that comes out when one says it.
Klok is a time tracking system rather than a time managing system. What this mean is you feed in a bunch of different projects then when you're working on one you just tell klok about it. The great thing about this is that it enables you to easily track how much time you've spent on a project and the fact it also makes automatic time sheets shoudl be a bonus for anyone who's ever worked as a freelancer or has otherwise been engaged in multiple projects at a time.
The biggest advantage Klok has brought to my life is that I find it easier to "just get to it" rather than procrastinate until a full hour or whatnot. This is because before klok I used to procrastinate until such an hour as it was easier to track time from because I'm usually paid on an hourly basis and need to know how much time I've spent with something. Since klok tracks the time for me I can now give accurate hour reports even if I work 20 minutes now, 34 later, 12 even later. Of course you have to learn to always punch in to the application, but hey, sure beats having to manually calculate amount of time spent working on something. Especially since I usually forget all about time when I get into something intersting.
Another feature I love is cost calculation. You can specify cost per hour for any given projects and klok will automatically tell you how much money you've earned or spent. This comes in extremely handy when you're developing something for yourself, but would like to give it an objective value when somebody asks.
It's also very nice that klok supports sub projects. The way I use this is to have "projects" that are actual different clients and then having subprojects for everything that I do. However I find the lack of telling klok _what _I'm doing to be a large fault. There are many situations when I need to have a list of things I did for a certain project, but it would be a waste of time and resources to have every little thing listed as a subproject.
Another thing that bothers me is how slow Klok is. I understand using a beta version brings certain problems to the table, but I'm only using it because the latest stable version is so stale it doesn't even allow right-clicking and is overall useless. The beta, although functioning wonderfully, needs a lot of polish.
For example when I first open klok and want to immediately start working on something I sometimes have to wait up to a minute for klok to start responding again. Then sometimes different projects in the week view (inspired by iCal I believe) show without labels so I can't even tell what they are. The fact that resizing the application window is encumbered by the fact klok's interface has to reposition itself is also a big ew. Then there's other little things like not being able to change project's colour even though the interface is there ... oh well, it's beta what did I expect.
Over all, Klok is a wonderful piece of software that I would advise everyone and their dog to use. Hopefully Rob will take care of the bugs and make something truly magnificent.
Oh and I love the design, very shiny.
Continue reading about Klok - the missing PIM application
Semantically similar articles hand-picked by GPT-4
- The Twitters pitched 5 products, why I chose the first
- Do you use any special time tracking software?
- Living life in 25min increments
- Workflowy is to TODO as git is to svn
- Sabbatical week day 1: Toshl and Toggl datasets
Learned something new?
Read more Software Engineering Lessons from Production
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Software Engineering Lessons from Production
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️