I’m a big fan of tinkering with electronic devices and regularly attempt to repair phones, laptops or computers around me. A few weeks ago I decided to repair an old thinkpad with a broken hinge by installing a fresh new bottom cover (after different previous attempts at saving it in a more hacky way). Above is my recording of the session.

If you have been lucky enough to go to conferences, hackathons, code-retreats or unconferences, you must know how much these events are privileged moments to learn and grow in your field. But they come with a cost: you may need to take days off to join them, they need to be available at a date and location compatible with your situation and not be sold out when you finally decide to pick one. So today, let’s reverse the table: if you can’t go to the conference of your dream, why not make the conference of your dream …comes to you?

The Software Craftsmanship London 2017, or SCL, was a 2 days conference organized between the 5/10/2017 and 6/10/2017. I had the chance to assist this event. I’ll try below to juice out one sentence per talk and explain why I chose this one.

The selected quote doesn’t summarize the talk nor is it supposed to be the most important for each presentation. It is just to give you a taste with one example of something said that I liked and encourage you to have a look to the complete videos of the talks.

Today I am gonna give you a quick review of the last two books I read: The Clean Coder, by Robert C. Martin (aka Uncle Bob), and The Software Craftsman, by Sandro Mancuso. Both books cover the same topic: the Software Craftsmanship movement.

It all started with the simple instruction: -t flag assigns a pseudo-tty or terminal inside the new container… and a moment of puzzlement… What is exactly a pseudo TTY? What does it mean to attach or detach a process from it?

Beware my friend, for this article will lead you into the depths of forgotten history, guiding you through arcane kernel mechanisms. But persevere and the pure light of knowledge will shine upon you by the end of this journey.

I’m getting more and more interested in how my system works “under the hood” lately. These fundations are essential to understand some behaviors / technical choices in technologies oriented for end users (such as Docker).

That’s why I decided to write, mostly as a reminder for myself, a serie of articles explaining some fundamental Linux mechanisms. As I have to start somewhere, I’ll start with the boot process.

I already wrote about Docker, and today I will present different solutions to host your lovely docker containers. If you want to know more about Docker, you can read my previous post on this subject.

I introduced in a previous post how to create Docker images interactively and with a Dockerfile.

In this post, I will focus on good practices and see how a proper repository is realized. Indeed, in my previous post, my example was a little bit trivial, and if you want to create your own images through a Dockerfile, you will surely bump into difficulties: how do I manage interactive installation that ask a user input during install? How should I configure my application after installation? And many others…

A week ago, I introduced the framework Docker. Docker is a lightview virtualized environment. It allows to build, manage and run containers to easily deploy an app in an iso environment. I will introduce today how to create containers interactively and through Dockerfile.

You want to create a nice graphic presentation, but you don’t know anything about design? You need to create some game graphic elements, but you’re really bad at drawing?

Isometric 3D allows you to create really neat and fun elements without knowing anything about design or art. In a few steps you can obtain really nice results.