This is how I feel most of my client proposal start:

* It's simple, I'd like to re-invent <the wheel>.

* All I want to do is use <rocketship engine> on <old typewriter>.

* I'm too cheap to hire a full-time < DBA, DevOps engineer, development team>. Can I pay you pennies?

* I'm poor and broke, can you do this for free?

* I'd like to <commit illegal act> and be <legal compliant standard>.

* I heard it was possible to <fly 30 people to the moon> using <Ford Model-T>. Please do this for us.

* I <sold my house>, but now <I'm locked out by the new owners>. Please help.

(c) Creative Tim. Worth to read pips!

How to land a programming job

1. ABC (Always Be Coding) - The more you code, the better you'll get.

2. Master at least one multi-paradigm language - Some good candidates are C#, C++, Java, PHP, Python, and Ruby.

3. Re-invent the wheel - You should implement the most common data structures in your language choice.

4. Solve word problems - Pick those that test your ability to implement recursive, pattern-matching, greedy, dynamic programming, and graph problems

5. Make coding easy - At least, make it look easy.

6. Be passionate - If you don't care, then nobody else will.

7. Don't make assumptions - Ask questions if you're not sure.

Y'all mother fuckers who use "don't re-invent the wheel" as a tactic to not grow new neurons, as if a ceiling's there — fuck out of my circle.

Those mother fuckers have never even created a single wheel - ever!

Well, ima re-invent any fucking wheel I want, when and where. How I learn is not your fucking busy.

What's even more annoying is that those telling me that shit are pretty much part of the paint on the wall and damn unemployable any where on this earth.

Some old tech: exists and functions just fine for 20+ years.

Some tech bro: Yeah we gotta throw this out the window and re-invent the freaking wheel.

1. Focus on learning; earning should come secondary
2. If it doesn't add anything to your resume, it's probably not worth picking up
3. Do not re-invent the wheel. Explore third parties and libraries thoroughly. Use them as much as you can.
4. If you stuck at a problem for more than 2-3 hours: post on stackoverflow
5. Plan, create deadlines, and focus as if an executive chose you.
Lazy = failure!

I find it very strange and telling when people tell me that a dev shouldn't "re-invent the wheel", "roll your own" or "leave it to the experts" while simultaneously promoting substandard own-rolled projects by other people that simply got popular.

Kind of a strange elitist double standard that encourages a bad mindset of "I can't be as good as them" and it's toxic.

If you wanna make your own framework / package / etc, just do it, it might even be better.

"Never re-invent the wheel, unless you’re sure the client needn’t go anywhere. " - Russell Bishop

Last couple of days as a dev at this job. I'm polishing up my documentation and making sure my reference guides are up-to-date. All the while knowing that my documentation, tools, and tests will likely never be touched. They'll sit on a share drive somewhere, like ancient tomes, while the next devs re-invent the wheel. So it goes.

To those of us who suffer from "Not invented here syndrome", I want you to ask yourself this question. If "reinventing the wheel is so valuable", would you re-implement the entire OSI stack?

No, as it would be a COMPLETE waste of time!!!

In all the layers below your application, several things related to how your code gets presented to your end-user are abstracted away from you. If you are able to accept that completely, why do you feel the need to re-implement every well-understood part of your particular project?

Cars, for example, are mostly made from standardized parts that solve well-understood problems. It then may have a few custom parts that may solve some novel problems to make it stand out from the rest.

Buildings are made completely from standardized parts, with regulations on how they are put together with some room for artistic flare.

If Software wants to be as equally respected as the rest, we need to get to that point.

DONT reinvent the wheel, just use battle-tested parts and just focus on what your project is trying to solve. It will be way more fruitful and fulfilling.

/rant

Oh, there are hundreds that I've started categorizing them. They outgrew the storage capacity of my head / brain. I've tried a lot of productivity tools to organize them, but in the end, all my project ideas just remain ideas scattered somewhere unless I see it action and go like, "Hey, I had that same idea. I wonder when they got the idea. Was it before or after I had it?" In the end, I just console myself saying that for me it was only an idea in my head when those people saw it through execution and has a working product. The next step for me is to get along with them and collaborate and make that idea better rather than re-invent the same wheel again according to my idea.

Nextcloud is the biggest example of an idea that came to me and remained in my head and is still on a todo list somewhere.