>If you can make a decision and you don’t think it’s going to get you fired, just do it.

This advice only applies to people with enough experience.

I'm thinking of a certain ex-employee that followed that advice all the time, despite us constantly correcting him. Even on their final day, they was still insisting that they was doing good work.

To this day, we are still finding code they wrote or modified that is wrong or broken in horrible ways.

Why? Because they didn't have the experience to know the difference between a quick fix and a good fix, and when to employ them. (Hint: The "quick fix" is almost never good enough.)

My personal line is a long way away from "Will it get me fired?" and I've got decades of experience.

I've always said that programming is all about making assumptions. And I'll frequently send off an email stating some assumption I'm making and start coding based on that assumption. If I get corrected, I can change pretty quickly. But I'm usually right.

But just not asking? Forget it. If I'm unsure enough to bother with sending a 2-line email, it's worth asking.