Sign In

Thiago Valentim

Highlights

Aug 11 · linkedin

Productivity in software development certainly comes with its challenges.

I remembered a situation 15 years ago when I was freelancing on an internal system.

As I improved the efficiency of my code, delivering less for each new feature, the manager misinterpreted this as a decrease in productivity. He believed that productivity was about writing more code, not less, and decided to reduce my pay.

This misconception about productivity persists even today. In the past, lines of code (LOC) were often used as a measure of productivity, but now we understand that there are far more nuanced and effective ways to assess it.

For instance, a year ago, I diagnosed a team that was seen as highly productive. The CEO wanted to replicate their success across other teams. However, I discovered that the team inflated their so-called productivity.

They filled their kanban board with micro-tasks, which made their output appear impressive on paper. After each sprint, the manager would proudly highlight the number of tasks completed without considering the true value or efficiency of the work.

In my approach, I deliver business results with minimal effort, focusing on efficiency and effectiveness rather than just output. So far, this approach has been successful.

I could also dive into the quality topic, but I’ll save that for another discussion.

What strategies do you use to boost productivity in software development?

Jul 26 · linkedin

Today, we had an important deployment from a technical and business perspective. And it is Friday.

Deployment represents a risk to the stability of services. Why are deployments on Fridays often considered a bad idea? It depends on several factors, such as:

  • How many developers will be available to fix and support the product over the weekend?
  • What is the complexity of the deployment?
  • What are the risks associated with the deployment? -What is the recovery and disaster plan?

If there are minimal risks, the deployment process is mature, and the company fosters a safe environment where developers can perform their best without generating risks. Friday deployments do not represent significant risks.

Moreover, I have seen companies experience production issues due to flaws in their software development life cycle (SDLC), regardless of deployment day.

What are your thoughts on this?

Related Questions

What projects has Thiago Valentim worked on at Trifork?
What are Thiago Valentim's main technical skills?
How did Thiago Valentim transition to a Principal Software Engineer role?
What is Thiago Valentim's educational background?
Does Thiago Valentim contribute to any open-source projects?
Thiago Valentim
Add to my network