As someone OE, absolutely.

2 years? More like 3-6 months.

I just died a little inside. Thank you.

In their defense (maybe a stretch) it could be 1-tab indents with a 1-space display?

I’m trying for their sake.

I worked for a company that refused to use TypeScript because it “slowed devs down”. It was…a laughable period in my life.

And then I realized it’s python.

That’s what I did locally.

But a lot of this JavaScript wasn’t even transpiled/compiled for prod, just uploaded to a bucket and referenced directly. It was painful.

Typo’d property names when accessing was the biggest one. Assuming a property was one data type instead of another and not casting or handling it appropriately. Accidentally calling something like it’s a method when it isn’t.

I ran a bunch of plugins on my end to help with some of that, but many of the older or stubborn devs refused and would refuse anything but, like, vim with no add-ons.

110% agree. But…

One job I worked at wouldn’t let us do this because it created too large of a QA impact (lol). We were only allowed to modify code in the smallest section possible so that testing could be isolated and go faster.

At another job they mandated that TypeScript wasn’t allowed because it “slowed down development”. It was soooo laughable. The number of bugs introduced that could have been readily caught was absurd, but management never put the two pieces together.

In my defense, the backend contracts change so often in early development the any just made sense at first…

…and then the delivery date was moved up and we all just had to ship it…

…and then half of us got laid off so now there are no resources to go back and fix it…

…rinse, wash, repeat

What would be even more wild is if you edited/replied to yourself and said, “nvm figured it out”…only to later discover it and not remember what you did

I agree 100%

When you have 1000+ Cypress tests, for example, it takes time to run, plain and simple.

Now, if they were simple unit tests, sure, one could run thousands in a second or two, but they aren’t. Even headless, these just took time.

I worked for a company that required 95% code coverage but simultaneously complained about how slow tests ran.

🤷‍♂️

In a small company with a non-complex product, there is a chance that TS creates more slowdowns than not.

In a large company with multiple cooks in the kitchen and a complex product, I’m personally of the mindset that there is substantial gain from typescript. I’ve had coworkers tell me it’s bullshit, and then I do the smallest lift possible to convert and the amount of bugs it reveals are insane.

Is it necessary? No, probably not. But unless everyone’s a 10/10 dev working on the world’s simplest product, why not just do it and enjoy the benefits?

INB4 JavaScript blahblah, yeah I’ve added type hints to pure JS projects too and discovered bugs. At this point I don’t get it. Typical resistance I get is that it’s too prescriptive and lacks JS’s dynamic nature - well, fuck off, I don’t want to read through 200+ lines of code where you’re changing types and shit on me willy-nilly.

A long time ago I remember building a version of VS Code for Android that worked OK. Dunno if that’s still available.

You and me both. I’ve been parsing around 10-100 million row CSVs lately and…this will hopefully help.

Wow those benefits are amazing.

Wait so it’s possible a Senior Dev outside of London would make $35k??

Holy crap. That’d be a pretty substantial cut for me, but I guess that said, is the COL a lot less?