15 Jul 2025 #writing
Headlines and opening lines get you 80% of the results.
Because, based on Small Brevity, readers spend 17ms deciding if they keep reading or move on. So no matter how helpful your content is, nobody will click it if you write a poor headline.
Want to gain readers? Master your headlines with these ideas:
- Study your favorite YouTuber’s titles.
- Follow this 3-step formula.
- Use one of these emotions: fear, curiosity, desire.
- Follow title-driven creation: Headline first, content comes second.
- Rewrite the headlines of posts you read.
When you write online, you’re really in the business of writing headlines. Online writing is headline writing. No headline = no readers.
14 Jul 2025 #misc
I’ve only reread a few books. One of them, How to Win Friends and Influence People.
There may be newer books on communication, but this one has stood the test of time.
Here are two ideas from that book that changed how I approach conversations at work:
Never, ever, ever tell anyone they’re wrong.
That’s the worst way to start or end a conversation. And you won’t change the other person’s mind.
Instead of blaming anyone, find something else to blame or pretend to be clueless by saying you are the one who might be wrong. “Hey maybe I’m reading the wrong documentation. Here it says…“
Be careful with your “but.”
Often what comes next to a “but” is something negative.
People often remember the last words they hear, so they will only remember the negative part. Find ways to replace your “no, but.”
“That’s a good idea, but we will go over budget” is different from “That’s a good idea, and if we stay within budget, it’ll be perfect.”
13 Jul 2025 #coding
There’s good laziness and bad laziness.
One day, the VP of a company I was contracting with called me “lazy.” That was a compliment. You know the lazy that finds an easy way to solve a problem. The good lazy way.
But AI is turning us into bad lazy. The “I don’t want to think” kind of lazy. And I don’t want that type.
I’ve been experimenting with AI for my coding. When I sit down to code, I open Copilot on a browser to see what I can offload.
Recently, I’ve been migrating a legacy Visual Basic app and I’ve used Copilot to code faster by helping me with boring tasks.
The problem? Last week, I was stuck on a stupid problem: finding a value in a dictionary from a list of possible keys. Maybe I needed some rest, but I couldn’t think of a LINQ query for that. I was so tempted to wake up the genie in the bottle for that. It felt like the easy way out.
It’s so tempting to go directly to the AI and outsource our thinking.
Just the other day, I found a coder desperate because he couldn’t code without AI anymore. If we’re not careful enough, any one of us could become that coder.
12 Jul 2025 #coding
Flying is safe but… accidents happen.
When they happen, it’s all over the news. But the thousands upon thousands of safe flights don’t make it to the headlines.
The magic of the Internet took me to Admiral Cloudberg on Medium. Each post breaks down a rare accident, tracing the failed part or procedure that triggered the disaster.
After every accident, there’s an investigation
After binge-reading some of Admiral Cloudberg’s deconstructions, what struck me was the meticulous investigation after every accident.
A committee finds out exactly what happened and why. Their task is to find the root cause and the subsequent chain of events.
After finding the root cause, they:
- release bulletins to manufacturers
- update procedures and checklists
- add the accident scenario to simulators to train pilots
Their goal isn’t to blame the captain or anyone else, but to prevent the same mistakes in future flights.
Coding isn’t flying
As software engineers, often we hear or say,
- “Something went wrong. We don’t know why. It hasn’t happened since then.”
- “OK, let’s move on. If that happens again, we’ll take a deeper look.”
Imagine if we treated coding the same way:
Coding would be as safe and reliable as flying.
We must adopt the same commitment to safety protocols and procedures to never let the same mistake happen twice.
11 Jul 2025 #mondaylinks
Hey there.
Do you remember the first time you saw a computer? I do. And I originally wrote that story on my blog (2min). But this week, it went kind of “viral” when I reposted it on dev.to.
Anyway, here are 4 links I thought were worth sharing this week:
#1. AI can make us code faster. But writing code has never been the bottleneck (3min). It’s everything around writing that code in the first place.
#2. Curious about the backstory of some coding jargon? Here’s why we “call” functions (10min). Funny enough, we also say “invoke” a function and in Spanish, everyone associates “invoking” with ghosts.
#3. Instead of forcing devs to use AI, here are some ideas for managers to adopt AI (7min) in their teams.
#4. Also an introvert? Here’s a quick guide to networking (5min) for you. Not the networking type with cables and switches.
And in case you missed it, I wrote on my blog about the “I just went on vacation” effect (2min) and 4 lessons to start your first online business (3min).
(Bzzz…Radio voice) This email was brought to you by… Check my Gumroad store to access free and premium books and courses to level up your coding skills and grow your software engineering career.
See you next time,
Cesar
Want to receive an email with curated links like these? Get 4 more delivered straight to your inbox every Friday. Don’t miss out on next week’s links. Subscribe to my Friday Links here.