Linked by RandomGuy on Wed 10th Jun 2009 20:00 UTC
General Development This series is aimed at programming language aficionados. There's a lot of very abstract writing about programming languages and a lot of simple minded "language X sux!" style blog posts by people who know next to nothing about programming. What I feel is sorely missing is a kind of article that deliberately sacrifices the last 10% of precision that make the theoretical articles dry and long winded but still makes a point and discusses the various trade offs involved. This series is meant to fill that void and hopefully start a lot of discussions that are more enlightening than the articles themselves. I will point out some parallels in different parts of computing that I haven't seen mentioned as well as analyze some well known rules of thumb and link to interesting blogs and articles.
Permalink for comment 367793
To read all comments associated with this story, please click here.
Benefit of the doubt
by RandomGuy on Wed 10th Jun 2009 21:32 UTC
RandomGuy
Member since:
2006-07-30

Sorry if you hate my article.

Like I stated in the introduction I deliberately sacrificed some precision to make it shorter.
I also wanted to combine ideas in new and (at least to me) interesting ways. These two factors make my writing very vulnerable to criticism. I expected that.

I didn't set out to write the most perfect explanation of big O notation or templates. That was never the point of this article. I wanted to give the noob reader a rough idea of the concepts that's short enough to be skipped easily by the pros. Everybody knows how to use Google and Wikipedia.

Well, if everybody completely missed the point of this article I guess my writing does suck. ;)
All I'm asking is this:
Don't think I'm an idiot because I didn't write a 10 page article that reiterates a simple idea for the 10billionth time. The facts are obvious and you don't get criticized. It's easy to write this kind of article. Easy and pointless.

Give me the benefit of the doubt.
I spent countless hours thinking about and rephrasing each and every part of this article.

Reply Score: 3