Confirmation bias: Στο 1-3 με την Βέρντερ κοιμόταν ο kid[0] δίπλα μου στον καναπέ. Στο 2-3 με την Arsenal κοιμόταν ο kid[1] δίπλα μου στον καναπέ. Στο 2-1 με την PSG στο 90′ κοιμόταν δίπλα μου η wife[0] και έσπασα και μια λάμπα.

Είναι να μη σε πιάνουν τα γούρια μετά :)

BlinkStick is a USB powered LED that can be driven via a simple API from a programming language like Python. Since the status of an ElasticSearch cluster can be determined using three colors (green, yellow, red) a BlinkStick can be a nice visual aid in your monitoring infrastructure.  An easy proof of concept is to use the BlinkStick Website API that allows, given a token, for the color of your BlinkStick to be set remotely by your monitoring system for example. You can find such a proof of concept here: https://github.com/a-yiorgos/elastic-blink

BlinkStick, soldered

BlinkStick, soldered

Of course if you want a more elaborate and secure setup, it is possible. I had my 15 minutes of fun. YMMV.

If you’ve read The Phoenix Project, then you already know that of the four types of work, unplanned work is the plague for DevOps.  It is just that sometimes, this unplanned work for DevOps, is planned work for everybody else. Conway’s Law at its best.

I got How to Self-Promote without Being a Jerk on a $0 promotion that its author was running on LinkedIn.

Sane advice and catchy phrases, but not something that you do not already know of. Surely not as boring as the disaster of Become a key person of influence.

I got You are a writer by Jeff Goins on a day it was given for free years ago. I got to read it over the weekend. I thought then, and I still do no now, that the book offers advice to people who write code too. Maybe because sometimes I believe that code is like a poem. So I will try to rehash advice I found useful here, since this seems to be one of the acceptable self-help books that have come my way.

While anyone can connect with anyone and put stuff out there, how does one gets noticed? By helping people. By relieving their pain. I’ve advocated answering one question per day on ServerFault (or StackOverflow, or whatever clicks to you), although I do not always practice this. I used to, though, years ago when mailing lists and newsgroups were the thing.

You need to build a platform. This blog is a platform. I post stuff here. Others do it with more success, for example John Sonmez who uses a variety of platforms (blog, YouTube channel, podcast, book) to publish his work (and he gives 90% of his work for free he said on Ruby Rogues). You make the platform and you establish a brand. Without a brand you are forgettable.

And you know what helps you not being forgotten? Networking does. Meaningful relationships do. Relationships that are mutual, matter to both parties and give you the opportunity to make friends and find mentors.

But nothing of the above makes any sense unless you are prepared to answer the following questions:

  • Am I serious?
  • Am I committed?
  • Am I prepared to be challenged?

Please take the time to sincerely answer these questions. And while you are at it, understand that you probably are not the best coder in the world yet. But you can become one. There is room at the top here.

Like one of the main characters in The Phoenix Project said, mastery comes through practice. And here Goins argues that the best kind of practice is done publicly. Interestingly GiHub seems to be our public place of practice.

While you’re at it, learn to estimate. Underpromise and overdeliver. Especially when you are part of a team. Like Goins writes, you have a gift. Someone is willing to work with you.

Go on! Practice.

The Phoenix Project


I remember I got the Phoenix Project for the Kindle for free on a promotional day sometime back in 2013. I’ve been meaning to read it ever since. But back in those days I was suffering from the problems that the main character is suffering for at least the first 35% of the book. And well, when you can simply rename the characters of a book and relive the experience it is not something that helps.

I finally made it this week and got through it with some late night reading. Just like now that I am writing the post minutes after reading the last page. I am not going to rumble about the three ways or even the four types of work. By now this is common stuff and even some years ago, if you tried to read about Systems Thinking or even Cybernetics, you would have reached to those conclusions. But hey a story always imprints a lesson better than a textbook and this is so much better than The Deadline. You want to revisit The Deadline in order to copy the notes of Mr. Tompkins. You do not need to revisit The Phoenix Project.

Interestingly the book forms a career path for people interested to follow. It kind of reminded me of Putt’s Law and how you cannot postpone your promotions forever. I find it kind of optimistic careerwise, depending the location of the reader and there is still the question of the top floor.

While this is a novel about DevOps, DevOps still means different things to different people. Luckily this is a novel for all people for whom DevOps at least means something.

Start me Up!


I cannot even remember how many disks Windows 95 was, fourteen, fifteen? Something like that. And how many hours installing it to machines around the lab.

That was the day I said goodbye to FTP software’s PC/TCP and Trumpet Winsock.


Ενημερωθείτε για κάθε νέα δημοσίευση στο email σας.

Μαζί με 1.947 ακόμα followers