This question got me thinking.
In IT often a technical interview will require you to write a bit of code to solve a problem, or implement an algorithm, or a question like 'What would you use XYZ technology for', (or, have you used xyz technology?).
Now it sounds cheeky, (but also very sensible!) but one could write a cheat sheet, perhaps outlining the pros and cons of various algorithms, and perhaps summaries of various technologies (so for example if they ask 'Have you used XYZ technology', you could consult your cheatsheet and say 'No, but I've done my research, and XYZ is used for...').
This would demonstrate that you're resourceful, you've got the initiative and smarts to know what's relevant etc.
Now of course, repeating word for word what's on your cheatsheet wouldn't looking particularly good, but so long as you were demonstrating that it's just a resource and that you've that you've got genuine ability behind you, it might be ok.
Now this could backfire if you got an interviewer who simply isn't impressed.
Question is - generally, for a good forward thinking workplace, is a cheatsheet a good idea (and even, is it already common for technical interviews)? What reasons to not bring a cheatsheet are there?