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.
Nobody wants to read about the successful being successful. That’s a bad story.
James Altucher, one of the writers I’ve stolen from, shares not to be heroes, but vulnerable. Our struggles make our stories more relatable. He has a rule: if it doesn’t make you scared, don’t hit Publish. I probably read it in Choose Yourself Stories.
These days, a reader told me the book related so much with her, because she’s been going through similar situations. That made it a 5-star for her. And that’s the power of stories.
I was looking to know how the mind and emotions work.
But I found the best lesson for marriages and relationships.
It’s the XYZ approach from Emotional Intelligence by Daniel Goleman:
When sharing about an uncomfortable or annoying situation, instead of attacking the spouse, point out the situation.
And say something like, When you did X, it made me feel Y. I would have preferred Z.
Always make it about the situation, not the person.
And if it works for marriages, it works at the workplace too.
Read broadly or read about certain subjects or reread the same books?
I’ve struggled choosing a reading strategy.
Probably, for years, I read about anything that crossed my path.
But I realized I was only reading to chase quantity.
Then I switched to read books as needed.
These days, I started Emotional Intelligence by Daniel Goleman.
It teaches about empathic listening: not just hearing or repeating the last words you hear, but to listen and paraphrase showing the underlying emotion.
While reading about it, I remember that’s precisely one of the habits from 7 Habits of Highly Effective People.
That made me go back and read that chapter again.
Habit #5, if I remember correctly.
Which led me to remember about Anthony Metivier’s idea of building a fortress of books.
In of his YouTube videos, he recommends reading books that build on, expand, or contradict each other.
You’ll find the same concepts in different perspectives.
That’s a better reading strategy.
In case you’re curious, here are my books. Feel free to pick any strategy to read them.
