Kernel Panic

By Niclas Jern

Flowdock and Go, sitting in a tree…

At Walkbase, on any given day our team is usually spread over at least four different offices in three different countries. We also have a remote-friendly approach to work, which places the weight on results rather than “ass in chair”-time for the team.

To keep everyone on the same page, we use Flowdock extensively. To make Flowdock even more useful, I have lately been working on adding some extra sugar on top of the already existing functionality.

Introducting httpstream

“Perfection is achieved not when there is nothing left to add, but when there is nothing left to take away”

I’m a big fan of libraries that do one thing and do them well.

Meet httpstream. Inspired by and forked from another library of the same name, but stripped down to doing one single thing; Consuming HTTP streaming API’s.

Hutch: Self-hosted Twitter Analytics

Hi there! Do you

  • care about what people say about your or your company in social media?
  • work in a field where it’s important to stay on top of the latest news & developments?
  • prefer running your own (open-source) services rather than relying on a SaaS app in a cloud somewhere?
  • not cower in fear when you hear words like compiling or terminal?

If the answer to one or more of the above is yes, you should probably check out Hutch, my latest Go project.

TicTacGo - An AI for Ultimate Tic-tac-toe

A few weeks ago I took part in Aalto Entrepreneurship Society’s Code It! event, which provided the perfect excuse to sit down and write some code in my current hobby language: Go. The competition consisted of five challenges, three of which were non-trivial. This post covers the how and why behind my submission for the UTTT challenge, including source code.

If you’re unfamiliar with Ultimate Tic-tac-toe, take a minute to read the rules before you continue. Done? Great, let’s move on!

Hello World!

A recurring theme, which most technical bloggers seem to bring up sooner or later, is the suggestion that every software engineer should have a blog.

A blog can be useful in many ways:

  • It acts as a repository of knowledge you have gathered.
  • The act of writing one is a great way to codify loosely coupled pieces of knowledge into a coherent stream of thought.
  • You get to practice one of a software engineer’s most important skills: writing.
  • You can share things you’ve learned with whatever community may be interested in them.
  • It’s a good way to bring attention to and solicit feedback for your personal projects.
  • Finally, it may even help you connect with people in your field, opening up new opportunities for them, you, or in the best case, both.

The purpose of this particular blog, which I’ve dubbed “Kernel Panic”, is to do and be all of the above. Let’s see how it goes, shall we?