3 ms·
After 4 years at Accenture with a responsibility for 'process' in one's title and enough free time to gain a familiarity with Dilbert cartoons but not enough to
by pvg 17y ago
After 4 years at Accenture with a responsibility for 'process' in one's title and enough free time to gain a familiarity with Dilbert cartoons but not enough to consider the possibility that perhaps people have thought deeply about these problems before. Maybe they even wrote papers.
http://en.wikipedia.org/wiki/No_silver_bullet http://en.wikipedia.org/wiki/No_silver_bullet
And they did, except better. They even came up with that title, except better.
- swombat 17y agoThere are no such thing as old jokes, my friend. To a newborn, every joke is a world première.
- pvg 17y agoI sort of expect someone who's held a job in tech and self-describes as a CTO of a start-up to actually know some of the good old jokes. My expectations of newborns, are, as you suggest, less stringent.
- swombat 17y agoI tend to write for my readers as opposed to writing for myself. I've rarely found out something that I didn't already know, from reading one of my own blog posts! It seems you got this impression from reading this post that this is a new realisation for me - it's not, I just happened to write about it now. I'll try to make that clearer in future posts.
- pvg 17y agoIt seems you got this impression from reading this post that this is a new realisation for me - it's not I didn't know you were the author of the post. The impression I got was that you were blithely unaware of the basic literature on the subject. And really, if you're going to make a post called 'No best practices' and don't reference Brooks at all, it's hard to come up with explanations other than 'plagiarism' or 'ignorance'. In fact, while I have you on the line, let me ask you directly - had you read the Brooks essay?
- swombat 17y agoYes, I have. I'm not quite sure how "someone wrote a related paper 30 years ago" prevents me from writing a blog post on a topic that I want to write about, though.
- pvg 17y agoWell the thing is, someone actually wrote a seminal, much quoted paper 30 years ago. You wrote a "related" platitude-laden derivative and borrowed the title 30 years later. Nothing prevents you from doing that at all. Common decency suggests you should reference the original, if you were, as you claim, well aware of it. That's all.
- swombat 17y agoPlease note that I said I have read that paper. That doesn't mean I was thinking of that paper when I wrote this blog post. Pardon me for not having absolutely everything I have read in mind whenever I write a blog post. Anyway, this conversation is incredibly tedious. I'm done with this thread.
- pvg 17y agoYou noted it here, not in your post. Citing references and work your work is based on is certainly quite tedious. Sometimes doing the right thing is tedious. Doesn't make it any less right.
- Confusion 17y agoI'll respond at this level, although the point was only fleshed out in the subsequent discussion with swombat. Brooks was writing about a different thing. No Silver Bullet is about techniques for writing code. He specifically mentions programming languages, OOP, AI, graphical programming, etc. as examples of 'silver bullet candidates'. His arguments are based on, among other things, the complexity and changeability of the 'software entities', and the main point is that it's hard to get the code right. This all has very little to do with the methodology one uses to organise the writing of code and all the things that need to happen to allow the code to be written. It has become common for people to broaden the meaning of 'No silver bullet' and use it, appropriately or not, in various other contexts. However, in those circumstances, no tribute to Brooks is required if you, for instance, are explaining how there is no single method to make sure your toddler doesn't poke out your cat's eye. Your indignation over the referenceless unoriginality of this blogpost is really unsubstantiated.