560
everywhere I go (discuss.tchncs.de)
submitted 2 years ago by to c/programmer_humor@programming.dev
40 comments fedilink hide all child comments
 

cat looking inside box meme

  • yeah our project uses typescript
  • look inside
  • any
you are viewing a single comment's thread
view the rest of the comments
[–] 10 points 2 years ago (1 child)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 8 points 2 years ago (1 child)

    Typescript only prevents typing bugs... why did they have so many typing bugs?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 2 years ago (3 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 6 points 2 years ago (1 child)

    I believe you don’t have to actually use (meaning “compile from”) typescript to profit from it. If you maul the compiler options hard enough, you might get it to analyze JavaScript and provide type checking.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •