Reinvent the Wheel? Why It's the Best Advice You're Ignoring - ListenHub

Reinvent the Wheel? Why It's the Best Advice You're Ignoring

ListenHub

0

May 27

From

endler

Reinventing the wheel fosters curiosity, learning, and deeper understanding of existing tools and technologies, leading to innovation and problem-solving.

Podcast Snippets: Reinventing the Wheel

Intro Hook:

Tired of hearing "don't reinvent the wheel"? What if that's the worst advice you could follow?

The Problem with "Don't Reinvent the Wheel":

Discourages curiosity and exploration.
We have much better wheels today than the originals. Reinvention is crucial for progress.
Think of "wheel" as any tool, protocol, or technology.

Why Reinventing is Learning:

Richard Feynman: "What I cannot create, I do not understand."
Implement a toy version to really understand something. It doesn't matter if it's perfect.
Demystifies complex concepts like protocols, cryptography, and web servers.

The Rabbit Hole Effect:

Fundamental things (strings, paths) are often taken for granted. Implement them yourself!
You'll learn:
- Infinite complexity in everyday things.
- Humbling to build something useful to others.
- Abstractions are human-made, not perfect. You can make different tradeoffs.
Everything is a tradeoff: correctness, simplicity, scalability, performance. No solution is perfect for everyone.
Level up as an engineer by finishing what you start.

Reasons TO Reinvent:

Build a better wheel (for some definition of better).
Learn how wheels are made.
Teach others about wheels.
Learn about the inventors of wheels.
Be able to change or fix wheels when they break.
Learn the tools needed to make wheels.
Learn a tiny slice of a larger system.
Help someone in need of a special wheel (wheelchair?).
Maybe your "wheel" becomes a skateboard, a potter's wheel, or something completely different!

Reuse vs. Reinvent: The Balance

Study existing work and reuse where appropriate.
Don't reinvent out of ignorance, but don't be afraid to test your knowledge.
Run small experiments and build prototypes.
Solve your own problems, start small, keep it simple, iterate.

Key Takeaway:

*Reinvent for insight. Reuse for impact.

Outline

Reinventing the wheel fosters curiosity, learning, and deeper understanding of existing tools and technologies, leading to innovation and problem-solving.

Podcast Snippets: Reinventing the Wheel

Intro Hook:

Tired of hearing "don't reinvent the wheel"? What if that's the worst advice you could follow?

The Problem with "Don't Reinvent the Wheel":

Discourages curiosity and exploration.
We have much better wheels today than the originals. Reinvention is crucial for progress.
Think of "wheel" as any tool, protocol, or technology.

Why Reinventing is Learning:

Richard Feynman: "What I cannot create, I do not understand."
Implement a toy version to really understand something. It doesn't matter if it's perfect.
Demystifies complex concepts like protocols, cryptography, and web servers.

The Rabbit Hole Effect:

Fundamental things (strings, paths) are often taken for granted. Implement them yourself!
You'll learn:
- Infinite complexity in everyday things.
- Humbling to build something useful to others.
- Abstractions are human-made, not perfect. You can make different tradeoffs.
Everything is a tradeoff: correctness, simplicity, scalability, performance. No solution is perfect for everyone.
Level up as an engineer by finishing what you start.

Reasons TO Reinvent:

Build a better wheel (for some definition of better).
Learn how wheels are made.
Teach others about wheels.
Learn about the inventors of wheels.
Be able to change or fix wheels when they break.
Learn the tools needed to make wheels.
Learn a tiny slice of a larger system.
Help someone in need of a special wheel (wheelchair?).
Maybe your "wheel" becomes a skateboard, a potter's wheel, or something completely different!

Reuse vs. Reinvent: The Balance

Study existing work and reuse where appropriate.
Don't reinvent out of ignorance, but don't be afraid to test your knowledge.
Run small experiments and build prototypes.
Solve your own problems, start small, keep it simple, iterate.

Key Takeaway:

*Reinvent for insight. Reuse for impact.

Script

Mars: So, I've always heard, Don't reinvent the wheel. It kinda feels like a creativity killjoy, right? Like, just shut up and use what's already there. Is that really the best advice, or is there more to it?

Mia: Honestly? It's probably some of the worst advice out there! It basically tells you to just accept things as they are, never question, never experiment. And for anyone who likes to tinker, that’s a total drag.

Mars: Okay, so you're saying building something from scratch – even something that already exists – can actually *help* you learn? Isn't that just a huge time suck, though? Why not just grab a library or package and be done with it?

Mia: Valid point! But think about it this way. There's this saying, What I cannot create, I do not understand. Say you wanna really get how web servers work. You *could* copy-paste some existing framework code, or you could write a super-basic HTTP server yourself. You'll run into all sorts of little problems – socket handling, headers, all that jazz. But by the end, you'll have demystified the whole thing.

Mars: Wait, so you're saying that by actually building a bare-bones server, I learn *more* than just reading the documentation?

Mia: Exactly! It's like cooking from scratch versus microwaving a frozen dinner. You might survive on the frozen stuff, but you'll never master the art of cooking unless you actually get your hands dirty.

Mars: Okay, I get it. But isn't there a danger of just going down these crazy rabbit holes? Like, next thing you know, you're writing your own string library at 3 a.m. instead of watching Netflix.

Mia: Haha, guilty! But those rabbit holes can be amazing. Strings, for example. They seem so simple, until you try to implement your own. Suddenly you're thinking about encoding, memory layout, performance... You realize that abstractions are just... compromises. You might want a wheel for a car, but someone else needs a skateboard wheel. No one-size-fits-all.

Mars: So every tool or protocol is just someone else's trade-off? And by reinventing, you learn which trade-off makes sense for *you*.

Mia: Bingo! You learn where you can sacrifice simplicity for speed, or vice versa. And if that wheel breaks – or if you need a specialized wheel – you'll actually know how to fix it. Reuse when it makes sense, but reinvent to truly understand and innovate.

Mars: Okay, devil's advocate time. What if I reinvent something and it completely bombs? Like, I build a better wheel and it's actually worse – slower, buggier...

Mia: That's part of the game! Small experiments, prototypes, are your best friends. You learn just as much from failure as you do from success. And who knows? Maybe your terrible wheel will spark an idea for a third version that's actually amazing.

Mars: So the moral of the story is: don't reinvent out of pure ignorance, but don't be afraid to test your limits. Build that toy version, embrace the mess, and then decide if you want to keep it or switch to the professionally-made version.

Mia: Couldn't have said it better myself. Reinvent for insight; reuse for impact. That way you're never just blindly copying – you actually understand your tools inside and out.

Mars: I love that. Alright, I'm off to write my own tiny crypto protocol. Wish me luck!

Mia: Haha, good luck! And hey, if you accidentally reinvent blockchain, remember to invite me to your TED Talk.

Mars: Deal! That's all for today's take on reinventing the wheel. See you next time!