We all want to look at good things. Promise chains were bad things. When I see bad things, I am willing to make the change. So should you. And we should ask before we change. GP was caught off-guard. That is not what we want.
We good?
We all want to look at good things. Promise chains were bad things. When I see bad things, I am willing to make the change. So should you. And we should ask before we change. GP was caught off-guard. That is not what we want.
We good?
> corporate tone
oof, maybe not wrong though.
I don't look at things for a living, I trade time for money with the expectation that my time has a multiplier on revenue, profit, and team health/productivity. I guess I've seen enough legacy code at this point that I don't have any desire to change it just because there's something better, changing stuff that works has to be a reasonable balance between tech debt/maintenance/quality of life things, vs features/uptime/performance. Of all those things, features make the most money right? So why would I want to spend time refactoring things when I could make measurable, incremental improvements somewhere else? Spend all day in the same system? Sure. Drive by refactorings? Absolutely not.