Topic: Communication

A senior engineer stepped into a first-time lead role and discovered that the real shock was not fewer hours of coding. It was realizing that a full day could be spent reviewing, mentoring, estimating, and unblocking, yet still feel invisible because the work had shifted from personal output to other people’s growth.

This piece is about that shift: what I had to trade when speed stopped being my main source of value, and why the manager side of the role turned out to be harder than I expected. It is also about what makes that transition more complicated in an AI-heavy code review culture, where code can look polished long before the underlying fundamentals are solid.

Modern B2B sales has evolved from annoying persistence into systematic manipulation, using tactics that exploit identity, manufacture intimacy, and weaponize professional boundaries.

These approaches persist because the conversion rate justifies burning bridges with the majority of prospects.

This article dissects the playbooks from an engineer’s perspective, revealing why they work, who they target, and how we can collectively demand better.

Code reviews can feel slow and effort-heavy, yet a subtle shift transforms the whole experience.

By bringing people together in a pair setting - live, synchronous conversations - teams unlock sharper insight, quicker alignment, and smoother momentum.

A glimpse into why this approach quietly outpaces the usual flow.