23 Jun 2025 #writing
#1. They offer a clear promise. “10 reasons” or “5 mistakes” are way better than “on writing” or “some thoughts on blogging.” It’s clear what to expect from the first two.
#2. They are easy to digest and skim. People don’t read online. They skim. A listicle with bolded bullet points or subheaders is easier to skim than text-heavy essays. People can jump in at any point after skimming. And even if they only read those subheaders, they will take away some value from a listicle.
#3. They follow a proven structure. Listicles are popular because they work. The 10 Commandments, The 48 Laws of Power, and 21 Lessons for the 21st Century are just three examples of listicles.
#4. They offer more interaction points. Every point invites comments and conversation. “I really like point #n…“
#5. They offer more repurposing opportunities. Listicle points with the most interaction make great standalone posts. See #4. That’s one tip to double our post count.
Best of all? If you already write 10 ideas a day, listicles practically write themselves.
22 Jun 2025 #productivity
For a long time, I was a note-taking freak.
I spent hours trying to find the perfect note-taking system. I tried a bullet journal, a simple A-4 sheet of paper folded twice, and an endless .txt file. I probably have an old comparison table of note-taking buried in my old computer.
Starting a second brain
Years later, probably scrolling on Hacker News, I found out about the Zettelkasten method.
It fascinated me so much that I read How to Take Smart Notes to learn more about the method and started my own “zettel.” But recently I realized that I barely revisit most of my notes. I’m not interested in the same topics anymore.
Simply writing 10 ideas
And after reading some of James Altucher’s books and recovering from burnout, I’ve changed my mind about productivity and to-do lists.
Instead of to-do lists and goals, I’ve started to write 10 ideas a day to become an idea machine. It has changed my note-taking habits too. Now, after every book, podcast, or course, I write down 10 key lessons. It forces me to recall the main ideas from the content I consume. I don’t need to write every single detail but rather remember the 10 points that resonate the most. That effort makes the learning stick.
I still write down the quotes I like the most from books I read. But I’ve stopped chasing second-brain systems and testing every new AI-powered app. I simply write 10 ideas. It’s simple and more useful than any system I’ve tried.
21 Jun 2025 #misc
In 2019, I started my first attempt at running a freelancing business.
I had started freelancing for a company I had just left. I thought I could do the same for other companies. My strategy for finding clients? Cold emailing any software agency I could find.
I even emailed every recruiter I found on open applications on LinkedIn. Those days, LinkedIn was flooded with “life-changing opportunities.” Sorry, I meant job listings.
I don’t remember how many emails I sent. But I remember getting just one reply. When I followed up, I only heard crickets.
Here are 15 ideas to reduce chances of getting ghosted when cold emailing clients or anyone else:
#1. Send 10 ideas for free. Don’t expect anything in return. This is James Altucher’s idea to become an idea machine.
#2. Don’t give your reader homework. “Fill out this application form to apply.”
#3. Make an offer simple to say yes. “For $x, I do XYZ.”
#4. Don’t make your reader look or feel bad. “Your YouTube video thumbnails suck, but I’m here to rescue you.” Good luck with that!
#5. Show real interest. “Hey, I’ve been following your content and liked your take on XYZ” or something like that.
#6. Start with a genuine compliment. Probably an idea I picked from “How to Win Friends and Influence People.”
#7. Sound like a real human being. Write using your own words.
#8. Don’t copy pitches from the Internet.
#9. Don’t use classical sales tactics. “Hurry up! Only X seats left. Limited offer.” Think you’re reaching out to help, not to close.
#10. Don’t just ask for something in exchange for nothing. “Let’s do a collaboration. You do something for me, but I don’t do anything for you.” Yeah, I’ve received DMs on LinkedIn in those lines.
#11. Interact with your reader’s content first on social media.
#12. Use a catchy subject line in your email.
#13. Spell your reader’s name or title correctly. You don’t know how many emails and DMs I’ve ignored simply because they started with “Hello, coach Cesar.” I don’t have a coaching business and I don’t have “coach” next to my name anywhere online. Somebody just use a template, got you!
#14. Tell them how you found their contact details. “I found your email on your LinkedIn profile…“
#15. Include your own socials or portfolio as proof you’re real. Nothing fancy, you could try adding them under your signature.
Last year, I found a job listing I liked. They were looking for people on-site in a different country, but it didn’t stop me. I reached out to the CEO sharing 10 ideas to improve their product landing page. My mistake? I misspelled the company name. Maybe that’s why I never got a reply.
20 Jun 2025 #mondaylinks
Hey,
Here are 4 links I thought were worth sharing this week:
#1. I don’t know how many times I’ve had to flip the conditions inside an if. Maybe not my trickiest bugs, but still… Anyway, here are 9 lessons from a coder’s trickiest bugs (8min).
#2. This coder doesn’t use AI and explains why (8min). One of his main concerns? Speed.
#3. Google Translate hasn’t killed translators and interpreters (6min). Maybe AI won’t kill coding either. At the end of the day, we as coders are translators too.
#4. It feels like coders will be AI’s first victims. But this might be the best time to learn software development (8min). Well, some time ago it was with textbooks, StackOverflow, forums, and instruction manuals.
I’ve been playing with Copilot recently. It’s already saved me hours of repetitive work. And in case you missed it, I’ve written about the tasks Copilot has helped me with here (3min) and here (2min).
(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.
19 Jun 2025 #coding
This week, I’ve been running a coding experiment.
Every time I sit to code, I open Copilot (on a browser, not inside my IDE) and look for tasks to delegate.
Yesterday, while migrating a legacy Visual Basic application, I found myself doing some mundane and repetitive work. So I hired Copilot as my junior coder. And here are the tasks it helped me with:
#1. Populate an enum.
I had a large While loop full of If statements on the VB side.
It used magic strings for the comparisons. I gave the original VB code and asked Copilot to populate an existing C# enum with the missing magic strings.
A method with dozens of parameters isn’t that weird in a legacy app.
To make it easier to port, I gave Copilot the signature of a method and a code block that invoked it, and asked it to use comments to document each parameter name.
Later, I found out VB has named parameters. Arrggg! Anyway, that wasn’t code I was planning to commit. It was just to make it easier to read and port to C#.
#3. Avoid jumping between files.
Why create constants when we could use magic strings, right? Another common mistake on legacy apps.
In a unit test, in the Arrange part, I needed to generate identical objects, except for the values for a pair of properties.
The problem? I needed to look at three VB files to come up with the right combination of values for each object. So I gave Copilot the three code blocks and asked it to generate a 3-column table with the values I needed. No more jumping between files.
#4. Convert stored procedures into Entity Framework Core queries.
I’m not going to discuss which one is better. Stored procedures or ORMs.
But I found myself migrating stored procedures with fairly simple queries to LINQ-like queries with Entity Framework. So I gave Copilot my entity classes and asked to generate the equivalent queries.
This might not work for large and complex queries inside stored procedures.
#5. Review a patch looking for typos.
Before opening PRs, I asked Copilot to look for typos and suggest more descriptive class, method, and variable names.
Naming is hard and it always generates a lot of back and forth in code reviews. To avoid long discussions, I gave Copilot a git diff of my changes and asked it to be my code reviewer.
I’ve found Copilot shines at text-heavy processing tasks and filling the blanks of well-defined tasks. I’ve already tried these five tasks. But it’s not great at vague instructions like “migrate this to C#” or “refactor this code block.” With clear instructions, it’s the best intern for tedious tasks.