Posted on August 31, 2018
Lately, I found myself to work on an application that was communicating via SOAP with a server. My goal was to understand how this application worked with the SOAP server to emulate its behavior. Even if I had access to the source code of the application, I thought it would have been easier, faster and more fun to do the work without actually reading the code. It’s important to note that actually, the application is fairly small and self-contained.
Posted on May 9, 2018
A couple of months ago, I wrote a blog post about why containerization is not always the answer and I’ve received quite a few comments about it. This article has the goal to analyze an aspect in favor of containerization which I believe to be true but was not mentioned in the previous post: the time aspect of the phenomenon.
In the ICT sector, we are used to new technologies, or at least we should be.
Posted on April 12, 2018
As many other clouds, Google Cloud Platform provides an Object Storage service, Google Cloud Storage. As many other Object Storage service, Google Cloud Storage provides an HTTP server to deliver your files quickly. When I started to use Google Cloud Storage and its HTTP server I have not been entirely pleased by how it works and therefore I wanted to re-implement the HTTP server so that I can manage it completely.
Posted on March 27, 2018
UPDATE: I’ve then written another post to clarify better my point of view on the future of containers.
When I hear people (and usually those people are salespeople) saying that as soon as you put a Container Platform in your company, all your problems go away, I feel bad for the company they are trying to sell it to.
I’ve seen far too many container platforms (as well as many other technologies) fail at customers because they have been sold as this magical problem that makes all your problems go away.
Posted on January 5, 2018
I found myself multiple times in situations where people were trying to explain to me how much they are (or would like to be) DevOps and how awesome DevOps is and how productive their teams had become since when they merged the Dev team and the Ops team, and they don’t have any team which is not DevOps and application-centric. I usually stare at them thinking that they have no idea what they are talking about, or they have just outsourced all the non-application-centric side of their IT and have not realized it.
Posted on December 21, 2017
A few months ago, I posted how to create a PKI in Go. Today I’d like to add share a useful function (at least from my point of view) that I found myself to write.
The problem arose when I had a function that required as input a *pem.Block of the public key, but all I had was the PEM file containing, as you can imagine:
the Private Key the Public Key the CA Public Key I think this is a typical situation, and for this, I’d like to share a function I wrote to extract it.
Posted on June 5, 2017
Lately I have been programming quite a bit and - for the first time - I have used Golang doing so. Go is a very nice language and really helped me with the development. One of the reasons why I have enjoyed this much Go is the standard library, which is amazing. I would like to share today the easiness of creating a basic Certificate Authority and signed certificates in Go.
Posted on January 3, 2013
Have you ever had to develop a script in UNIX that has to send an email?
If you have, probably you have used the “mail” function since this program is the standard program to send e-mails in UNIX environments if you are using the CLI (Command Line Interface).
The manual for mail reports this as mail usage prototype:
mail -r [sender] -s [subject] receiver-1[,receiver-2,...,receiver-n] < [File with the body] I think all the parameters are pretty straightforward except the “File with the body” one.
Posted on May 19, 2012
This book starts with a little introduction and with the instructions to setup the environment. After this, the book starts at full speed with “the Recipes”. The structure based on Recipes is what I liked the of this book. Every Recipe has the structure:
Problem Solution Discussion I think that this is a very powerful structure because in this way we can learn from the obstacles that each one of us can encounter in his way while coding.
Posted on April 24, 2012
This is not the typical O’Reilly programming book and you can find it out very easily when you have the book in your hands, since it does not have any code inside The author, in fact, tries to create a software development science. This left me very puzzled since:
I think this kind of stuff has to be said by people after you, not buy the author himself The author mainly collect ideas and principles that are already explained in a lot of other books The author suggests the DRY and the don’t fix if it isn’t broken principles and I think these will not always bring you to good code The book only says what to do, it does not cover how to do it Re-factoring and single responsibility principle are not covered Apart of these five points, I think that the book has reasons to live.