141: Maximizing Value by Breaking Constraints

DDD for business understandability and constraint mitigation

Thank you for reading Snippets of Text. Snippets from media about tech, programming, parenting, and more. This is a preview of a post available exclusively to paying subscribers. You can get unlimited access to all articles by purchasing a subscription.

Off Topic: Event-First Architectures Collaborative Patterns

In an event-driven architecture, the emitter of an event is decoupled from the processors that consume it, making the event itself the API. This decoupling enables consuming apps to evolve without requiring changes in the emitter. Consider the analogy of entering a room and the light turning on to react to an event. This contrasts with a command-based approach where the light switch is flipped to command the light to turn on. Instead of a single shared data store, an architecture with specific, targeted views is preferable. Consumers can store relevant data from events, often only requiring precise information. 

The true strength of the event-first process becomes evident when enhancing the system. In the command-based analog, knowing how to act lies with the person issuing the command. In the event-command pattern, the service is aware of the endpoints and APIs of other services and makes the necessary calls. 

[^]: Implementing Domain-Driven Design: Vernon, Vaughn

Unrelated: Creating a Culture of Learning and Growth

Build relationships early. Much of my time is spent doing written work, research, and talking to people. It can help when you need to pay social/political capital to take a stance on something. Staff-plus is about enabling others to do better work - to be a force multiplier. Try to become the engineer that people want to work with. Develop a relationship with your manager where they trust you, and you trust them.

Empathy for your users, in particular, is essential for all engineers to develop. As a Staff Engineer, you're a manager without the people aspect. By changing our habits and approach, we will revise the industry. By improving ourselves, we make the industry better.

A leader is a set of skills anybody can meet, no matter the title. To be a leader, we don't even receive any authority over others. We need to be consistent with our areas of responsibility. Being open about our strengths and weaknesses moves us closer to the role of leader. 

The only way to remain a long-term leader of a successful company is to create space for others to take recognition. Create space for others so your team grows stronger than your contribution. Several tactics help create an open space for learning and growth. E.g., pair programming, book clubs, mob programming, brown bags, etc. Help with guidance on current and future decisions.

Train new team members during their onboarding. As well as help the team grows in skill capacity and ability. Ask your sponsor how you can support their sponsorship. If you get folks pointed in the right direction when they join, that habit momentum will favor remaining aligned. You need to maintain a positive and productive relationship with your manager. Never shock your supervisor. Sudden surprises can shatter your manager's trust and respect for you, resulting in a complete and utter loss of faith.

[^]: Staff Engineer: Leadership Beyond the management track

Thanks for taking a look at the free preview of Snippets of Text. Please consider subscribing to the paid version if you find my work helpful. This way, I can spend more time developing new ideas to share with you.