Author Andrea Lorenzani
The conference started with a guest performance, Reeps One, a beatboxer that apparently worked with AI to try to visualise voice and music. He did a documentary called “We speak music“, nice introduction. But the first tech keynote was “Developer… Continue Reading →
While most of the team members care about estimate just as part of a routine of the Scrum methodology, estimating tasks is quite important for those members of the team, or even of the company, that deal with senior management… Continue Reading →
In the previous post about “Theory about technical leadership” I just gave an overview of what I listened in a couple of courses on LinkedIn. I guess most of those opinions are correct, in the ideal World. I say that… Continue Reading →
Have you ever heard about the Scaling Agile @ Spotify (or the so called “the Spotify model” or “the Spotify process“)? Well, I am not a big fan of it, but some principles, adapted to the different companies structures, have… Continue Reading →
The best way to improve the quality of our work is to learn and keep up to date on new theories. And that is not all: even revising our knowledge is a good practice. I worked in agile teams for… Continue Reading →
You may remember my post, few weeks ago, about “NodeJS vs Java by Example“. I was comparing the same algorithm, the insertion sort, chosen because not extremely performing and therefore easy to generate a bit of delay, and easy to… Continue Reading →
I think it is useful to have a quick discussion on what happened about moving to serverless in the last 3 years. First of all, I want to clarify that there are many discussions in my company related that, even… Continue Reading →
I think it is important to make some examples when we compare languages and Runtimes, or libraries and protocols, as I did for my post on GPRC. This time is the time of NodeJS and Java. How did I made… Continue Reading →
Let’s clarify: I work with AWS since 7 years now, and not in one, but in two companies I have been forced to use Kinesis to develop components that didn’t need Kinesis. And every time I try to explain that… Continue Reading →
