zlacker

They are forcing people to write Typescript code like it’s Golang where I am right now (amongst other extremely stupid decisions - only unit test service boundaries, do not pull out logic into pure functions, do not write UI tests, etc.). I really must remember to ask organisations to show me their code before joining them.

(I realise this isn’t who is hiring, but email in bio)

>>andy_p+(OP)
Have you seen Java people write Python? Same vibe :)

>>andy_p+(OP)
Ah yes. I love working at places that hire experts just to tell them how they should do the work they're an expert at.

>>andy_p+(OP)
I do this and think it works really well...

myfunc(arg: string): Value | Err

I really try not to throw anymore with typescript, I do error checking like in Go. When used with a Go backend, it makes context switching really easy...

>>theshr+W1
Reminded me of this classic talk https://www.youtube.com/watch?v=o9pEzgHorH0

>>candid+Y4
They still throw and just have millions of try catch blocks repeated everywhere around almost every function :-/

>>theshr+W1
Sure have: https://youtu.be/wf-BqAjZb8M?t=831

>>candid+Y4
I do actually love returning errors in TS. It solved most of the problems I have with error handling.

>>chamom+yB3
Yes not terrible, I think throwing is often worse. I do think that Golang forcing you to deal with Errors immediately is just a bit extreme, sometimes it’s nice to have a choice or create abstractions about how to handle them.