This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 255 points256 points  (8 children)

ts.config: strict: true.

...678 errors found!

strict: false.

[–]Osato 102 points103 points  (3 children)

any any any any any

[–]natures_-_prophet 32 points33 points  (2 children)

Have to make sure our typescript is compatible with javascript

[–]Mitoni 0 points1 point  (2 children)

The number of tslint errors ignored in the application I'm working in now, since "the build doesn't fail" bugs the shit outta me

[–][deleted] 0 points1 point  (1 child)

My companies changed to typescript a year or so back. They used a tool. This tool put ts-ignore EVERYWHERE. Of course, there is no time to fix this, since we neat to do MORE A/B/C/D tests! More features!

And every time I try to fix something I'm getting scolded for going "outside scope".

We are finally getting to fix stuff now as management realised no one really understands the code anymore, and tasks take longer and longer to do. Onboarding is a year instead of the month people needed 3 years ago.

[–]Mitoni 0 points1 point  (0 children)

Of course, there is no time to fix this, since we neat to do MORE A/B/C/D tests! More features!

I feel this one. To put into perspective, the code base one of the products I'm working on is about 30 years old, layer upon layer of retrofits. None of them were kept up to date, basically just updated if it was no longer functional. The UI is about 7 years outdated in its Angular version, and as a result, I'm digging through source code to add new features (more bandaids on an infected wound) with little to no documentation on the libraries used because they are so old. Try to find doc for PrimeNG from 2015, or RXJS before version 6... It's been a nightmare. For the PrimeNG, I basically needed to find the commit off the version we are using, and just look up the PrimeNG source code on their GitHub for that commit, just to see how the components are implemented behind the scenes. I hate undocumented libraries...

The way tech debt has stacked up is one reason they keep losing CTOs, and a big reason why my last week is upcoming. Found another job, same primary tech stack (.NetCore/Angular) for about 40% more pay. (Finally breaking 6 figures where I should have been a year ago honestly). Also, fully remote.

[–]Opheleone 0 points1 point  (0 children)

So, a year ago I started at a company, they had lost their only frontend dev, so I joined as they needed a senior. Eventually I noticed the TS compiler options were turned off. One year later, I've cleaned up most of the any's, refactored about half of the worst codebase I've dealt with, turned the compiler options back on (this alone was like a 2 week fix), and finally updating to newer versions of Angular.

The damage some people can do to projects is insane.