A Blog Has Been Better for My Career Than a Portfolio

I don’t have a coding portfolio.

By portfolio, I mean a webpage showcasing my best projects. My GitHub account is the closest thing to a coding portfolio. But it hasn’t helped me land jobs.

My blog has helped me more. Here’s how:

1. A content collaboration

Some time ago, the next day after interviewing for a small local company, I got a phone call.

They wanted me to start a company blog for them. The interviewer read some of my blog posts. I had a link to it on my CV. He wanted me to write something similar for them.

I wrote five blog posts for them with interview preparation material. Even though I decided not to continue the interview process, I declared it a win. Also, I made some lunch money with them.

2. A smoother hiring process

Years later, the last time I applied for a job, in the first interview, I shared my screen and walked the interviewer through my blog.

The interviewer asked if I contributed somehow to the coding community. The process went smoother from there. I didn’t have any coding interview after that, except for opening a PR on an open source project. That was it.

Sharing your thoughts and learnings can open unexpected doors. Even if you don’t land new jobs, you’ll learn new skills. And more importantly, you’ll learn to think better. So write your first online piece and see what opportunities it brings. But don’t start a blog.

I'm Ditching My To-Do List: Here's What I'm Doing Instead

I used to be a productivity freak with to-do lists.

At a past job, I had a notebook where I wrote down every single action I needed to finish. Small tasks, large tasks, meeting notes… Everything.

Later on, I became a plain text lover and kept my to-do list in a .txt file I edited with Notepad: a “todo.txt” file.

Same story as my notebook at my past job. Even worse. I had “todo.txt” files for work and non-work. One in my personal computer and another in my work computer. My to-do lists grew without control. I still have items in my “todo.txt” file from years ago. Oops!

But there’s something with to-do lists.

To-do lists are stressful.

Every item on our to-do lists is an item we haven’t finished and probably won’t finish either. In the meantime, they’re another source of stress.

I learned from Choose Yourself Guide to Wealth by James Altucher to ditch to-do lists and goals, and live by themes instead.

The theme I want to live by in 2025 is the Daily Practice: doing something for my mind, body, and spirit every day.

As part of my Daily Practice, I’m sticking to:

  • A glass of water after waking up
  • A workout session
  • A moment of silence
  • Writing 200-250 words
  • Coming up with 10 ideas
  • Getting rid of negativity

Few things have helped me change my life like the Daily Practice.

That Daily Practice helped me get my health and life on track after burning out. Focusing on my health brought clarity to my life last year.

Goodbye “todo.txt” file and hello Daily Practice. That’s my only rule for 2025. You should give it a try too.

If You Enjoy Coding, Think Twice About Joining the Management Track

It took me 10 years to learn this lesson:

The higher up you go, the less it’s about coding and more about all other skills.

Being the best at coding won’t get you higher on the corporate ladder. Well, the corporate ladder is a trap.

Unfortunately, few places offer growth opportunities for coders, and even fewer for those who don’t want the management track.

Every place has its own expectations for team leaders or managers.

In some places, the team leader role is divided between:

  • someone technical in charge of coding and architecture decisions, and
  • someone non-technical in charge of project management.

In other places, a team leader wears all hats, often for the same pay.

Making the jump into a leadership role

If you enjoy coding and are thinking about joining the management track, start by understanding that your role as a team leader is more like a movie director than an actor.

Your job is not to appear on screen, except for some cameos. Your job is to make sure your movie gets done as expected and on time.

For that, you’ll need coding skills. Sure. But much stronger soft skills.

You’ll spend most of your time in meetings, not coding:

  • Daily meetings with your team,
  • Daily meetings with all other leaders,
  • 1-on-1s with every team member,
  • Sync ups with project managers and product people

Once you understand you’re the director, not the best actor, show your interest in exploring the role with your team leader during your 1-on-1s or performance reviews.

Then, find easy and cheap ways to validate if being a team leader is a role you’d enjoy:

  • Organize and tidy up your project board
  • Cover your team leader during their vacation
  • Be the onboarding buddy for new team members
  • Coordinate efforts to complete a feature from requirements to deployment

That will force you out of your “coding” comfort zone into the soft skill-heavy zone.

As a leader, you’re not responsible for your own code anymore. You’re responsible for all other coders and the code they write.

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.

Stalking a Writer Online Made Me Change My Reading Strategy

I’m a recovered book addict.

Two years ago, I tried to read as many books as possible to show off my huge book count. But I didn’t remember much about those books, even when I took notes.

Ironically, it was another book, The Almanack of Naval Ravikant, that made me change my mind.

By pure accident, I discovered my new reading strategy.

Last year, for the first time, I discovered James Altucher.

I found his bankruptcy stories. I followed his idea of becoming an Idea Machine. I read some of his books. I loved his idea of the Daily Practice. And without even realizing it, I was stalking James Altucher online. Quora, Medium, his own website, YouTube… Everywhere.

By immersing myself in his work, I heard extra details about the stories in his books. I learned his book publishing strategy. I learned about the motivation behind some of those books. And I listened to way more anecdotes.

So, from now on, I’m immersing myself in a writer’s world by reading their books and listening to their interviews. It adds more context and depth to my reading experience. Yes, often listening to an interview about a book counts as reading the book itself.

As a Team Leader, You're Not the Best Coder Anymore

Promoting the best coder to team leader is how projects go sideways.

I’ve seen it happen. One day, an executive pats the best coder’s shoulder three times. And the next day, he’s a team leader. No training. No expectations shared. Just a new title, a team, and lots of meetings.

That new leader continues thinking in terms of lines of code and pull requests, failing to delegate, pass context, and coordinate a team.

The next thing you know, the new team leader burns out and leaves the company. The project? Behind schedule and without a leader.

Being good at coding opens doors for leadership roles. But to shine as a leader, you need stronger soft skills.

You’re not the best player on the team anymore. Now you’re the team coach. You’re not supposed to be the fastest runner or the best at kicking. You’re supposed to manage a team.

Soft skills are way more important than coding because the higher up you climb the ladder, the less it’s about coding and the more about communication, project management, and team dynamics.