In my defense, the backend contracts change so often in early development the any just made sense at first…
Refactorings and changes are the prime reason to use TypeScript. You edit your data objects and get squigglies everywhere shit won’t work anymore. A godsend!
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
Refactorings and changes are the prime reason to use TypeScript. You edit your data objects and get squigglies everywhere shit won’t work anymore. A godsend!
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.
Record<string, unknown> ftw
Its sad how relatable this is
Sadly, this is the way.
I’d guess the lack of defined backend contracts is caused by the same issue that made you unable to fix those
anylater.Anyway, the frontend / backend split is stupid and ridiculous. It’s even worse because both sides usually include tasks that do need to be split up.