I hacked my blog to let AWS Polly create podcast over it

         · ·      · · ·

Prelude Hi guys, after a series of back-to-the-future-I-didn’t-have-time-to-write-new-things… I’m back. What happened in the last months… ok, covid19 put the whole world in trouble, I bought an apartment, I opened a company and I resign my contract. Really. Nothing. Special. But TODAY - I wanna talk about a project I have since a while, and I worked on a boring Sunday afternoon: I hacked my blog to let Polly read it for you!

A Golang Turing machine library

         · · · ·      · · · · ·

Preamble This is a repost of an old article :) In 1962, Hungarian mathematician Tibor Radó introduced the Busy Beaver competition for Turing machines: in a class of machines, find one which halts after the greatest number of steps when started on the empty input. Even if it could seem trivial, the Busy Beaver competition has implications in computability theory, the halting problem, and complexity theory. I decided to use GoLang to implement a Turing machine library and accomplish three goals: first, having a Turing Machine model to play with for learning purpose; second, learning how to use interfaces and the factory pattern, other then testing package to test my code and let it be more flexible for future enhancement (at least I hope!

Jails: confining the omnipotent root

         · ·      · · ·

Preamble This is a repost of an old article :) Recently I became nostalgic and fascinated with stuff from the past, so I decided to create a Vagrantfile to work with FreeBSD1. Why FreeBSD? Because as a developer, I really like Docker and I started looking in the past to find its historical birth: in fact, as a concept, Docker is no so recent as you think, and I think it exists also because of the works of some other bigs from 80', such as Poul-Henning Kamp2.

T.H.I.N.K: is all about problems, not data

         · ·      · · · · · ·

Intro Mute post Bye

Devops strategies

         · ·      · ·

Intro As you might know, I use to work with AWS doing and destroying stuff like many other devopssss out there: this post is all about some challenges and problems I had to deal recently - in the last months - and involves some notes about how to deal with multistage environments, decoupling and many other practices you should all know about. The first thing to emphasize is that each of these best practices is fairly clear and well-defined, for sure online (perhaps discussed by bloggers more experienced than me XD) and deeply described in many books.

From Jekyll to Hugo, from Travis to Gitlab: a time for changes

         · ·      · · · · ·

Intro In the last 50 days I had to work a lot for many… many different reasons. The main ones: I was accepted as a Speaker at FullStackConf19 in Turin, talking about coding in mobility. You can find the slide of my speech here and the material I prepared the talk in this Github repo. By the way, I was truly inspired by some of the talks during the conference, and I started brainstorming around the next post; I moved back to Italy and trust me -> it was a pretty complex goal to achieve, with particular regards to my car; I joined Enerbrain and I’m really having fun with theme building smart-energy solution as a Devops Engineer; I joined a softball team - yes, it’s mixed, but it’s officially played also by men hahe.

Time to say good bye


Prelude In the last two months, many things happened in my life, so this is the reason I wasn’t able to dedicate a lot of time to my blog. What can I say… I’ve been in South Africa, and I literally lived experiences I will never forget and cannot be described. I visited the Blyde Canyon and the Rain Forest. I made so many safaris, I saw the elephants in the morning washing and drinking from the river, the giraffes, I saw the warthogs - and by the way, they are exactly as Pumba in the Lion King by Disney - the lion, which was about to attack the buffalos, I found the white rhinos, the hyenas and the leopards.

The Good Employee, a story about how you can explain modern companies with graph theory

         ·      · · · · ·

Prelude This is a twin post of - I guess - a good one that I wrote a long time ago: I was just surfing the blog thinking about all I would like to do, and I came to my old thoughts. I was curious, you know? so I read it, and read it once again, I reflected a bit on it - and I found it inspiring in a sense: even better, I would say I found myself surprised to agree with myself of almost 1 year and a half ago, in most of the things I wrote.

A Bugs Life: stories of a software engineer

         ·      ·

Disclaimer I’m on a train, back from Frankfurt - Germany, another of the cities to collect together with the ones I visited in this experience abroad in search of myself, trying to figure out who I am and who I want to be. Why this post and what to expect…Well, why, it’s simple: I recently studied a lot and got my AWS certifications (yuppie), I didn’t stop studying because I already planned other exams (really one of a bad idea of mine) and I also started to use my free time to go ahead with a couple of side-projects - they are super time-consuming.

Software developing and Data science

         ·      · · ·

Software developing and Data science I recently had the chance to think about software developing and data science: it’s not about the fact that I hate everything that contains the word data inside, but I was somehow interdicted by sentences like this. > [..] we found that - specially with Amazon retail - we can really accelerate the use of machine learning if not everyone needs to be a data scientist.