2 ms·
So, this discussion reminds me a lot of discussions in logic programmig circles about why so many programmers can't learn to program in Prolog, no matter what.
by YeGoblynQueenne 11y ago
So, this discussion reminds me a lot of discussions in logic programmig circles about why so many programmers can't learn to program in Prolog, no matter what. There's papers dedicated to the question, people who had done research on the question back in the '90s when Prolog was still popular (yeah, it was, google it). The verdict: no verdict. Some few special and magical people seem to be able to learn to program in Prolog, but the majority can't.
Well then, why not set the bar for who can program and who can't on who can code in Prolog, rather than who can write FizzBuzz? If the point is to sort out the men from the goats, or whatever uncle Joel said we're trying to sort out, surely using Prolog as the sorting tool would leave many, many fewer "real programmers" than FizzBuzz. Hell, we could even combine the two: FizzBuzz in Prolog! See how well you can do at that, internets!
And why stop at Prolog? There's languages that are way, way harder to program in! Hey, if you're a Real Programmer you should be able to write FizzBuzz in, dunno, Ook. Brainfuck. Leboge? Mondrian? Perl, even?
Or maybe, I don't know, we can start asking people to show us what they can do instead of trying to find things they can't? Does that make sense to anyone else? I'd personally love it if people who want to hire me took the time to check out my github and the git repository I'm serving off my public server, in order to get an idea of the things I have already done (and so demonstrably can do) rather than trying to catch me with my pants down in front of a whiteboard.
Look. I write a lot of code. I go over a lot of code I've written. I'm an idiot 80% of the time, but the other 20% of the time I figure it out, fix my bugs and go to town. It works, OK? If interviews can't appreciate this balance then they 're useless.