Comment Re:Don't reinvent the Wheel (Score 1) 548
Hard to say. I would almost consider building new wheels to be part of the learning process for a new programmer. And I think there's value in it. Not just in the base problem solving skills that comes with re-inventing the wheel a few times, but in the perspectives that come along with it. If you don't re-invent the wheel at least a couple of times, then you will have no basis for forming a valid opinion on the best way to implement a wheel. Which, granted, may not sound like much, but it makes a difference in so many other areas. Besides, even when you're talking about literal wheels, those get re-invented all the time. If they weren't we would never have gotten innovations like the rubber tire, or the memory foam insert for armored cars. We would still have wooden wagon wheels, which, while useful, aren't especially interesting or versatile. I think, in the long run, the same is true for code. If someone wants to write a big new shopping cart product, based on what they think are the best practices for such an implementation... let them. If someone wants to think out a new way to write a blog, or send an email, that's fine too. If I were bringing young guys onto my team, I would honestly prefer to work with people who had that kind of experience, over people that didn't. Just my 3800 satoshi.