When you contemplate the structure and effectiveness of your software departments, the concept of product teams and the strategy of vertical slicing emerge as pivotal part of the journey.

These methodologies can revolutionize the way products are developed and maintained, directly impacting their success and the adaptiveness of the organization. This post aims to explore the essence of product teams, their significance, and the practical steps to implement vertical slicing within those teams.

Raise your hand 🖐️ if you recognize this meme:

Do you agree with it? I generally do. In today's fast-changing tech world, it's easy to get lost in the 'rules' of coding.

It's important that we occasionally stop and rethink our methods—not to reduce the importance of solid coding principles, but to make sure our efforts align with the broader goals of our projects and companies.

Leads Horizons is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.

Have you ever read Conway's law before:

Organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations.

— Melvin E. Conway, How Do Committees Invent?

And considered how it relates to your experience upon entering a new organization and seeing its entire architecture? We will explore the different levels where Conway's law impacts and how to mitigate its effects if desired.

In 2024, Software has become the backbone of countless industries, it seems natural to equate software engineering strictly with coding. After all, code is the very fabric of software. However, I've come to appreciate that software engineering encompasses far more than just the act of coding. It involves understanding business needs, validating ideas, crafting user experiences, and so much more.

The reality is that while coding a solution is vital, it is also a considerable investment—both in time and resources. This investment makes it imperative to explore and validate options thoroughly before committing to a specific path.

Here, we delve into why software engineering is not just about coding and how a broader perspective can lead to more successful outcomes.

In the realm of software engineering organizations, the synergy and coherence of a department are often the driving forces of success and innovation. As an engineering leader, I've witnessed the transformative power of establishing common practices across teams.

These practices streamline operations and foster a culture of collaboration and continuous improvement. The key lies in identifying and implementing a “minimum common denominator” of practices that all teams can adhere to, ensuring consistency while accommodating the diverse nature of our projects and teams.

In the dynamic field of engineering, effective decision-making is crucial. From day-to-day team choices to strategic departmental shifts that align with company-wide objectives, understanding how to navigate these decisions is key to fostering a productive, innovative, and cohesive engineering environment. A well-established decision-making process is vital for several key reasons:

1. Clarity and Efficiency: It provides clear guidelines and roles, streamlining decision-making and saving time and resources.
2. Accountability and Quality: Assigning clear roles enhances accountability, leading to more informed and thoughtful decisions.
3. Transparency and Trust: A transparent process builds trust among team members, ensuring decisions are made fairly.

In every organization, decisions are made daily across various levels, to help shape the direction we collectively strive for.

TL;DR;

In essence, leadership and management are two sides of the same coin, each playing a critical role in guiding teams and individuals towards achieving their potential and realizing organizational objectives. By building trust and taking control in measure, you empower your teams to innovate, perform, and thrive in an ever-evolving landscape.

Have you ever worked in an organization that either seems too lax on the process or too stiff? What is behind that lack of balance? Are Leaders & Managers roles completely contradictory?

In the realm of organizational success, the distinction between leadership and management is not just semantics. It's foundational to how teams and individuals achieve their goals. While management is essential for ensuring tasks are completed, budgets are adhered to, and deadlines are met, leadership goes a step beyond, it cultivates an environment of trust, vision, and empowerment.

Welcome to our Continuous Delivery Bootcamp! We'll teach you the skills you need to get your projects out the door fast, without sacrificing quality. By the end of this program, you'll be a pro at transforming code into working software. Sign up today and start transforming your workflow!

This chapter we will do an example on how to build and validate our project in github actions.

Video

Watch the video on Youtube

This is a #functional #programming series focusing on the main concepts using #kotlin.

In this second chapter, we will initialize a project with gradle and kotlin

Video

Watch the video on Youtube