Developers in C-Level Meetings
Posted2 months agoActive2 months ago
radekmie.devOtherstory
calmpositive
Debate
10/100
Software DevelopmentManagementCommunication
Key topics
Software Development
Management
Communication
The article discusses the importance of having developers in C-level meetings to improve communication and decision-making, and the HN discussion supports this idea with some sharing their positive experiences.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
7d
Peak period
3
156-168h
Avg / period
3
Key moments
- 01Story posted
Oct 31, 2025 at 10:14 PM EDT
2 months ago
Step 01 - 02First comment
Nov 7, 2025 at 6:48 PM EST
7d after posting
Step 02 - 03Peak activity
3 comments in 156-168h
Hottest window of the conversation
Step 03 - 04Latest activity
Nov 7, 2025 at 7:43 PM EST
2 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45778729Type: storyLast synced: 11/20/2025, 2:27:16 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
- Try to find a way to not go to the meeting. Anything you say, especially the most insignificant part, will be used against _someone_ in an argument that doesn't make any sense. You're going to feel the need to correct their misunderstanding and misuse of what you said. You might even try to re-focus the discussion back to the important thing you were _trying_ to say. It only goes down hill from there. You're better off interfacing with a group of C-level people through documents.
- 1:1 meetings can work. Make sure you can back up everything you say with data.
- You're a developer, you can't estimate time and effort for shit. If asked, say you'll get with your manager or the PjM or w/e to get a date.
- Find out from the person that asked you to join what you should be prepared to speak to.
- If there's an agenda or documents that will be discussed, read them before the meeting. Doesn't matter if they plan to read it during the meeting.
- No hemming and hawing. If you don't understand what you're being asked, ask for clarification. If you don't have an answer you're confident in, say so. If they insist, prefix your crisp and concise answer with your level of confidence. "In my experience.." "From what I've read.." etc.
From my experience, execs want to know the current state, and also want to be able to intervene before a project derails. That's usually accomplished by open and coherent communication - a skill that is yet to be found by some developers. But you can work on it! ...if you want.