I probably need to start thinking about imports now for Commonmarks. Pinboard and Pocket are probably the two exports that I need to focus on.
I must admit, I do miss freelancing. Skipping the commute into the office this morning would have been a good start to the day.
I am hoping to add RSS feeds to Commonmarks today so that I can hook up my bookmarks to Micro.blog. The plan is to have a public feed that the owner can control as well as a private feed that the owner can use themselves.
Just finished watching Bird Box on Netflix. Fantastic to watch but closing the blinds now. š±
This is my first round of the year with Ethan. Iām pleased to say weāre both hitting the ball well, but my game dipped on the last few holes.

Say hi to Commonmarks
My own bookmarking app is up and running.
Itās nothing fancy in terms of how bookmarking apps usually work, but I wanted this to look and act more like a blog than a collection of bookmarks. I opted for paginating results on the right with a sidebar on the left. In time the sidebar will include more filtering options.
Iāve had a couple of stabs at my own bookmarking apps over the years, but this one feels more right than wrong. The code is still rough around the edges, but Iām happy to open source it now on Github.
And the name? Well, think of it as a commonplace book for your bookmarks.
Update: Commonmarks has been renamed to Markcase and is still under active development. Iām hoping to open it up for registrations in spring 2020. Source code is available on Github.
Plugging the web development knowledge gaps
Dan Abromovās Things I donāt know as of 2018, is a refreshing take on the knowledge gaps of software developers. Even though Dan is the creator and maintainer of a widely used package used with React, his list of knowledge gaps in web development is quite an eye-opener. And he made them public too!
Iāve worked alongside a lot of great developers, and Iāve been amazed at both their spread of knowledge on web development but also their gaps. I rarely pay attention to the knowledge gaps though. Itās easy to be amazed at the breadth of one personās knowledge and not focus on a personās knowledge gaps. Perhaps they just didnāt get round to that gap, and focusing on their knowledge gaps feels wrong, but should that be the case?
As Iām approaching 20 years working in software development, Iām starting to know the excellent job descriptions from the bad ones. Merely listing a long list of tech experience that you would like in a candidate is a poor way of getting the right one. In my view, the best candidate can come in and use their soft skills to learn and get up to speed in a few months regardless of their experience. I think it comes down to the fact that more organisations want their candidates to hit the ground running from day one. No training or onboarding, just another cog in the big development machine.
Given the number of languages, frameworks and other techs in web development, itās a near impossible task to keep up with everything, but Iām taking two things away from Danās post.
- Thereās no harm in not being up to speed with everything that a full stack web developer should do. Sure, I can deploy an app using Cloud66, Heroku and Dokku, but I canāt say the same for Docker and Kubernetes. I can deploy web applications, but only on the technology that I have chosen to learn.
- Iām considering changing my job description to be more specific. Sure I can be a jack of all trades, and know a bit of everything in the web development stack, but Iām sure I would be better off describing myself as a backend web developer instead and focusing on the technologies around that.
With these points in mind, Iām renewing my focus on Ruby on Rails as well as adding to this the knowledge that I need for the gaps around it.
Itās good to know though that I am not alone in not understanding a few topics that have been popular in the last couple of years.
Trying to keep pace with most of the topics in the web development world is a task in itself, but thereās enough work to keep me marketable as a backend web developer even if I do focus on a single core skill.
A few scrappy thoughts on buying online instead of locally
As I picked up our New Yearās Day order from the butchers this morning, I was reminded of how little I have used my local butchers and other local stores since I started working in an office.
When I worked from home, I shopped locally every week. Very rarely did we have to do our grocery shopping online. I was able to pick up most things from local stores during my lunch break. It was a good time to get away from my desk and get some air. Now that I commute to an office though, I donāt have the time in the day to continue to shop locally, and the stores where I work arenāt convenient too within my lunch break.
My thoughts on this are still a bit incoherent despite having tried to write this for close to an hour now, but hereās what I have in raw form.
- More people should be allowed to work remotely. Working from home gives you more time to run a few errands as well as shop locally and support local businesses.
- More people should be allowed to work fewer hours. Is a 40 hour work week really necessary anymore? Working fewer hours would allow us the time shop locally as opposed to just feeding more and more orders into the Internet retail giants.
Iām not an economist, and Iām sure there are holes in these thoughts, but if I could have seen the damage that internet shopping has caused to my local town, then I would have been a bit more selective about my spending habits over the years.
Iām usually the first person to defend the march of technology, but itās come to a point where even Iām not sure that the change has been for good.
Great afternoon exploring the Gleniffer Braes with Jennifer and Drew. Drew even came prepared with his own walking stick!
Keep it simple.. Another great productivity booster from Nicholas Bate.