8

I feel like it might be a tiny bit (not much) better among React developers, but I ended up within one of those enterprise Angular till death companies, and it seems like nobody would ever doubt their Typescript skills, yet nobody actually understands Typescript at all.

In theory, I love Typescript. But you can abuse it to a point where it's almost as painful to work with as normal JavaScript.

It's not that I'm a master of Typescript.
But while I feel like I'm the only one understanding the mental model behind Typescript and also get stuff like mapped types or why you might wanna replace your enums with as const assertions, the rest calls themselves Typescript developers in their CV, no doubt. But It's way to easy to write whatever Typescript, while it's not as easy to reel get the hang of it.

Comments
  • 6
    That's 100% of so the places I've worked at that use TS. They just don't know what the fuck they're doing with it.

    Maintaining or reading it is about as awkward as the first time you have sex.

    Nothing is where you expect it, things don't work when you expect them to, and all the toys you expected to help just make it worse.
  • 5
    The first time I had sex was done within 20 seconds at most, probably much less.

    Unfortunately, maintaining problematic TS is not behind you after 20s.
  • 1
    The first time I had sex was done within 20 seconds at most, probably much less.

    Unfortunately, maintaining problematic TS is not behind you after 20s.
  • 4
    Lots of stuff in angular are not typed properly. The fucking angular html template language is worse than JavaScript.
  • 4
    @sariel the team I work in, they all profess to love TS but then don’t even know how to use freakin’ generics, and don’t understand why you would use "as const" on a key-value object in a constants file !
  • 3
    @black-kite frontend devs masquerading as c devs.
  • 0
    I know them, they argue that const is for constants only and let should always be used
Add Comment