Fixie Friday - Cinelli Vigorelli Red Hook Crit Limited Edition
The Limits of Automation
The other day I experienced the limits of what automation can deliver and realized that not all tasks are best done in an automated fashion. Some tasks need that manual touch to get done properly.
At the start of the I got back on the writing bandwagon and published another of my muddled thoughts a couple of days ago. Being a lazy guy, I have App.net's Broadcast setup that takes my daily posts from the RSS feed and publishes them to App.net and to my email subscribers. One of the reasons I done this is that I would ordinarily forget to do it.
This morning I had the realization that I might just be missing an opportunity here. Automating this sharing process from blog to you the reader is all well and good, but what if at an earlier point I could let you decide whether you want to read this post or not?
A couple of weeks ago I started adding a summary to the beginning of each post. In it I try and condense the gist of the post into a couple of lines. If it's not for you, you can move on, if you're interested then you keep on reading.
There was another couple of places though where I could be doing this, and that's in the original broadcast message and the post to my timeline on App.net. I turned off the automatic posting and sharing of my blog and instead opted to use the intro to the blog post as a brief description on the broadcast. The post which was originally sent to my timeline, doesn't include the intro and it uses a shortened URL which I don't want. So as well as using the intro on the new broadcast, I'll rewrite the intro as a condensed version for posting to my timeline on App.net. I'll do both of these tasks myself rather than relying on the automation tools to do it for me.
Automation is great for when it's mundane tasks that can be repeated over and over without interruption, but when we want to tailor that task each time it happens, we need to step in and do the work ourselves. It's not a bad thing either. Now I get the chance to tweak the broadcast and post in the hopes that I can encourage you to keep reading as well as reaching out to more people.
To Kill a Project
Stopping a project isn't easy to do, especially when that project is based on an idea that seemed to be within your grasp. Sometimes though it's the best thing to do, but to ensure it's dead we need to kill the project.
I had an idea a few months ago for a service for users of App.net. It was a service that curated the most interesting or popular posts from your timeline when you weren't there to check it. For the most part this could be when you're in bed or at work. So if you wanted to see the best posts from your timeline in terms of highest replies or stars, it would filter out the best posts for you and email them to you in a summary on a daily basis.
I've spoke to a couple of people on App.net about the idea and they were favourable of the idea. After months of incubating the idea though I want to abandon the idea. I never wrote any code for it, registered any domains or even tested the idea. The idea might be a success, but given that the number of users on App.net isn't as much as Twitter, I'm making an educated guess that it won't be profitable as a service. I want it off my radar for good. It's too distracting having it sitting in my master list thinking I might do it one day.
I'm killing the project then. I'm not abandoning it, deleting it or putting it off. I'm killing it. Permanently.
With this action comes a sense of relief. No longer will it sit on my radar demanding another few minutes of contemplation. I can get rid of it permanently.
I've only done this a few times in the past and each time it was necessary to simply kill the project. For as long as it remains in a list or in your head, you'll always spend a bit of time thinking that you'll get round to it.
The first time I did this was when I killed my mind mapping blog, MindMapSwitch. I had gave up writing about mind mapping but I left the blog itself up in the hopes that one day I might go back and write about it. I didn't. In fact for about two years it just sat there as another dead blog on the internet. A couple of years ago I decided that the blog had to go. No longer would I need to the account to keep it running. I wouldn't be writing on that blog ever again. So I took it down. Gone was all the work that I put into it, but despite that, I felt great about the decision. Another little project that has been sitting on my radar is now gone forever. I don't need to worry about it, spend time on it or even get it started. It's gone for good.
That's why it necessary to kill a project. There's no sense in having a project or an idea sitting there on the shelf gathering dust. Yes, one day you might get round to it, but chances are you won't. Better to kill the project and move on then have it pecking away at your conscience. Once you've killed that project you'll feel a weight off your shoulders and you'll have rid yourself of a commitment.
Fixie Friday - BB17 Karma
Balance isn't something that comes up a lot when people are writing about productivity. Once you are aware of it though, it's a fundamental lesson to learn if you want keep focused and make progress.
I'm like a kid in a candy shop when I have a new idea. I tend to drop just about everything I'm working on new idea for a night or two and then get back to what I was doing before. Not a good practice to follow. When you stop working on something else and spend some time with an idea, it can take over. The idea snowballs and then before you know it, you've grand plans for it and it overtakes everything else you are doing. Inevitably my workload becomes so much that I need to try and prioritise and sort my work into a schedule that can't feasibly accommodate this new idea. What to do?
Well the answer is simple. From now on for every project I take on I need to drop something else. Realistically I can only manage one side project at a time on top of freelancing and family life. When I take on too much everything else suffers. It's a balancing act.
The monthly themes I am doing just now are good for balancing work as it means that in one month I can focus on a single idea or product for that time. Since the start of the year I've used broad themes to cover everything but this month I'll be focusing on a specific project. It's the first of four projects that I'll be working on this year. The goal is to clear the backlog of tasks for that project so that it can be left alone for another few months while I bring another few projects along.
This also means that I can schedule these ideas into the year so that I know what work lies ahead in my schedule. Not only is this good for scheduling purposes but the idea also gets a chance to incubate for a few weeks or months before I start on it. By then I might have discounted the idea will then pick something else to work on.
Fixie Friday - Mars Cycles Track
via FGGT
Complicated software looks like hard work, but does that make simple software easier. I would say no. In fact I think it's harder to produce simpler software than complicated software.
At the weekend I got into a conversation with my Dad about complicated software. My Dad is a draughtsman. He puts together the drawings for piping installations such as refineries and oil rigs. He uses software on a daily basis for his piping designs, but it wasn't always done this way. When he started in his career nearly 40 years ago there wasn't a computer to be found near the desk of any draughtsman. Everything was done with pen and paper. Simple tools by today's new tool of choice, CAD software.
Over the last couple of decades the mouse has replaced the pencil as the draughtsman's main tool for work. In this time the market for CAD software has boomed and with it come some of the most complex software I have ever heard of. My Dad has made the gradual change to CAD over the years through a number of training programmes and plenty of on the job experience. His biggest bug bear though is the software. In his opinion it is too complicated.
For over a decade now I've heard many complaints against software being too complicated. Complicated software isn't the root of the problem though. Software starts with people and what those people want. These are the initial requirements of software, what we expect it to do. Given enough time, and no constraints, any software product can go from simple and easy to use to bloated and complicated. In the past it was thought that a software product rich in features was the way to sell it. What happens over time though is that the product continually grows and grows as it caters to more and more requests until it becomes just too big and complicated to use. Those original features that made the software a hit have become bogged down by other quick hit features that only cater to a small subset of users.
We software developers are a bit older and wiser now though and we've learned a lot from those first days of commercial software. The main thing I think many software developers have learned is that it is okay to say no to a request. This is perhaps the hardest thing to do, we want our software to be used by many, but that doesn't mean catering to every request. Saying no to nine features, but yes to one is our way of saying that we care about the software we produce. If a feature doesn't fall within the general mantra of the software then we should say no to it. Yes, we might gain a few more users, but in turn we could end up annoying half of our existing users.
The thought of complicated software has made me re-assess the projects that I am working on and how they can be simplified for the people that use them on a daily basis. It's also made me question requests from clients for changes to their products. I could simply take the money and add the new feature, but by questioning that feature I could be opening a new discussion with the client to find the exact source of the problem and deliver a solution that will simplify the software instead of complicating it.
Plain and Simple Bookmarking
I seem to have a love/hate relationship with bookmark managers. I like using them yet I find faults in each one and end up disliking them. Can I find plain and simple bookmarking service that let's me just search?
Bookmarking services. I've used a fair number of those in my time. Remember Delicious? Those were good days. I do and since then I've tried a number of different services including Google Bookmarks, Pinboard, and I even tried to roll my own bookmarking service a couple of times. Each time I tried something new though it felt like it was just over the top.
I never wanted to manage a collection of separate bookmarks, I just wanted a somewhere I could store them and find them. How they got there wasn't the problem, it was how I found them that mattered. Lots of bookmarking services tagging as a way of grouping your bookmarks, but do we need to tag our bookmarks if they can already be found with a good search facility?
You might have noticed a new addition to the blog in the last few weeks. At the top of the page beside the main navigation links there is a search box that you can use to search my blog. This isn't a feature of the blogging software I use, this is an external service called Searchpath. It indexes the content of your static site and gives you a plugin for your site that let's you search on your site's content. I've been using this for a couple of months now and the results of the searches have been good. Anytime I've needed to find something, I can using the simple JavaScript widget that sits at the too of my site.
After a couple of weeks of using this I wondered if it could also index other pages. Pages of bookmarks perhaps?
So last week I finally got my collection of bookmarks out of a database and converted them to markdown files grouped by the month they were created in. From here I then set up a page on my site that listed each months worth if bookmarks. You can find this new archive here.
How I add to this collection is simple. In my toolbar I have a couple of bookmarklets. One coverts the URL to the page to a markdown link and the other converts the entire page to markdown. I use the link bookmarklet to get the link for the page I want to bookmark and copy it to the clipboard.
I keep the this months file open on my desktop using the wonderful Marked application. If I need to add a bookmark, I simply press the edit shortcut key in Marked and my markdown file appears in my editor. Once I have my bookmark file open I simply append the new bookmark to the bottom, add any notes and save it.
The last part is the indexing of these bookmarks. Searchpath looks for links in site and follows them through to find pages to index. I'm interested to see how this change to my bookmarking routine works out. It's taken me to now to realise that I don't need things like tags, favourite bookmarks or even grouping bookmarks by a collection. I just need a place that allows me to search through them when I want to.
Back on the Course
Yesterday was such a glorious day in terms of weather. An ideal day to get Ethan back out on the golf course. Unfortunately the course is still a bit damp from the last couple of weeks of rain but hopefully it will dry out soon.
Logitech K811: A Review
It's been a month now since I started using the Logitech K811 keyboard. The reason I made the switch was that my old Apple keyboard was getting rather old. Five years is a long time for a keyboard, in fact it's probably the longest time I've ever owned a keyboard. As a result the keys on the keyboard were sticking and one of the keys needed a fair amount of beating before it would register the key press. I needed a new keyboard.
Two things the new keyboard had to do. Be OS X compatible and wireless. Anything else after that is a bonus. After looking at a number of different keyboards I filtered this down to a number of keyboards from Logitech. In the past I had a Logitech keyboard when I worked as an ERP developer. This was a great keyboard, so I started to look at the rest of Logitech's range. The K811 stood out for a number of reasons.
The keyboard itself is light and while it doesn't exactly match the build quality of my Apple keyboard, it has been sturdy enough for every day use. The top of the keyboard has a plastic backing while the rest of the keyboard has a nice aluminium finish. It's a shame the aluminium finish doesn't extend to the whole of the keyboard. There is also a greater degree of flex in the K811, but then that it would take a great amount of pressure to snap the keyboard this way.consists of an has a small profile. The K811 is thin and doesn't have as steep an angle as the Apple keyboard. Looks wise it's definitely up there with my old keyboard.
The keyboard can be charged using a USB cable. This is good but in the last month I've had to charge the keyboard three times. This maybe partly because I've left the keyboard on when I leave my desk. If I turned it off when I wasn't using it then it would probably extend the life of the battery between charges. I'm not going to worry too much over this though as it does mean that I don't need to replace the batteries for it.
Another nice feature of the K811 is that you switch between multiple devices at the touch of a button. With my iPad almost unusable (long story), I haven't used this feature although when it comes to getting a new iPad, it's good to know that I'll be able to switch between my iPad and my MacBook if I need to.
The last thing that I like about the keyboard is the backlit keys. My hours of work can vary from day to day and during these dark winter nights it's been good to know that my keyboard is easier to see when I'm working late with just my desk light on.
The only real gripe I have with the K811 is that the connection to my MacBook cuts out about once a day. I've searched the support forums on Logictech for a resolution to this but I've yet to find one. The connection does come back after a few seconds, so I'm not going mark this as a big drawback to the keyboard.
Other than that the K811 has been a great keyboard to use so far and is definitely a worthy replacement to my old Apple keyboard. It's more expensive than an Apple keyboard and maybe not worthy of the price difference but I was happy to fork out the money to get something that would work for me on a daily basis and offer a little bit more than other keyboards do.