Stanford CS9: Problem-Solving for the CS Technical Interview

Re:Stanford CS9: Problem-Solving for the CS Technical Interview by avip on Monday January 15, 2018 @05:20AM (#16149682)

Having less time to "learning new stuff to stay relevant" makes us de-facto less hirable. The "github" thingy is just a proxy (as is the "whiteboard CS exercise").

[ Parent | on HN ]

Re:Stanford CS9: Problem-Solving for the CS Technical Interview by virgilp on Monday January 15, 2018 @05:37AM (#16149736)

I actually do learn new stuff. While on the current job, I've been doing:

- Code-hinting (semantic analysis) in an IDE - Product management - Low-level JIT codegen & optimisation (for ARM Neon & Intel SSE) - Some datascience (technology/ product evaluation for a 8-digit aquisition) - One of the early contributors to a web standard - Distributed systems, bigdata (mostly graph-processing at quite big scale - Facebook-big)

and probably other stuff I can't remember right now. I worked in half dozen different programming languages. I'm pretty sure I've "stayed relevant" more than the average Joe, but you wouldn't know it from github.

[ Parent | on HN ]

Re:Stanford CS9: Problem-Solving for the CS Technical Interview by phkahler on Monday January 15, 2018 @08:34AM (#16150362)

If you're not learning on the job you should probably find another one that's more challenging.

[ Parent | on HN ]