Pinned — 28 Oct 2025 #codingStreet-Smart Coding: 30 Ways to Get Better at Coding Without Losing Your Mind
I spent five years in college learning to code.
A stupid dissertation delayed my graduation. But that’s another story.
Most of my five-year program didn’t prepare me for real-world coding. My real coding journey began at my first job, with one Google search: “how to get good at coding.”
I found a lot of conflicting advice:
“Use comments”
“Don’t use comments”
“Do this”
“Don’t do that”
Arrggg!
It took years of trial and error to learn what worked.
I had to survive on-call shifts, talk to stakeholders, and say “no” politely. More importantly, I had to learn that coding takes more than just syntax.
That’s why I wrote Street-Smart Coding— a roadmap of 30 lessons I wish I had when I started. For every dev who’s ever typed “how to get better at coding” into Google or ChatGPT. (Back in my days, I didn’t have ChatGPT… Wait, I sound like a nostalgic grandpa…)
Preview of the first ~12 pages
Inside “Street-Smart Coding”
This isn’t a textbook. It’s a battle-tested guide for your journey from junior/mid-level to senior.
Some lessons are conventional.
Others were learned the hard way.
And a few are weird.
One lesson comes from a TV show. Nope, not Mr. Robot or Silicon Valley. That’s on Chapter #29. It will teach you about problem-solving.
You’ll learn how to:
Google like a pro
Debug without banging your head against a wall
Communicate clearly with non-tech folks
…and 27 more lessons I learned over ten years of mistakes.
The right time to do something is when you don’t feel like doing it.
If you don’t feel like going to the gym, that’s when you should go.
Don’t feel like getting out of bed? That’s when you should count up to 3 and get up.
Don’t feel like writing? That’s when you should do it.
Today I didn’t feel like writing my daily post.
To spice things up, I challenged myself to write this draft without looking at the text.
I opened LibreOffice Writer, set the font to white, and wrote blindly.
Here are 4 links I thought were worth sharing this week:
#1.Coding sucks (9min) It’s not like building a house, but like jumping into a ship, nobody knows where it goes…And no, AI didn’t take our jobs. It was something else.
(Bzzz…Radio voice) This email was brought to you by… Street-Smart Coding, 30 lessons to help you code like a pro. From Googling to clear communication, it shares the lessons to help you stand out in the age of AI.
#1. Buy a domain and choose a professional handle. And no, a hacker-like handle isn’t cool.
#2. Start that blog. Seriously! Write anywhere. You’re going to like it.
#3. Open a brokerage account and start investing. Go with a broad market index fund and don’t worry about ups and downs.
#4. Take care of your body. Go to bed early. Exercise. Eat the right food, in the right amount.
#5. Don’t try to fit in. If you feel alone, there’s nothing wrong with you. Build a place where you fit in.
#6. Don’t force people into your life. That applies to friends and relationships.
#7. Ask for help. Figuring out things on your own is satisfying. But with help, you’ll get results faster.
#8. You can’t fix the world or people around you. And that’s OK. Often, they don’t want to be saved.
#9. Be present for your family. And being around and providing for them isn’t enough.
#10. If something feels off about work and life, you’re most likely right.Come up with your plan or work on somebody else’s plan—you’re not going to like it.
Search for “Zettelkasten” and you’ll drown in endless breakdowns of note types and apps.
But the Zettelkasten method isn’t complicated.
How to Make Notes and Write by Dan Allosso shows a simple way to adopt it.
Here are five lessons I’ve learned from reading it:
#1. Avoid the mere-exposure effect.
Seeing a concept frequently doesn’t mean you understand it.
You truly understand something when you write about it.
Writing makes you think.
#2. Read with a project in mind.
Don’t extract everything from a book in one pass.
Record what’s useful for your current project.
You can always reread.
#3. Focus on the process, not the tools.
“What’s the best plugin for Obsidian?”“When should I use this note type?”
Arrggg!
Forget about tweaking fancy tools.
Niklas Luhmann, the Zettelkasten godfather, didn’t even have a computer.
He only used pen and paper—and a typewriter.