Richard Towers | Typescripting the technical interview

An homage to Aphyr's Typing the technical interview

@richardTowers
Thank you, that is beautiful. I laughed and cried.

I had to immediately forward this to my friend who is currently going through job interviews with TS assignments, where I occasionally help. And man these assignments are so damn rediculis some times. But this is on another level, thanks.

@richardTowers Interesting post! but did you skip a `Nil` after the last queen?
@gholk oops, yes you're right, I did. I couldn't copy paste the type from the popup so I had to type it out by hand
@richardTowers I tried on typescript playground and it give me the type definition of the Solution in sidebar
@gholk thanks! I've added a link to the playground to the end of the post, and credited you in the errata for the missing Nil
@richardTowers this is beautiful storytelling, in a long time, genuinely pleasant one too😍

@richardTowers i use this as an example when describing the difference between an application programmer and a systems programmer.

the application in this scenario is run entirely by the system, which means it was a systems programmer that built it.

An application programmer needs for a person to be able to play chess, even if only a contrived variation for a technical interview, to call their job complete-- and to do so would need to declare more than four variables.

@richardTowers This is genius. I actually love this kind of TypeScript (more so the type system than the eldritch runes.) In particular some of Gary Bernardt's talks opened my eyes to what was possible with the type system (i.e. https://youtu.be/KRMJIiGE0ds)

I've only had one job where I was paid to write TypeScript, and I was pretty much the only person at the company who would attempt to use things like dependent types and template literals. My coworkers would get very confused 😅

Statically Prevent 404s - Gary Bernhardt

YouTube