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.
#2. What’s worse than spending all day in meetings? Well, here are 12 nightmares every coder faces. Be careful it any of them makes you wake up.
#3. You spent two days preparing for your next interview, just to find out your interviewer, who never asks your name, wants to test your IQ and have your brain scanned to see if you’re smart to work with him.
#4.Do you have a minute? When your boss texts you that, you don’t know if it’s going to be a new priority or your turn to leave.
Booo! Happy Halloween.
Don’t worry Street-Smart Coding won’t scare you at all. That’s the roadmap I wish I had on my journey to become senior
One year ago, it felt like a distant goal. Today, over 90 devs are coding smarter. You’ve probably started getting these emails after grabbing your copy.
If you’ve read the book, I’d appreciate a quick review on Gumroad, Amazon, or Goodreads. That’d help more devs code smartly.
Maybe it’s time to start thinking about a new edition.
Announcement: After 1 year, Street-Smart Coding became a 4-part series.
I’m working on the third book. A short and actionable guide to help you leverage AI without becoming dependent on it. I’m calling it: Street-Smart Coding in the Age of AI. You can preorder your copy starting at just $1.
As usual, here are 4 links I thought were worth sharing this week:
(Bzzz…Radio voice) This email was brought to you by… Preorder your copy of Street-Smart Coding in the Age of AI. A short and actionable guide to leverage AI without losing your skills.
It isn’t a New York Times best-seller… yet?
It doesn’t pay my rent… yet?
It’s just another tiny piece of content filling the Internet ether.
But it’s a big small win for me.
That’s why I broke my weekly routine and went out to eat a slice of pizza or two.
To make it more symbolic, I paid for it with the book sales.
By the way, I ate some salad and protein before, to control the glucose spikes.
Even I took some pictures to remember it.
Some say, happiness is about the journey, not the destination.
Just make sure to celebrate those small moments along it.
I’m doing nothing the rest of the day off to keep celebrating.
If you’re curious, you’ll find Street-Smart Coding and the rest of my books here.
One year ago, writing a book felt like a distant goal.
Today, Street-Smart Coding turns 1 year old.
It’s the book I wish I had when starting out as a coder.
A roadmap with 30 lessons to build skills that last a career.
From the most conventional to the most unexpected.
I wrote it for my younger self Googling “how to get better at coding.”
Street-Smart Coding became a book series
After one year, Street-Smart Coding became the second book in a 4-part series.
I’d rewrite Chapter 1 to make it timeless. The principle is there: find your own answers. But I framed it using Google, which is not as relevant in these days of AI as it was years ago.
Unless you write a New York Times best-seller, you won’t live off a single book.
But if someone outside your circle buys your books, it’s already a success. Street-Smart Coding is a huge success.
In the last year, it’s sold 92 ebook copies via Gumroad, and 9 Kindle and 2 paperback copies via Amazon.
It passed 100 copies in its first year.
Apart from sales, it earned me my first hater.
Someone called me “b*tch” for promoting it.
And it helped me define my category of one.
Someone called me the “Street-Smart Coding guy” in a comment.
Since then, I’ve made it my bio everywhere online.
Apart from my daily blog, Street-Smart Coding is the project I’m the most proud of.
One year later, I’d still recommend it to my younger self. If you want to code smarter and build real-world skills that last a career, grab your copy of Street-Smart Coding today.
Commenting might be the ultimate growth hack on social media for some.
For me, it feels unproductive and time-consuming. I still comment from time to time. And to avoid make it a waste of time, here are 5 random comments I shared on social media in recent weeks:
#0. Change is part of the job description of software engineering. Decades ago, we were punching cards. Years ago, we were writing every single line of code by hand. Well, not anymore. Change is probably the most exciting and challenging part of being a coder. Ride all the waves that come along.
#1. Clean Code isn’t the book everyone should read. The best in the Clean series and the book everyone should read is: Clean Coder. Clean Code turned me into a maniac of lines of code, a police offer looking for infractions. But nobody told me how to actually become a professional. The closest book was: Clean Coder.
#2. With AI, languages and syntax isn’t the edge anymore. Well, the real edge has always been ownership, communication, and collaboration.
#3. The real job is to solve problems, not to write code. Every time I share that end users don’t care about code, I get virtual stones. But interestingly enough, I’ve never heard a single client or end user asking to see the source code of the tools we build for them.
#4. It’s completely fine if you don’t know about everything. Full-stack? Full-stack who understands DevOps? Full-stack who understands agentic coding and is able to define the product they’re building.
Truth is, both generalists and specialists are needed. And we can’t pretend everyone should thrive on every mode. From Range by David Epstein: The world needs both frogs (deep-focused specialists) and birds (“above the trees” generalists who can see the bigger picture).
If any of these ideas resonates, you’re going to like Street-Smart Coding Manifesto. A case against syntax obsession to stand out as a coder.
