[spiffytech]

I learned that I can't talk through my thought process while in the middle of writing code.

During a remote interview I was asked to code up Fibonacci, an algorithm I'd implemented plenty of times before. The interviewer wanted me to share what I was thinking as I did the work.

I struggled and struggled and just couldn't get it. I lost my train of thought every time I described what I was doing.Eventually I was told I could stop.

After I hung up the call, I banged out the correct code in thirty seconds.

It's easy to walk someone through my code after it's written. But apparently I don't get to consider a problem space in $LANG and in English at the same time.

[rumori]

I had the exact same experience with writing code for Fibonacci in an unfamiliar online coding environment. I completely froze up, couldn’t think straight. It was really embarrassing and hilarious at the same time. These interviews take some practice, it’s very different from everyday coding. I can track down and fix the most complicated bugs in complex systems, yet bomb the most basic assignment if taken out from my comfort zone. As with everything it takes practice.