During the last year at buildo, we have been working on improving our internal communication dynamics. We had a clear goal in mind: to write a set of guidelines describing our company's specific communication needs and communication tools, so that each of us can communicate in the best way possible.
We wanted to answer questions such as the following:
“Deliberate experimentation is more important than deliberate practice in a rapidly changing world.”
Even though the article focused more on experimentation for personal improvement, the first thing that came to my mind was something like: “this should be one of the core values of every company” (here’s a Forbes article that tells the same).
Here at buildo, we take experimentation and continuous improvement seriously: it’s our core value. The goal of this post is to share with you how we do experiments internally, also…
In any software project, transforming customer needs into something actionable by the development team is a very challenging task.
Traditional software development processes rely on the concept of requirements for representing inputs to the developers; a software requirement typically dictates what is expected by a software.
An example of software requirement could be:
The menu shall display the name of the user currently logged in
This serves both as an input to a developer and as acceptance criteria for when the feature has been implemented.
The issue of relying exclusively on requirements is that context is usually very little if…
I recently attended the Scala Italy 2017 one-day conference in Rome, together with my coworkers at buildo. Having just started to learn Scala, I was excited to have the opportunity to get in touch with the Scala community and to attend talks by experienced developers in the field. Here are my thoughts about the conference!
First, let me highlight the fact that Gabriele Petronella, one of my colleagues at buildo, was one of the organizers of the conference, and that we are very proud of it.