{"id":1142,"date":"2016-10-15T13:15:09","date_gmt":"2016-10-15T10:15:09","guid":{"rendered":"https:\/\/alexbolboaca.ro\/?p=1142"},"modified":"2017-01-03T12:46:40","modified_gmt":"2017-01-03T10:46:40","slug":"the-aftermath-of-the-three-problems-blog-post","status":"publish","type":"post","link":"https:\/\/alexbolboaca.ro\/software-craft\/the-aftermath-of-the-three-problems-blog-post","title":{"rendered":"The aftermath of ‘the three problems’ blog post"},"content":{"rendered":"

In my previous post<\/a>, I set out three problems that I believe software crafters worldwide should work on in the years to come to fulfill the promise of “raising the bar”. This is a quick update on its aftermath.<\/p>\n\n\n\n

Metrics<\/h2>\n\n

The blog post generated 430 views at the time of this writing, which you can see as low or high. I see it as “a few hundred people seem attracted by this idea, although we don’t know how many want to act on it”. We can work with that. The history of innovation shows that we don’t need more than a few people to work on these problems. It’s much more important to find the right group of smart and motivated people who are interested in solving them. The rest will follow.<\/p>\n\n

Reactions<\/h2>\n\n

The blog post generated a few reactions. Here’s a quick list.<\/p>\n\n

Eradicate legacy code<\/h3>\n\n

Despite it being the first on the list, and sounding crazy, I was surprised to get a total of one reaction. I don’t know how to interpret that, but I have a few hypotheses:<\/p>\n\n