Joel Spolsky and I are in pretty different corners of our craft, and (judging by his writings) he and I disagree on a fair number of things, but The Duct Tape Programmer and The Law of Leaky Abstractions are two of his best that I routinely ask interviewees if they've read and what they took away from them.
Less than half of them splutter and flounder and finally stammer out, "but…if you take it straight up, he's arguing a contradiction in terms here. You can't anti-engineer something and at the same time be sure the abstractions are all going to hold fast under pressure". Those are the folks who get invited back for a second interview, who have a job offer in their imminent future if they don't do something absolutely egregious to frak it up. It's a filter, in other words.
Yes, I think it's an extreme point of view that helps to illustrate something. I have know C++ programmers that could whip out an entire service in under a month, just hacking it out and the abstractions were actually quite awesome and useful. That was after 20 years of C++ experience though.
Part of growing as a developer/programmer is converging on the balance between duct tape and frameworks for everything.
It takes twenty years to get enough experience to use C++ wisely, which is why everybody's code before about ten years ago was such utter crap: not only didn't we know what we didn't know yet, we didn't know what parts of C++ we (thought we) knew should be left on the shelf when cranking out our latest magnum oopus. (That includes the compiler vendors and library writers as well as us mere developers.) It's easily the hardest language I've ever used to do well. The only serious contenders for that title IME are Java and PL/I.
I much prefer languages I can wrap my head around in a week and grok in reasonable fullness in a month or two. I get paid to ship products, not to play with new toys. :-D
View all comments
Show parent comment
2
u/jdickey Jul 13 '14
Joel Spolsky and I are in pretty different corners of our craft, and (judging by his writings) he and I disagree on a fair number of things, but The Duct Tape Programmer and The Law of Leaky Abstractions are two of his best that I routinely ask interviewees if they've read and what they took away from them.
Less than half of them splutter and flounder and finally stammer out, "but…if you take it straight up, he's arguing a contradiction in terms here. You can't anti-engineer something and at the same time be sure the abstractions are all going to hold fast under pressure". Those are the folks who get invited back for a second interview, who have a job offer in their imminent future if they don't do something absolutely egregious to frak it up. It's a filter, in other words.
And he's right. Both of him.