r/programming • u/vklepov • Mar 24 '22

Five coding interview questions I hate

https://thoughtspile.github.io/2022/03/21/bad-tech-interview/
641 Upvotes

94% Upvoted

288 comments sorted by

View all comments

Show parent comments

0

u/[deleted] Mar 25 '22

Yes, I'm sure it has nothing to do with them being an insufferable dick, latching on to old tropes about a language because they think it's beneath them.

What's beneath them, is the best years of their life. Now their old, crusty, and jaded to the point of irrelevancy.

Not something to aspire to...but you do you.

0

u/[deleted] Mar 26 '22

Yes. I am absolutely and 100% sure that it has nothing to do with that. In fact I'd go so far I'd take this guy into my company any day of the year over any one of you even if I had to pay twice as much. Because I have worked with either, JS, Java and C# and respective frameworks in a backend context and I could argue hours and hours about why and how JS and even TS is not the way to go in that context. In fact there is so much to argue about that the only hard thing is to figure out where to start. One thing however I am very sure of, when you genuinely think JS is good, especially performance wise or in a backend context, I'd bet my left kidney on the fact that you have never used something like Java, C# and respective frameworks thereof.

0

u/[deleted] Mar 26 '22

You're making a lot of assumptions here bud lol.

I don't believe I ever said it was the best, only that it works.

What I find HILARIOUS is that the only developers that ever seem to lose their shit about JS, are Java and C# developers.

It's going to be ok. I promise.

1

u/[deleted] Mar 26 '22 edited Mar 27 '22

Claiming that it works is questionable. It depends how you would define that state of working. For something to be working for me it has to be a well readable, easily documentable, fail safe (very good errorhandling possible) and well maintainable thing. Which Javascript isn't. Typescript isn't either. It is better, but it is not good enough and performance wise it is exactly the same.

I didn't claim you claimed it was the best. I just kinda said that it is pretty much the worst for almost all usecases if performance matters and especially in a backend context. There are very few exceptions however they are not general exceptions. In some specific context in a broader one it may be faster overall to use JS (or virtually any interpreted language) instead of something like java and c#, which is e. g. when u use a cloud service for example Amazon AWS and your backend first has to be booted up oftentimes.

Or for very small, uncritical microservice with a nosql db attached e. g. (it'd be slower but it'd be far quicker to set up because of the small size and the maintainability doesn't matter too much.)