A leadership commentary piece contrasts the deterministic world of software engineering, where compilers and tests give clear pass/fail answers, with the ambiguous environment executives face, where decisions involve incomplete information and competing priorities. It uses the example of a newly appointed CTO, Richard, to illustrate how technical purity can conflict with business needs once an engineer moves into an executive role.
talkingtech.online
· 2026-11-19
An engineering guide describes how staff engineers on platform teams—who typically lack product managers, roadmaps, or revenue metrics—can identify what to build next. It categorizes signals into four sources: system-generated signals like crashes and cost data, plus signals from users, the organization, and the broader industry. The piece details methods such as analyzing postmortem patterns and scrutinizing cloud costs and vendor contracts to surface opportunities.
sujithjay.com
· 2026-09-28
A senior engineer describes how he identifies which problems are worth working on as a staff engineer, in response to a mentee preparing for promotion. Rather than scheduling dedicated 'strategic thinking' time, he says he absorbs complaints and pain points from everyday conversations, meetings and chats, letting patterns emerge over time until a clear opportunity surfaces.
lalitm.com
· 2026-08-23