Hacker News new | ask | show | jobs
by ra0x3 704 days ago
+1 for not bringing up (even arguably) negative topics or discussing "dislikes" in an interview.

Sort've reminds me of that quote "Do you want to be right, or do you want to be married?"

1 comments

I don't totally get this point of view. What if your job involves evaluating things with trade offs?

OP didn't say they disliked TypeScript, just that it might not be the solution for all problems.

OP has made some questionable statements, that if said on an interview, would be a big red flag for me

> I also can wager that most people don't need type safety enough to ...

I think most of the industry has decided type safety is worth the effort

> For the tin hat owners out there ...

Dawning tinfoil hat ideas is definitely no-go territory in interviews

---

There is a difference between evaluating tradeoffs and coming off as a highly opinionated person that will make such discussions more difficult than they need to be

That's fair I guess. JSDoc over TS for a legacy codebase strikes me as a good decision.
Maybe, maybe not, it's context / company dependent decision. A full rewrite is an opportunity to pay down other technical debt at the same time, or open the door to fully new approaches.

It's more about how one engages in such a debate than the merits looking in from the outside. OP wanted to know why they are having issues in interviews, their language / approach is probably the root cause, not the merits.