Candost's Blog

Candost's Blog

Candost

I used to think that reading would make me wise. One day, ten pages before finishing a book, I realized that I had read that same book before. At that point, my perspective on reading and, therefore, my life had changed. Now, I don’t care how many books I read; I take many notes, connect dots, and share what I’ve found on my blog and newsletter. I’m interested in many things at the same time (I’m a multipotentialite). On this blog, you’ll find me talking to about multiple aspects of life like leadership, software engineering, philosophy, psychology, software architecture & design, urban & industrial design, exercising, finance, Formula1 Racing, eating healthy, and many more. I’m a software engineering manager; that’s my current job. At home, I’m a writer and an avid reader. I rarely watch TV, movies or TV series. I don’t have any social media account (except Mastodon where I have automated posting of my new articles). Hence, I often miss the popular culture references in conversations. That’s alright. I don’t have FOMO; I embrace JOMO. I rarely read fictional books.

Latest Posts

Things to delegate: Work that drains your energy. Wherever the work is running, and not so relevant for you anymore. Whenever the work is running and more operational work (in case you want to do more strategic work). Related Note(s):...
When deciding the person you're going to delegate the work, look for specific criteria and ask yourself a few questions: How much time would you spend when you delegate? How much time does this person require from you? How bad can their...
Designing Teams shouldn't be with instincts. Leaders should design frameworks to move their teams and define how they work, evolve, and succeed. While planning the organizational changes, leaders should also create team design rules to...
The most difficult part of facilitating interaction mode is to create an enabling team that consists of experts. Because experts rarely want to work as an enabler. However, I think staff engineers are the perfect solution for being in...
Inverse Conway Maneuver doesn't work alone. Knowing team interaction modes and team types helps us use the Inverse Conway Maneuver to our advantage. As I'm not fully convinced that the Inverse Conway Maneuver will work, I cannot see how...
For team interaction modes to work, managers have to work on creating the environment and consistently (and sometimes with big-bang changes, sometimes with deliberate actions) work on setting the expectations for the team. The managers...
Having facilitating team interaction mode should be across the organization. I think Quality Engineering can work in this mode for some organizations for a certain period. They can coach other teams to increase the quality of the...
Creating an X-as-a-service team communication mode has advantages and disadvantages. The biggest con I see is the operational cost of setting the team up. The forming stage requires deliberate actions and doing them consistently in a...
I used to think of system design as being formed by technical and communicational patterns. However, everything around software teams and technical infrastructure affects the system design: offices, team distribution, CI/CD,...
Organizations mistake collaboration as a good strategy and don't see its side effects. The effect of two teams collaborating on systems is sometimes invisible. Collaboration between two teams can enforce "great teamwork," and leaders can...
Sometimes, it looks like long-term collaboration is necessary between two teams that are both stream-aligned. But it doesn't fit into the collaboration team interaction mode framework (e.g., consumer and provider teams were meeting every...
When organizations are poorly managed, usually, there is chaos between teams: either more interaction than necessary or no interaction at all where it needs to be. Clearly defining the expected interaction mode will provide clarity, and...
Platform teams have a lot of organizational work besides designing and coding the platform. Without organizational work, they cannot function well. Organizations have to ensure that platforms' APIs are well-designed and documented. Their...
Getting the platform right is difficult because of the product pressure. Once the platform team works efficiently, it's fantastic to have because the team takes a lot of organizational burdens away from stream-aligned teams along with...
Using Complicated Subsystem Teams separates the complicated part to reduce the cognitive load on stream-aligned teams. Separation of concerns and decoupling are fundamental techniques in software engineering. The key part and difficulty...
Search Random