“Fábio Miranda is a Commit Engineer who specializes in developing Web Applications and sees beauty in designing systems and making sophisticated requirements and technologies evolve into simple solutions and unique user experiences. He enjoys spending time with family playing video games, watching movies, and traveling.”

“A common scenario is when an early engineer has the company grow around them. They wonder whether they should become a manager so they can feel like they’re making an impact. I think that’s the worst thing to do, because it’s probably not what they’re best at and not actually what they want to do—they just think it’s something that helps them become higher scope or more relevant in the organization.”

“Invest in engineers and make them part of the conversation when it comes to planning and setting goals. Instead of just saying that I’m going to hold a hard line at 20% allocation on x, I’d rather empower someone to have a seat at the table and drive the direction of what we’re going to do.”

In this edition of our peer-to-peer Q+A, Commit community member Fábio Miranda asks for suggestions to help Engineers learn and progress with growth hacking.

“The first crisis is going to be a big opportunity for trust building. Look for those situations and really go for it. Leave it all on the floor with that first crisis because it’s going to pay dividends later.”

“In my less guarded moments, I refer to myself as a bureaucrat. Because bureaucracy is actually a very software-like scaling model. It’s not necessarily a bad word. Bad bureaucracy is bad and good bureaucracy is good.”

“If you have your unique set of engineering metrics and the business people have a bunch of different metrics, you are going to be misaligned. Sharing the same goals helps you fight that.”

Commit Engineering Partner Anh Nguyen discusses his approach to building a tool to enhance the connections between the Commit community.

In this edition of our peer-to-peer Q+A, a Commit community member asks for assistance creating automated changelogs with a trunk-based branching strategy and a build-once, release-many-times mindset.

“The overall concept of the application is simple. There will be different modules or plug-ins that connect to one another to create a data pipeline.”