That does sound like a bad org tho, sorry to say that.

Not to disagree of course that time is limited, but in my experience, optimizing it this harshly leads to poor results, because eventually, you just get leapfrogged by reality.

Hyper-optimized systems are brittle and can't really adapt to the market changing.

But yeah, I guess they still need developers. Just doesn't sound like a fun job :D

▲

vibe_that_works 4 hours ago | parent [-]

Just trying to fix the misunderstanding: I am not saying that you will have a literal 25 seconds meeting with your boss's boss. I am just making a math argument taking typical orgchart ratios.

So let me take this a step further. You want to meet your boss' boss for 10 minutes to present them something. 10 minutes of his time are an equivalent of more than 20 hours of your time. So if your initial idea was to "take maybe 1-2h" to prepare for this -> You are underprepared by at least one order of magnitude.

	▲	ImprobableTruth 44 minutes ago \| parent \| next [-]
		This is a very strange mindset. Even if you want to treat everything as sort of billable hours this doesn't really make sense because the average boss's boss's isn't paid anywhere near 144x. If a SWE spends 100 hours to save their boss's boss one hour, they're wasting a ton of money.
	▲	hypfer 4 hours ago \| parent \| prev [-]
		I mean I am no expert, but to me it sounds like the org you're describing seems to lean away from the "engineering" side of things and into the "org for the sake of org". Which might not be ideal, because "orging for the sake of org" to my understanding consumes significant resources not going into building products/marketshare/shareholder value. But then again, I'm no hiring manager in such a structure, so this is probably just an uninformed take.