The best way to learn
👋 This page was last updated ~12 years ago. Just so you know.
“The best way to learn is to just go out and make stuff, collaborate with people who are better than you at different things, and experiment.”
“That’s what I’ve found, at least. Just be around people who are awesome and learn off them. Trade ideas around and try stuff.”
“Everything I do, I’ve learned from friends, collaborators, people I look up to, and personal experiments. Just going out and trying stuff.”
— Noel Berry, aka @NoelFB
Here's another article just for you:
A dynamic linker murder mystery
I write a ton of articles about rust. And in those articles, the main focus is about writing Rust code that compiles. Once it compiles, well, we’re basically in the clear! Especially if it compiles to a single executable, that’s made up entirely of Rust code.
That works great for short tutorials, or one-off explorations.
Unfortunately, “in the real world”, our code often has to share the stage with other code. And Rust is great at that. Compiling Go code to a static library, for example, is relatively finnicky. It insists on being built with GCC (and no other compiler), and linked with GNU ld (and no other linker).