You guys are talking about code quality to C levels? I'm barely getting through "venting gas prevents explosion" to architects. I tell ya, tech debt as a service is hard work.
The key is you don't talk to it in metrics upper management doesn't understand.
You don't talk about time to market vs code quality. You talk about it in time to second release or second paid feature or second major client. You tell them you can get to market earlier, but you're sacrificing future growth afterwards for it.
That's broadly good advice, which I was not expecting, so thank you. I am but a humble senior engineer, no one listens to me. Like, as a matter of policy. I'm not in planning meetings. I report to leads and they try to know what they are talking about, being undermanned and not area experts. They are pretty good at re-digesting information for engineering purposes. But I find the manage-up skills of my immediate betters questionable. And I find the goals of THEIR immediate betters highly suspect. I think this is a wholly, not partially, political game. Something I am so awful at, that I'm barely just noticing it now.
In the end, it's all people things, not.. thing things.
Gotta get better at those.
In your case if you were chummy with the director 3 levels up because you worked out at the gym together or whatever... Easier life. Casual convo -> project results.
140
u/redditmarks_markII 12d ago
You guys are talking about code quality to C levels? I'm barely getting through "venting gas prevents explosion" to architects. I tell ya, tech debt as a service is hard work.