November 7, 2025
C-Suite or C-Ya?
Developers in C-Level Meetings
Engineers at the big table: one camp says run, the other says lean in
TLDR: The piece says engineers can add value in executive budget meetings by asking clear questions and doing quick math. Commenters split: one warns to skip the room entirely, another says it’s how careers are made—drama over survival vs strategy in the boardroom.
A Head of Engineering says developers in executive budget meetings can be secret weapons: ask dumb-but-necessary questions, care about the whole company, and flex quick math to catch bad assumptions. The vibe? Bring your calculator and your courage. He even nods to shares like ESOP (employee stock options), and the classic “blarp vs blurp” confusion that makes the room feel like an improv show.
But the comments set the room on fire. uberduper drops a scorched-earth take: skip the meeting entirely or your words will be twisted into office courtroom drama. His line sparked memes about the “C-Suite Hunger Games,” with devs joking they’d rather refactor a legacy codebase than explain “blurp” to Marketing again. On the other side, spullara strides in like a career coach: he built his whole path by showing up, splitting time between strategy and coding, and doing the homework to understand the business. Cue popcorn gifs as the thread turns into “Survivor: Boardroom Edition.”
The split is stark: Avoid the chaos vs Own the room. One camp says meetings siphon your soul; the other says it’s where promotions are forged. The article says be useful. The comments say choose your adventure—and pack snacks.
Key Points
- •C-level year-end meetings review budgets and plan the upcoming year, with engineering present to address developer-related costs.
- •The author advises asking clarifying questions to avoid assumptions and ensure shared understanding across teams.
- •Engagement with seemingly unrelated topics is encouraged because cross-department performance impacts engineering and budgets.
- •Developers should use quick estimations and formal definitions to identify gaps and clarify vague executive-level discussions.
- •Sharing a developer perspective on AI, motivation, automation, and standards helps align expectations and reduce burnout risk.