Latest articles

I ‘ve been asked a lot by colleagues and friends about the way I manage to stay focused and productive in the long run. This is a really tough question and I am sure that people out there use a great variety of techniques to accomplish this. Personally speaking, I follow a dead simple pattern.

React Hooks were officially released in February of 2019 and since then the frontend world has started changing rapidly. Other popular JavaScript frameworks such as VueJS are moving also to a more functional approach as we can see here so the future seems bright for Hooks.

In 2019 React is moving fast to concurrent rendering era. This change will be a massive boost for client-side apps and will help frontend engineers to tackle slow performance bottlenecks.

Consistency can easily become our friend or our foe. Being consistent is extremely hard but this is what it keeps us away from fulfilling our goals and our dreams eventually. Who said that this is easy right?

I love the idea of the minimum viable product. Identifying what is absolutely necessary for launching a new viable product and building it timely with discipline within a tight timeframe is a virtue.

I tend to listen and read really a lot about the meaning of React Hooks and how they help us to win the fight against evil classes that tend to pollute our codebase and blah blah blah. So guess what? This is a big lie.

There is this postmodern motivational advice that I seriously despise; “Surround yourself with people better than you”. What disgusts me more about it, is how it cultivates parasitic personalities and camouflaged egocentrism. Fuck that!

In 2019 even more and more companies are willing to hire remote employees in order to attract the best possible talent and reduce office costs. On the other hand people seek for new career opportunities worldwide because of this option. That said remote working flourishes and everyone wants to take advantage of this.

Recently I had a discussion with a colleague of mine about procedures and code reviewing and i realised 2 really important things. The first is that code reviewing is priceless and extremely beneficial but only if we follow some principles and we keep everything transparent. On the contrary, code reviewing can become a really painful process and ruin teams collaboration and relationships, if we do it wrong.

A fundamental skill in software development is realising when you have to relinquish control and actually doing it.

Yesterday I witnessed impolite behavior by an xterm.js contributor. The issue started when they voluntarily opened up a Pull Request that we were skeptical about accepting.

Every so often, I see developers getting excited about something new that just came up. This can be anything from a new machine learning tool to a front-end framework, containers, lambdas etc.

It’s been lots of years since I found any new app and enjoyed using it.

Lately, I have been thinking a lot about how things can go wrong when creating a user interface.

In May 2017 I bought a couple of tickets for a Premier League game from a very popular ticket selling website. The tickets were not delivered in time, because I didn’t include my flat number in the delivery address, so I missed the game.

Let’s get straight to the point; choose an SQL database for your web application. I think I can’t make my self clearer.

Anyone who has ever contributed code in a collaborative software project, had hard time doing so at some point.

Welcome to The State of Progress, a blog that hosts only pragmatic and timeless articles on developing and managing software.