it's just weird how we phrase it as "remote doesn't work" despite all the evidence pointing otherwise, rather than an abject failure of management "i can only run teams if i can physically touch them" and "three hours of traffic and wearing headphones all day is peak productivity"

Bacurau foi um DOCUMENTÁRIO meus amigos.

I've been trying to push the vscode API in that direction 😅

it might be a bit boring but better tools for refactoring, type systems and lsp help but I want to know where are all instances of type X constructed, when are they sent across threads, where is field Y read etc. Things that let you plan and execute complex changes on legacy code.

Yeah, I remember we discussed this because someone (you?) had a PR to error on element access on never... But in the end we didn't figure out a way to distinguish between intencional and accidental nevers.

From what I recall, just one: we only error on property access to `never`, sadly. 🙁

Funnily enough this comes at a time when layoffs are ripping up existing systems, flushing irreplaceable organizational knowledge down the drain. The answer these managers give is "just use AI" because they are not competent to rebuild the broken system, or even see it.

I'm so sorry.

This is Omelette.