Matthias Nehlsen

Software, Data and Stuff

SystemD and Clojure

Oh hey, I’m back. Been a while. Today, I want to share with you how I’m using systemd to start my Clojure applications on, and keep them alive, in case anything should go wrong. These are the applications managed this way:

Systems Toolbox Example

Today, I have another sample application for the systems-toolbox library for you. This application measures roundtrip times of a WebSockets connection. Before I delve into the reasoning behind this library, here’s a little teaser of how that’ll look like:

I wrote all of this from scratch in Clojure and ClojureScript, including the histogram - no charting libraries required. There’s a live version, try it out by clicking on the animated GIF.

Optimizing my Workspace - Hardware, Software, Ergonomics

So within the two weeks, I spent a fair amount of time with something that should seem fairly obvious to someone who uses computers a lot, yet that I paid far too little attention in the last couple of years of my life. Now you may wonder what I’m getting at, but no worries, I’ll get there. Let me ask you something first. How many hours per week do you spend in front of your computer? Let me guess, probably most of your waking hours, considering that you read a software-related blog. But is your workplace ideal or even anywhere close to it?

Progress with “Building a System in #Clojure”: new Feature

Most of this week, I was working on the client-side codebase of my BirdWatch application in order to remove the hairball in its architecture that I mentioned last week. That’s been going really well. But how do I make the readers aware of what I am working on right now? Your time is precious, so you may only want to read the stuff that I feel good about already, unless you have the time to dive deeper and compare the good, the bad and the ugly. That’s fine, too, but it’s just going to involve more effort on your part.

I’m writing a book about Building a System in Clojure

I thought about where to take my series about Building a System in Clojure next and realized that I don’t like the format of a blog series all that much. Instead, the format of a book seems like a better choice; one where you, the potential reader, are invited to provide feedback from the very first moment of the writing process. I have already started that process and for now I have transferred the existing articles from the series into the book without much further editing. Over the next couple of weeks, I will be working on making the content more consistent with the book format. The book is available for free on Iff (if and only if) you find the content to be of value, you can pay a suggested price, but that’s entirely up to you and something you can decide on later.

Weekly Update: Clojure eXchange, next steps in BirdWatch, Clojure and me

Last week was great. I had just come back from my trip to the United States the week before, where I attended the Conj and got to hang out with dear friends in both Washington DC and New York City. I used to live in DC in 2009 and 2010, and it was really good to be back. Last Friday, I had a talk at Clojure eXchange in London about my BirdWatch application and my journey to Clojure. I think there should be a recording somewhere, but I haven’t checked it out just yet. The day before that, I had parted from Scala with a farewell letter here on this blog. It took me by surprise how much attention this little letter received 1, considering that it was really only between Scala and me.