26 Feb 2025 #career
It took me two years to go from being just another developer in the room to sitting in meetings with the president.
It was at a past job. Sure, it was a small software company in my city. So small everyone knew who the president was, and he recognized everyone’s faces in the hallways. That was a point in my favor.
In my first years at that place, I was always behind: delivering my tasks late, staying after hours to keep up, and fixing bugs in my code.
And I wasn’t my team leader’s favorite team member.
It took me hours of studying and practice and hard work to prove I was more than a “problematic” developer.
But you don’t need to work hard, here are 10 ways to stand out at work:
- Deliver your work on time. Not early, and definitely not late.
- Document and automate your work. Don’t become a bottleneck. Don’t become a hero.
- Ask for the context behind your tasks. Always ask why. Why this? And why now?
- Get interested in the business side of your work. Understand how your work is helping the company make money.
- Speak up in meetings. Ask questions and give suggestions.
- Volunteer for the work nobody else wants to do. Make sure you can do it, or figure out how.
- Give 10 ideas to improve the company, the product, or the work around you.
- Be reachable during working hours, especially when working from home.
- Be easy to work with. A.k.a don’t be an ass*.
- Make your boss look good in front of their bosses.
- Make sure every task you get is solved. Either because you solve it or follow up with the right team or person to solve it.
Ok, those were 11 ways. I know I said there would be 10.
But if I had to pick only one from that list, I’d go with #9: Be easy to work with. Invest in your soft skills or human skills. That’s the easiest way to stand out. People will remember you, not by your work, but by your attitude.
Refactor your coding career with my free 7-day email course. In just 7 emails, you’ll get 10+ years of career lessons to avoid costly career mistakes.
25 Feb 2025 #writing
That was my favorite lesson from the book Writing for Developers.
We could always write more. I could have written more. I abandoned my blog for months back in 2023. I burned out and instead of doubling down on what I enjoyed, I abandoned it. Arrggg!
Content ideas and posts are everywhere.
Every bug fixed is a post. Every subject you’re learning is a post. Every time you struggle to figure something out is a post. Every job interview. Every performance review. Every promotion. Every book. Every mentorship session. They’re all posts.
The same way we read biographies to look for success clues, we could leave our own success clues in every post. We could build our own public time capsule.
From Just write by “Chasing Brains”:
Don’t over-engineer your site. Don’t even check the grammar. Just write 100 words and hit publish.
No matter if it’s a small bug fix or a career event, don’t create, but document.
If you’re interested in writing, read four lessons for a coder struggling to write and always write about what you do at work.
24 Feb 2025 #misc
Pierre started coding back in the 60s and still maintains a 30-year-old codebase.
Thanks to the magic of the Internet, and to one of my posts going viral, I’ve exchanged a couple of emails with Pierre. I don’t know him in real life, just on the Internet.
His story has captivated me from the beginning.
I know only about a few industry veterans, and even fewer who are still actively coding.
Another of those veterans is Leslie at one of my past jobs. He was a Distinguished Engineer, a title created just for him. He was in charge of reviewing every single one of our PRs. He didn’t miss a single comma.
After going through every boom and hype, here’s a veteran’s take on AI
Since the 60s, Pierre has gone through every boom and hype in this industry.
He witnessed the Y2K panic, the birth of Java, the rise of Agile, and probably more that I don’t remember now.
In one of our emails, I asked Pierre about his take on AI. Today, we only see headlines of CEOs claiming AI generates most of their code, along with headlines saying coders are doomed.
But, here’s what Pierre, with his wealth of experience, told me about AI (slightly edited for brevity):
I’m skeptical about AI. I just don’t see automatically generating code from typical imprecise specifications…Apparently we’ve run out of Internet on which to train AI. It is now feeding on its own hallucinations, like mad cows eating their own prion-riddled offal, or the inbred Hapsburg dynasty.
If Pierre, who has seen quite a lot, is skeptical, we shouldn’t be worried. I’m not.
Pierre reminded me of that joke/meme that we’re still safe because AI needs unambiguous and well-written requirements. As long as clients who don’t know what they want exist, we’re still in business.
I don’t think AI is taking our jobs anytime soon. Sure, we have to adapt. AI is changing the landscape. For sure, coding in 2034 will look different. We can’t ignore it.
AI is like using calculators in math classes. They make us faster, sure, but they can’t do the thinking for us.
23 Feb 2025 #misc
“What I cannot create, I do not understand.”
That’s one of the quotes on Richard Feynman’s blackboard at the time of his death. See the full picture here.
We truly have learned something when we can teach it. Feynman also said that we truly understand a subject when we can teach a beginner’s level lecture on that subject.
But that first quote reminded me of the famous mantra among programmers and coders: “don’t reinvent the wheel.”
Back in my first coding classes at university, one of my teachers taught us to write our own “Connection” class and use it wherever we go. We were learning how to connect to databases, probably using PHP or something.
Well, that wasn’t code reuse. That was reinventing the wheel and taking our reinvented wheel with us everywhere. We had ORMs in those days.
Reinventing the wheel is a bad idea. It only makes sense when learning to code or a new concept. Understand something, disassemble it, then recreate a simpler version. In fact, that’s the best way to learn coding.
The full quote should be “don’t reinvent the wheel. Only reinvent it to know how it works. Then use a real wheel.”
“You can only recreate what you understand” works in the other direction too. You only understand what you can recreate. You only understand the wheel you reinvent.
22 Feb 2025 #writing
It took me almost half a day to come up with yesterday’s subject.
That was after claiming, a few days ago, that writer’s block is not the real problem. Well, it took me more than usual to mark the calendar yesterday, even after looking for inspiration in past posts and half-baked ideas. I ended up writing about one of my recent frustrations: Hourly billing.
In case you’re like me yesterday, struggling to find what to write about, here’s a list of prompts to help you write today.
- Expand an old post.
- Dissect a book passage.
- Describe what’s around you.
- Turn a 10-idea list into a post.
- Write about your favorite quote.
- Summarize your favorite podcast episode.
- Write a letter to your past or future self.
- Expand one of your comments on social media into a post.
- Answer a question from Reddit, Quora, or any other forum.
- Set a timer and write about whatever comes to your mind.
- Open your browser history and compile the answers you found.
- Scroll through YouTube or any other feed and write a reaction post.
Even if you don’t have anything to write, don’t miss two days without practicing. Your writing muscle will atrophy. And here’s a list of tasks for the days you don’t feel like writing.