Paul Gauguin Couldn’t Paint, But He Still Became A Great Painter

You must read this if you have read Joel’s article on the same topic. We averages deserve a living too.

Monadically Speaking: Adventures in Programming Language Theory

Today, I discovered a blog post, “Soloists vs. The Choir,” by Andy Leonard on a blog entry by Joel Spolsky, founder of Fog Creek Software, on the correlation (or lack of, rather) between spent time and resulting quality of programming. Leonard wrote:

Is there really that great a difference between good and great programmers?

Joel cites some impressive statistics gleaned from Yale Professor Stanley Eisenstat, who teaches a software development class. The scatter plot says it all.

As Joel notes, “There’s just nothing to see here, and that’s the point. The quality of the work and the amount of time spent are simply uncorrelated.”

While that may be so, companies do not determine what people want to do; people do. This kind of reasoning leads to the conclusion that only star programmers should program. By that kind of reasoning, only great writers should write, only great translators should translate, and…

View original post 2,558 more words

Standard

Incomplete Programming History w/ Related Quotations

Awesome collection of quotes

Lewis' Random Maybe Computer Stuff

Well, I wrote this today (when I should’ve been writing a real paper)… Why not put it here! It has some great quotes from programming language developers, and my descriptions of languages in my own words. I mainly did it for the programming class I am teaching (and because I like reviewing programmer quotes). I don’t claim this to be exhaustive, but it should be accurate although I am sure some of my opinions of various language couldn’t help but come through…

“There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies.” — C. A. R. Hoare

FORTRAN, John Backus and IBM team (1957)

FORTRAN is the oldest language still in use today. It was designed for high performance computing for…

View original post 5,587 more words

Standard

Print lines between two patterns , the awk way …

Beautiful display of AWK craftsmanship. Dont miss the solutions in the comments section.

NixTip

Note: My awk guide.

Example input file:

The standard way ..

Output:

Self-explained indented code:

The first optimization is to get rid of the print , in awk when a condition is true print is the default action , so when the flag is true the line is going to be echoed.

To delete de NEXT statement , in order o prevent printing the TAG line,  we need to activate the flag after the “OUTPUT” pattern discovery and after the flag evaluation.

A slight variation of the program flow and we’re done:

PD: What if we only want to print the lines enclosed between the OUTPUT && END tags ? check this

View original post

Standard