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.

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.

Entire software engineering community debates on the influence of current AI revelations on our industry. Most people tend to agree that AI will land an impact on how software is going to be built in the upcoming years - a good idea would be to prepare yourself and your colleagues for a change that will happen, or at least be aware of what may happen.

In the final part of the series about learning, I'll focus on discussing topics of knowledge retention - from Ebbinghaus Forgetting curve, through plastic platypus learning up to PKM systems, commonplace books and Zettelkalsten.

This is the second post in my series about my different levels of awareness around the topic of learning. This time I'll be describing areas like 'Just in Time' versus 'Just in Case' learning as well as the topic of 'Deliberate practice'.

It's difficult these days to keep up with constantly changing technology. The common problem is proper motivation or discipline, but lack of direction or weak retention may be equally disturbing. This post is a first of a series about my approach to constant learning.

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