Surviving code interviews
Nobody likes them — neither the hiring side nor the hopeful developers. But since code tests are not going away, let’s talk about why they exist and how get through one alive.
I am Jonas
Latest posts
RSS feed migrated
It's on a static site now
The trouble with troubleshooting
Sigh. That didn't work either. Why can't someone else have already solved this? Maybe it's a bug? I'll upgrade and hope that works.
Reverting unhappiness
There are benefits to being happy with what you do beyond the mere feeling. To become happier we need to know the low points and take back some control over the causes of misery.
The scheduling session
Multitasking and interruptions? All bad! Unless you do it yourself. Then it's all right!
Falsify yourself
You've solved it! Until someone asks a simple question and you're stunned. Why didn't I think of that? Because you're hardwired not to see holes in your own solutions. Let's fix that
How to enjoy a good meltdown
It's down! Production is down! You're working at an intense pace yet you have a serene calm feeling. You are prepared for this. It's showtime!
Want to be great? Know a lot
Remember that time where you knew of a solution that no-one else did? And it worked exceptionally well too. I bet you felt like a great programmer. Let's make that happen again!
I don't understand this (yet)
You gently face-palm and let out a groan. Your bug is so obvious now. How did you miss it before? Thank goodness you didn't blame Bob publicly.
Getting unstuck
You sigh. Maybe the compilation didn't work? You recompile and run it again. Nope. Still the same problem. You stare out the window.
The test-plan
"The tests are timing out again" someone yells. "Alright I'll bump them" you instinctively respond. Then you pause and feel uneasy. Is there another way?