The introduction to Head First Design Patterns exhorts us not to recreate the wheel:

You're not exclusive. At some assumption minute, somewhere in the world person struggles with the European software system design problems you have. You know you don't want to recreate the wheel (or worsened, a flat deplete), so you look to Design Patterns -- the lessons conditioned by those who've featured the European problems. With Design Patterns, you get to take point of the best practices and experience of others, so that you can eat your time on...something else. Something more than difficult. Something more than structure. Something more than fun.

Avoiding the reinvention of the known wheel is a standard bit of acceptable wisdom in software system development circles. There's certainly women's liberationist here, but I think it's a bit serious if condemned too literally -- if you categorically deny no attempts to figure out a question with encrypt once some extant edifice is in place.

I'm not so sure. I think reinventing the wheel, if finished properly, can be functional. For mental representation, James Cervus elaphus reinvented the wheel. And he likeable it:

I reinvented the wheel last period of time. I Sat down and deliberately coded something that I knew already existed, and had probably also been finished by galore galore otherwise group. In conventional programing damage, I worthless my time. But it was worthy, and what's more than I would suggest almost some intellectual software engineer do precisely the European thing.

But who's James Cervus elaphus? Just other software engineer. If that doesn't carry decent weight for you, how does it sound reaching from Charles G. E. Moore, the person of FORTH?

A second consequence was even more than dissident: "Do it yourself!"

The conventional approach, unenforced to a lesser or small point, is that you shall use a standard package. I say that you should write your personal subroutines.

Before you can write your personal subroutines, you have to know how. This instrumentation, to be virtual, that you have spoken it before; which makes it effortful to get started. But give it a try. Aft activity the European package a large integer arithmetic operation on as galore computers and languages, you'll be beautiful good at it.

Moore followed this to an unbelievable point. Throughout the 70's, as he unenforced Forth River on 18 dissimilar CPUs, he invariably wrote for each his personal program, his personal record and terminal drivers, even his personal increase and divide subroutines (on machines that mandatory them, as galore did). When here were manufacturer-supplied routines for these functions, he read them for ideas, but never old them exact. By intended exactly how Forth River would use these resources, by omitting maulers and generalities, and by sheer acquirement and experience (he speculated that least multiply/divide subroutines were spoken by person United Nations agency had never finished one before and never would again), his versions were invariably small and faster, usually significantly so.

Moreover, he was never slaked with his personal solutions to problems. Revisiting a computing machine or an exercise aft a small indefinite quantity eld, he often re-wrote key encrypt routines. He never re-used his personal encrypt without re-examining it for possibility improvements. This early became a source of hindrance to Rather, United Nations agency, as the shopping arm of FORTH, INC., often bid jobs on the assumption that since G. E. Moore had just finished a like project this one would be easy -- lone to watch helplessly as he moulding up no his past encrypt and started over.

And point there's Bob Lee, United Nations agency leads the core edifice development on Android.

Depending on the discourse, you can almost always exchange "Wherefore recreate the wheel?" with "Gratify don't contend with me," or "Gratify don't make me read something new." Either way, the hostile doesn't have a real sum-up against creating from raw materials something newer and better, but they also don't want to admit their edematous motivations for hard to stop you.

More seeds, more than blooms, I say. Don't build houses on kitchen sinks. Recreate away. Most of our electric current engineering sucks, and even if it didn't, United Nations agency am I to try and stop you?

Indeed. If thing, "Don't Recreate The Wheel" should be old as a call to instrumentality for deeply educating yourself about no the extant solutions -- not as a bludgeoning tool to hollow those United Nations agency legitimately want to build something better or change on what's already out here. In my experience, sadly, it's little more than the former than the former.

So, no, you shouldn't recreate the wheel. Unless you plan on encyclopaedism more than about wheels, that is.

The introduction to Head First Design Patterns exhorts us not to recreate the wheel:

You're not exclusive. At some assumption minute, somewhere in the world person struggles with the European software system design problems you have. You know you don't want to recreate the wheel (or worsened, a flat deplete), so you look to Design Patterns -- the lessons conditioned by those who've featured the European problems. With Design Patterns, you get to take point of the best practices and experience of others, so that you can eat your time on...something else. Something more than difficult. Something more than structure. Something more than fun.

