I have earned ten cloud certifications. When I was starting out, the certs I collected did not change how I felt about my own ability. A project did.

It was a personal capstone from a course I was taking, built on my own time, outside work. My course mentor said: open source it.

So I did. I wrote it up and published it on LinkedIn: a multi-agent customer service system I designed and built myself, open for anyone to read and pull apart.

People I had never met started asking questions about the design, and it became the build I could explain in depth. But the bigger change was in my head.

This time, the confidence was real. Not the kind a pass mark gave me back then, which faded as soon as I faced a problem the exam had not covered. The kind that comes from building something and putting it in public.

Here is what I see every month with career changers. They collect certificates because certificates have a clear finish line. Study, sit, pass, post the badge.

A project has no finish line unless you draw one, so it sits half done on a laptop where nobody can see it. The certificate goes on the CV. The project, the thing that would make an interviewer lean forward, never leaves the machine.

A cert tells a hiring manager you can learn. A public build shows them how you think: what you chose, what you rejected, and whether you can explain it in plain words. That second list is the interview.

Learning plus building beats certs alone. The cert opens the door. The build is what you talk about once you are through it.

You do not need a big idea. You need one small thing that exists in public and that you can explain. Five steps.

Pick one project from your current study. Whatever module you are on this week, that is your material. Do not wait for a better idea.

Decide what "published" means. A repo with a README, a diagram, a short write-up, a live URL if there is one. Write it down before you start, or the finish line moves.

Set a ship date. Two to three weeks out. Rough on the day beats polished never.

Write your brief under four headings. The problem, the architecture and the trade-off you made, what you learnt, and what you would do next. The last two matter most, because they show you understood the build rather than assembled it.

Post it where the people who hire you will see it. I put mine on LinkedIn. Then tell someone it is live, so you cannot quietly take it down.

Do this once and you will know what I mean about the confidence. Make it a habit after each cert and you stop being the candidate with the badges and nothing to show.

Today's sponsor is Wispr Flow. When you are writing up a public build for LinkedIn, voice dictation can get the first draft out of your head faster than typing, so you spend the time on the headings that matter.

If you have paid time left on an individual Granola plan, we'll match it with a Wispr Flow subscription that includes Notetaker and dictation, and add bonus time, up to 12 months total. Sign in or create a Wispr account and submit proof of your plan to check eligibility.

Try Notetaker Free

💬 What are you studying right now, and what is one thing from it you could put in public in the next three weeks?

Reply with SHIP and a one-line summary of your brief. I will tell you the one thing I would tighten before you publish it. I read every reply.

Know someone with a folder of certificates and nothing public? Share your referral link. 1 friend subscribes, you get a free LinkedIn Profile Optimisation Checklist.

{{rp_refer_url}}

Shola

P.S. If you want to see a finished brief first, I wrote an example for a fictional capstone, using the same four headings: the Capstone Project Brief (1 page PDF), direct link, no signup. Next Tuesday: the short video I used to pay someone to edit, the AI model that edited it instead, and how I now use AI as a companion outside work. 6PM UK.