View Full Version : Don't use the Term "Why Reinvent the wheel"
barkermn01
11-13-2009, 12:02 PM
This is probably one of the most said things on forums along with Google IT
But the term
"Why Reinvent the wheel"
Is the most annoying Saying on the planet what good would it be if we all used the same thing and there was no competitors.
I found some thing out this morning goggle are reinventing the Web Protocol With a new system called SPDY
But by those that are narrow minded Yes there reinventing the Wheel but who gives a damn if a better system come out from it lets Reinvent till our hart is content
http://sites.google.com/a/chromium.org/dev/spdy/spdy-whitepaper
So Please don't have ago at some one when they put an idea forward to invent some thing that has been done for all you know they could do it 20 x Faster then the last,
So don't put people down, its like how many of you have built a login for but why its been done at least 500 times use some one else's so let users try,
Just try to remember this before you post "Why Reinvent the wheel" or some thing that means the same thing
tomws
11-13-2009, 02:15 PM
This is just silly. It's a perfectly valid statement when explaining to someone that they're wasting their time writing commodity code - time that could be better spent in development of the project rather than dawdling with trivialities.
Furthermore, your suggestion that this mysterious "someone" may actually come up with a better system in the end is a fairy tale. Most of the people who earn the "don't reinvent the wheel" statement are those who have absolutely no idea what they're doing anyway and are slogging away in Dreamweaver or following a tutorial from 1996. They are (largely) incapable of creating anything better than what's already freely available.
Notice that your positive example used Google; they are people who know what they're doing.
Notice that your negative example considers a login system, something that can be done by people who have no experience, but also can compromise an entire system if done poorly. (You probably should have picked something besides that.)
oesxyl
11-13-2009, 02:31 PM
Furthermore, your suggestion that this mysterious "someone" may actually come up with a better system in the end is a fairy tale. Most of the people who earn the "don't reinvent the wheel" statement are those who have absolutely no idea what they're doing anyway and are slogging away in Dreamweaver or following a tutorial from 1996. They are (largely) incapable of creating anything better than what's already freely available.
true but it's very simple to check this, ask them to explain, if they can answer you can learn something new else they will learn, :)
I don't care how stupid I look if I don't know something, I don't understand or I'm not agree, I simple ask. What could happend? :)
best regards
tomws
11-13-2009, 02:40 PM
true but it's very simple to check this, ask them to explain, if they can answer you can learn something new else they will learn, :)
I don't care how stupid I look if I don't know something, I don't understand or I'm not agree, I simple ask. What could happend? :)
I agree, but I wasn't considering posting methodologies - just the larger question of defending the "don't reinvent the wheel" retort for those who are incapable or uninterested. It wasn't (and isn't) my intent to claim that every newbie is incapable.
barkermn01
11-13-2009, 03:10 PM
I agree, but I wasn't considering posting methodologies - just the larger question of defending the "don't reinvent the wheel" retort for those who are incapable or uninterested. It wasn't (and isn't) my intent to claim that every newbie is incapable.
But how dose some one learn most of the things i have learnt are done by some one somewhere its the same with any programming langs,
Like now as a little experiment im trying to build a browser Engine Component for C# , IE like WebKit, or Mozzila, but its for fun see how much i know and see how much i can learn from trying to build it the best way to learn is to do some thing that needs what your learning so you learn how to implement it and how it can be used or exploited
oracleguy
11-13-2009, 03:28 PM
But how dose some one learn most of the things i have learnt are done by some one somewhere its the same with any programming langs,
Like now as a little experiment im trying to build a browser Engine Component for C# , IE like WebKit, or Mozzila, but its for fun see how much i know and see how much i can learn from trying to build it the best way to learn is to do some thing that needs what your learning so you learn how to implement it and how it can be used or exploited
That is different, if it is an exercise for fun to learn something. The whole don't reinvent the wheel thing mostly applies (imo) to anything that is going to see production environments or any actual non-educational development project.
But the reason why people rarely re-write that stuff, like in your example a browser component is that it takes valuable time away from building the actual application. I've never written a browser engine but I'm sure I could do it. Why? Because of all the other experience I have writing other types of applications.
But don't let that stop you, even if you don't finish it, you'll most likely learn something.
tomws
11-13-2009, 03:31 PM
Most people aren't building web sites or apps for educational purposes - they're building for production. For common production apps, those that require only commodity code, there's simply no reason to bother with reinventing the wheel. Using freely- and widely-available components reduces development time, increases development quality, and allows the developer to focus on more important aspects of the project.
When building for educational purposes, anything goes. "Waste time" on anything. But most of the simpler questions I've seen aren't asking for purely educational purposes - they're trying to achieve an end product. Using tried and tested components will get them a little closer to a decent quality site or app.
barkermn01
11-13-2009, 03:32 PM
That is different, if it is an exercise for fun to learn something. The whole don't reinvent the wheel thing mostly applies (imo) to anything that is going to see production environments or any actual non-educational development project.
well i understand that but,
Hey another browser system would be nice to get out there hell if i could get it to work fast i would put it open source for one ting it would be the first C# Componant
What im trying to say is its easy for you to build some thing then think well there might be others out there but mine might win,
Look at Cpanel, Plesk, WebCP there all the same thing but they all thrive
But then people could just plan Well i want to do this i know this exists but im want to make my own i have a friend who will not use any thing any one else has built
Apostropartheid
11-13-2009, 06:36 PM
Your analogy is flawed. All of these things add value to the market, through either competition or because they offer a better UI, a faster way of doing things, &c. I believe you are misinterpreting the phrase; take a look at Wikipedia (http://en.wikipedia.org/wiki/Reinventing_the_wheel) and look at where the phrase is valid for use and where it isn't.
vBulletin® v3.8.2, Copyright ©2000-2012, Jelsoft Enterprises Ltd.