Many engineers wonder what it takes to turn into Staff engineers. It's a huge topic and I'll take a look at only one of those aspects - the ability to identify cross-team technical work.

I've finished reading "Modern Software Engineering" by Dave Farley. In the first part of the book, Dave explains his definition of engineering and it resonated with me. What is it?

After being in GAT for over 2.5 years and working closely with CTO, I've observed and learned a lot. Here are some of the top lessons about leadership I took out from the experience.

We are in the second half of 2023 and our approach towards remote work has shifted since the start of the pandemic from love to doubt. For a long time in IT, it was considered to be a benefit, what has changed since then?

Since the beginning of the IT industry, we couldn't find a decisive answer on how to properly measure software engineering productivity. In the last five years, there have been many discoveries on this topic - in this article, I'll try to unravel and connect the dots between the three most extensive frameworks that could bring us closer to solving the productivity puzzle.

Every company wants to have the best engineers they can afford. Obtaining them is hard, but keeping - even harder! In some cases, it may seem that promoting a strong engineer to a leadership position may be the biggest form of recognition and a reason for them to stay in the organization. I think it often leads to big mistakes, and here's why.

Life would be so much easier, if we could just get user manuals to understand other people. We would just read a rough summary before the first encounter, highly increasing chances for great first impression. If we would spend more time with this person, we could look into the details in the manual, get the nitty gritty details. What stops us from doing that?

While working with people, you constantly battle through tough choices. Multiple times, each decision will have their solid arguments and supporters. The 'Washington Post test' may be an useful trick in your toolbelt to make that choice easier.

For over a year now I'm working in GAT as a full time engineering manager. During that time I've basically stopped contributing to the codebase. Recently, I've got opportunity to commit a couple of small updates here and there. And I've learned a lot thanks to that.

Netguru is a big software house in Poland. When I browsed their website some time ago, I've found an interesting resource - a company guideline for project managers. Is it worth reading?

Discover powerful leadership principles from Jocko Willink's Extreme Ownership book that can transform your approach to responsibility, team management, and personal accountability.

Discover key insights and practical lessons from The Phoenix Project, the legendary DevOps novel that revolutionizes IT operations and software delivery practices.