Here’s my 10-idea list today—Well, I wrote 12:
Hey there.
This week, for the nth time, I had to bulk import records via an Excel file. It made me think, no matter how complex the code, it often boils down to reading and writing Excel files. Maybe we should build Excel add-ons or plugins instead of enterprise software. Thoughts?
Anyway, here are 4 links I thought were worth sharing this week:
#1. Worried about running out of work in the age of AI? (13min). We can learn from the auto industry. And no, they didn’t run out of work.
#2. I’m always amazed by how much you can accomplish with the command line. Here are some small programming tricks (6min), some of them for the CLI.
#3. Headlines saying coding is dead are exaggerated (10min). Coding isn’t going anywhere.
#4. For a bit of nostalgia, here’s a list of obsolete sounds. The modem dial-up…Anyone else?
And in case you missed it, I wrote on my blog about why you need an intention for a successful career (3min). That was a follow-up on the most painful mistake from my best job (3min).
(Bzzz…Radio voice) This email was brought to you by… 10 Surprisingly Simple Ideas That Changed My Life And Could Change Yours Too. If you’ve wondered how to actually change your life, this book shares 10 small daily ideas for big change.
See you next time.
Cesar
There’s nothing more intimidating than a blank page.
That was me today. I scrolled Hacker News, minifeed, and LinkedIn. I was looking for a subject to steal, but nothing inspired me.
Yesterday was easier. The most painful lesson from my best job sparked a discussion on dev.to. I just replied to that discussion.
Waiting for the muses, I tried a course called Write 4 a day. The first exercise was to write by hand for four minutes, whatever comes to mind, without judgment.
I had nothing to lose. So I tried it.
This exercise is like a 4-minute version of Julia Cameron’s Morning Pages, at anytime. It works: I’m writing these lines.
If you’re blocked, grab pen and write for 4 minutes. That’s all you need to unlock your words.
If after 4 minutes, you’re still blocked: try this trick or any of these prompts.
Last week, I wrote about the most painful lesson my best job taught me. Recently, I shared it on dev.to. The concept of a “plan” generated some discussion. Here I’m expanding on that.
It took me over 10 years to connect the dots.
For years, I didn’t have a career plan. I jumped from job to job feeling something was missing. OK, when I say “jump,” I mean fired, bored, and laid off. That was my most painful lesson. It cost me my health at the lowest point.
A “plan” sounds like a blueprint with every career scenario figured out in advance.
Nobody starts with a perfect plan. The early stages of our careers are about discovery, experimentation, and building skills while learning to navigate the corporate world.
Plans are hard to follow when layoffs are always around the corner and AI is changing job descriptions.
Instead of “plan,” think of an intention: a guiding principle that helps you decide whether to stay or move on.
There’s always luck, setbacks, and resets. It’s impossible to account for all of them in a “plan.” But an intention pushes you to act instead of waiting.
Here’s how an intention helps you in practice.
If your intention is money, a couple of years without raises or bonuses should push you to move. That’s not the job that will fill your pockets. Maybe a better choice would be joining a startup in early stages.
If your intention is growing a network, sitting in a cubicle isn’t the best idea. A better role might be DevRel, evangelist, or consultant, positions that takes you out of your cubicle.
Money was just an example. It could be gaining leadership experience, climbing the ladder, or learning opportunities.
Use your career intention as your flashlight. Otherwise, wait to leave only when bored, fired, or burned out. I wish someone had told me that when I started my coding career. It would have saved lots of headaches. Set your intention today.
If you liked these lessons, you’re going to like, Career Lessons From the Trenches, my free 7-day email course where I distill 10+ years of career lessons into 7 short emails–to help you navigate your coding career.
At first, I only wrote when I had something to share. That was once or twice a year.
Then, I challenged myself to write every other week. I was playing the SEO game. I packed headlines with keywords and wrote posts to land on Google’s first page.
Years later, to recover from burnout, I pushed myself to write daily.
A daily writing practice taught me to find ideas quickly, write away from my desk, and build a creative routine.
Apart from those three benefits, the #1 benefit is what I call the time capsule effect.
After +600 daily posts, I can jump to almost any date to see what I was learning, struggling, or sharing. A couple of years ago, I was learning how to outline a book and wondering when to call myself a writer.
Reading old posts and thinking “I’d do it better today” shows how much our skills have improved. That only happens with consistent practice.
Show up consistently, and you’ll build a time capsule that future-you will treasure.