[bfung]

> Engineers aren't generally setting the priorities on what gets fixed

A good engineer would be like: “f—k it, I fixed it.” And the priorities would then get shifted around it.

Identifying when this is the right time to act and fixing it often makes the engineer gain seniority.

(Yes, it only works when both business and tech are broken. If it’s just the tech broken, then engineer will probably get pipped for working on wrong thing)

[servercobra]

I'm not sure how an engineer could be like "f--k it, I fixed it" to the company's business and pricing model.

[otikik]

By being 10x, full-stack, and a ninja rockstar.

[bfung]

The context to my post are the reliability issues that def. can be instrumented and fixed.

Business and pricing model not so much unless the engineer is willing to add the Sales prefix to their engineer role ;)

But even the pricing model - measure and compare the costs, competitors, and value derived (ok, commodity now vs 5yrs ago) and work with people pitching prices.

That’s still designing, analyzing, measuring systems - prices instead of code - definition of engineering.

[spoils19]

I've done this multiple times in my career.