Meandering On Tech leadership

I believe in freedom with responsibility. With freedom, you gain ownership, allowing developers to take responsibility for the outcomes of their work.

This is why it's crucial to always question the "why" behind our actions, understand the "what" we aim to achieve, and leave the "how" to those who actually perform the work.

Enforcing rules can ensure technical alignment, which is beneficial. However, it can also stifle creativity. It's important to strive for minimal rules while maintaining consistent delivery, managing maintenance, and fostering innovation.

I believe that platforms and processes should have minimal constraints while implementing enough guardrails to support good ideas and filter out bad ones.

Going too far with this approach can lead to a chaotic tech environment with multiple languages, frameworks, and tools, which is not sustainable and should be avoided.

In such cases, the process should guide you. Roadmaps and decisions should be collaborative, allowing the team to provide input. Freedom doesn't mean unlimited freedom to build and deploy without consideration. Ideas need support. Introducing Rust into a Java environment could be challenging, but with compelling arguments and better alternatives, it should be considered. The key is to have a platform for these discussions.

It is in such situations where you can share your tech philosophy, align on details, and drive innovation without compromising quality.