Occasionally (OK, maybe more than occasionally. Maybe more like every fu**ing time) I am in an Interview Situation, I find myself on the spot on topics I feel I *should* know more about – and I have to pipe up with a clear-to-all unsatisfactory response to key questions. Rather than kick myself and let the perfect answers come to me in REM sleep mode (never to see the light of day), I’ve decided to try to track these disappointers here. Then, answer them. One by one. Completely. Branch from them, roam the Graph of Semantic Relatedness from these answers. Explore the Humanly Knowable about them.
My theory is that I’ll never run out of items to add to the list, no matter how much I branch and roam and recurse and traverse said Network. Unless, of course, I stop going to / administering Interviews / Sales calls / Meetup bar sessions / etc.; -or- I stop meeting new challenges. I hope neither of these things ever come to pass.
Without further wafflage:
- Code coverage tools for C++? DUH Rational Coverage …
- Name of method that invokes a method on an object in Ruby: NO it’s NOT “call” you MORON.
- Open source NLP tools? Come ON. At least mention Lingpipe. That’s off the top of my head …
- What are you *best* at? Hmmmm. Uh, waffling in Spanish, Oh wait, I meant Producing Suibstantially Perfect Code at Top Speed while Communicating Well with All Stakeholders. Right?
- Other code quality metrics besides complexity, coverage, style? Uhhhh Cohesion for one …. Performance. Volatility. Memory usage.
- My Primary Interest / My Dream Job? Oh clearly it’s whatever you want to hear. So, that would be …?