/Management

5 Non-Verbal Behaviors Killing Team Health

- Raviraj Achar tl;dr: Raviraj shares annoying non-verbal behaviors, how he avoids exhibiting them, and how to deal with them. These include: (1) Silent but Irritated - the person that rolls their eyes when they hear something “stupid” or exhales heavily when someone disagrees with them. (2) Annoying Interrupter - they appear eager to interrupt the speaker and can’t seem to wait for their turn. This behavior can be distracting when the speaker is trying to make their point. (3) Ever Confused - The person gives a puzzled look to everything you say but asks no follow-up questions.

featured in #506

Overcoming Event-Driven Architecture Complexity With An Event Gateway

- James Higginbotham tl;dr: EDA offers flexibility and scalability, but as your architecture grows, complexities arise. Message receivers struggle with filtering, third-party orchestration consumes developer time, and webhook integration becomes challenging. James explores how event gateways can address common scenarios that increase EDA complexity.

featured in #506

The Remoteness Of Remote Work

- Kailash Nadh tl;dr: “We transitioned to being fully remote during the first pandemic in 2020. It worked out great in the first year, started losing its sheen in the second year, and became detrimental to creativity and collaboration by the third year. It failed for us in the most critical areas. We then made the collective decision to switch to a “hybrid” mode, where about 10% of us involved in creative and decision-making endeavours now come to the office three days a week while 90% of us continue to be fully remote. The hard lesson is that effective, long term remote work requires specific skill sets and DNA to pull off.”

featured in #506

How We Decide What To Build

- Ian Vanagas tl;dr: “There is a point in your product journey where what to build next goes from obvious to unclear. The options seem endless and choosing correctly can be the difference between a thriving product and a failing one.” Ian discusses how to navigate this. 

featured in #506

Meetings For An Effective Eng Organization

- Will Larson tl;dr: "I’d like to recommend 6 core meetings that I recommend every organization start with, and that I’ve found can go a surprisingly long way. These six are split across three operational meetings, two developmental meetings and finally a monthly engineering Q&A to learn what the organization is really thinking about." Will discusses each in depth. 

featured in #506

Meetings For An Effective Eng Organization

- Will Larson tl;dr: "I’d like to recommend 6 core meetings that I recommend every organization start with, and that I’ve found can go a surprisingly long way. These six are split across three operational meetings, two developmental meetings and finally a monthly engineering Q&A to learn what the organization is really thinking about." Will discusses each in depth. 

featured in #505

An Open Letter To Auth Providers

tl;dr: The first job of any auth company is to protect its customers – before anything else. Somewhere along the way it feels like a lot of auth providers lost sight of the thing that matters: You, their customers.

featured in #505

Have Concerns And Commit

tl;dr: “I lead a couple of teams. I could use a gut check on decision making. how do you convey a top down decision (a decision that you don’t buy in entirely) to your team? something other than “hey, leadership wants x, I see a, b, and c as potential pitfalls in x. I have conveyed my reservations. now it’s time to disagree and commit”” The author breaks decisions into three types - non-material, material and critical.

featured in #504

Headline Driven Development

- Slava Akhmechet tl;dr: Process involves: (1) Decomposing the project into a stream of headlines. (2) Picking an aggressive ship date for the first headline and working hard to meet it. (3) Having everyone focus only on one headline at a time - the upcoming one. (4) Ignoring everything else that doesn't help ship the current headline. (5) Once a headline ships, switching to the next one and repeating. This process works well as for three reasons - headlines is how humans process change, prioritization is easy and setting deadlines is effective. 

featured in #504

3 Hours to 3 Minutes: How Mobile reCell Is Importing Customer Data 60x Faster

- Will Genesen tl;dr: Mobile reCell streamlined their customer data import process, reducing file cleaning time from 3 hours to 3 minutes. By leveraging the pre-built validation library and intuitive interface with smart suggestions, they quickly set up validations for key workflows. The engineering team fine-tuned the implementation to focus on critical data points while allowing flexibility for less critical customer data. 

featured in #504