Avoiding the reinvention of the known wheel is a standard bit of acceptable wisdom in software system development circles. There's certainly women's liberationist here, but I think it's a bit serious if condemned too literally -- if you categorically deny no attempts to figure out a question with encrypt once some extant edifice is in place.

I'm not so sure. I think reinventing the wheel, if finished properly, can be functional. For mental representation, James Cervus elaphus reinvented the wheel. And he likeable it:

I reinvented the wheel last period of time. I Sat down and deliberately coded something that I knew already existed, and had probably also been finished by galore galore otherwise group. In conventional programing damage, I worthless my time. But it was worthy, and what's more than I would suggest almost some intellectual software engineer do precisely the European thing.

But who's James Cervus elaphus? Just other software engineer. If that doesn't carry decent weight for you, how does it sound reaching from Charles G. E. Moore, the person of FORTH?

A second consequence was even more than dissident: "Do it yourself!"

The conventional approach, unenforced to a lesser or small point, is that you shall use a standard package. I say that you should write your personal subroutines.

Before you can write your personal subroutines, you have to know how. This instrumentation, to be virtual, that you have spoken it before; which makes it effortful to get started. But give it a try. Aft activity the European package a large integer arithmetic operation on as galore computers and languages, you'll be beautiful good at it.

Moore followed this to an unbelievable point. Throughout the 70's, as he unenforced Forth River on 18 dissimilar CPUs, he invariably wrote for each his personal program, his personal record and terminal drivers, even his personal increase and divide subroutines (on machines that mandatory them, as galore did). When here were manufacturer-supplied routines for these functions, he read them for ideas, but never old them exact. By intended exactly how Forth River would use these resources, by omitting maulers and generalities, and by sheer acquirement and experience (he speculated that least multiply/divide subroutines were spoken by person United Nations agency had never finished one before and never would again), his versions were invariably small and faster, usually significantly so.

Moreover, he was never slaked with his personal solutions to problems. Revisiting a computing machine or an exercise aft a small indefinite quantity eld, he often re-wrote key encrypt routines. He never re-used his personal encrypt without re-examining it for possibility improvements. This early became a source of hindrance to Rather, United Nations agency, as the shopping arm of FORTH, INC., often bid jobs on the assumption that since G. E. Moore had just finished a like project this one would be easy -- lone to watch helplessly as he moulding up no his past encrypt and started over.

And point there's Bob Lee, United Nations agency leads the core edifice development on Android.

Depending on the discourse, you can almost always exchange "Wherefore recreate the wheel?" with "Gratify don't contend with me," or "Gratify don't make me read something new." Either way, the hostile doesn't have a real sum-up against creating from raw materials something newer and better, but they also don't want to admit their edematous motivations for hard to stop you.

More seeds, more than blooms, I say. Don't build houses on kitchen sinks. Recreate away. Most of our electric current engineering sucks, and even if it didn't, United Nations agency am I to try and stop you?

Indeed. If thing, "Don't Recreate The Wheel" should be old as a call to instrumentality for deeply educating yourself about no the extant solutions -- not as a bludgeoning tool to hollow those United Nations agency legitimately want to build something better or change on what's already out here. In my experience, sadly, it's little more than the former than the former.

So, no, you shouldn't recreate the wheel. Unless you plan on encyclopaedism more than about wheels, that is.

Vivek Kundra, Obama's newly-appointed CIO, is the man in charge of processing and deploying IT to change politics trading operations. He's also a fan of creating from raw materials politics intranets founded around Google web apps.

In his time as Federal government D.C.'s CTO, Kundra old Google's web apps to not lone develop intranets, but also content production systems. And accordant to cnet, he believes in a platform-independent, open source performing of software system development. Kundra is also a big advocate of picture and the offer of aggregation online, serving to shape the U.S. Government's updated school policy.

Chalk up other net tolerance win for the good guys. And let's not forget, the CTO is still to be proclaimed. [cnet via Electronista]