In the limited TypeScript I've done (only a few months so far), every single time I thought "oh well, let's leave this at any for now" or "ah, crap, ts-ignore u

In the limited TypeScript I've done (only a few months so far), every single time I thought "oh well, let's leave this at any for now" or "ah, crap, ts-ignore until I can think of a better way" or even "let's disable strict-null-checks for now, as fixing all those cases is too much work" has resulted in broken code down the line because assumptions that are not caught by the types have been invalidated. So I tend to err on more or better types for now. Some things can't really be improved of course, but that's where experience comes in over time in recognizing those cases.