The other day on Hacker News, there was a good discussion of Avdi Grimm‘s talk on how to write Confident Code given at this year’s Ruby Midwest. He covers four areas: gather input, perform work, deliver results and handle failure. Here are links to the code example showing the initial, timid and final, confident code.
Explaining Why Moose is Awesome – The Direct Way
The Perl community knows that Moose is awesome as evidenced by the amount of talks at YAPC and the number of times it is mentioned on blog articles and discussion boards. However, to me, what often seems to get lost is why Moose is awesome and why it is relevant, especially to those outside the
Filtering Popular Mailing List Discussions with DateTime
Discovering Information via Better Browsing A great way to get into the thick of a new software project you want to learn or need to use is to check out popular mailing list discussions. Typically these will have detailed answers and multiple points of view. Recognizing this, Grokbase was designed to sort many things by
Why We Say “Performance Is A Feature”
Singing the Praises of the Unsung Hero The phrase “Performance is a Feature” has been growing in popularity. Lately, it’s importance for me is underlined by the fact the most common response I get from showing off my early-stage mailing list archive, Grokbase, is that “it’s fast.” I first heard this idea similarly phrased in
So You Want To Be A Coder
Self-Directed Job Enlargement This article is dedicated to my friends and colleagues working in non-coding technical roles that wish to make a transition or at least increase the amount of coding in their work. The Dilemma In software development teams above a certain size, there are often software engineers and systems engineers (including testing, support,
