How Writing in Public Accelerated My Cloud Career (And How to Start)
The highest-leverage career move most engineers never make.
Hey, it’s Lefteris 👋 I’m the voice behind the weekly newsletter “The Cloud Engineers.”
Here’s a career truth that took me too long to learn: being good at your job is necessary, but it isn’t enough to advance quickly. The engineers who move fastest aren’t always the most technically brilliant, they’re the ones whose work is visible. And the single highest-leverage way to make your work visible is to write about it in public.
I know, because it changed my trajectory. Writing this newsletter, publishing what I learn, and sharing it openly opened doors I didn’t know existed, such as speaking opportunities, connections with people I admired, and a reputation that arrives in the room before I do. This article is the practical case for doing the same, and a no-excuses playbook to start.
Why Writing in Public Works (The Mechanics)
This isn’t motivational fluff. There are concrete, compounding mechanisms at play:
It compounds while you sleep. A good article you wrote two years ago is still working for you today — being read, shared, and building your reputation. Almost nothing else in a career compounds like published work.
It forces clarity. You don’t truly understand something until you can explain it simply. Writing exposes the gaps in your knowledge and closes them. You learn the topic twice — once to do it, once to explain it.
It builds a surface area for luck. Opportunities can’t find you if you’re invisible. Every article is another door people can knock on. Jobs, collaborations, and invitations find people who are findable.
It’s proof of skill that outlasts any résumé. “I understand event-driven architectures” is a claim. A clear article explaining a real trade-off is evidence. Evidence wins.
The Objections (And Why They’re Wrong)
Almost everyone talks themselves out of starting. Let’s kill the four excuses head-on:
“I’m not an expert.” You don’t need to be. You need to be one step ahead of your reader. The person who learned something last month explains it better to a beginner than the expert who forgot what confusion feels like. Write from where you are.
“It’s all been written already.” It hasn’t been written by you, with your examples, in your voice. Your specific angle like the mistake you made, the trade-off you hit in production is what makes it worth reading.
“I don’t have time.” You don’t need much. A useful post can be 400 words about one thing you figured out this week. Consistency at small scale beats a heroic effort you never repeat.
“What if I’m wrong?” You will be, occasionally. That’s fine becayse the internet corrects you, you learn, you get better. The cost of a public mistake is far lower than the cost of staying invisible for years.
How to Actually Start
Here’s the playbook how to start:
Pick a lane, loosely. Write about the thing you’re already doing at work. For me it’s cloud and serverless. You don’t need a grand content strategy but a topic you touch every day so you never run out of material.
Start with what you just learned. The best first article is “here’s a problem I hit this week and how I solved it.” It’s authentic, it’s useful, and you already have the material in your head.
Choose the lowest-friction platform. Don’t build a custom blog first, that’s procrastination in disguise. Start where writing is free and distribution is built in: a newsletter platform like LinkedIn, Medium, or Dev.to. Reduce every barrier between you and publish.
Commit to a cadence you can actually keep. I write every Wednesday. The specific rhythm matters less than the promise you keep to yourself. Weekly is great; even monthly beats sporadic. The cadence is what turns one article into a body of work.
Write like you talk. Drop the corporate voice. Explain it the way you’d explain it to a colleague at lunch. Clarity and personality beat polish.
Ship before it’s perfect. Your first posts will make you cringe later and that’s a sign you’ve grown, not a reason to have waited. Hit publish. Iterate in public.
What to Expect (A Realistic Timeline)
Let me set honest expectations, because unrealistic ones are why people quit:
Weeks 1–4: Almost no one reads it. This is normal. You’re building the habit, not the audience yet.
Months 2–3: You get better and faster at writing. The occasional comment or share appears. The compounding hasn’t kicked in so keep going.
Months 4–12: A back catalog accumulates. Search and shares start bringing readers you never reached directly. People begin to recognize your name.
Beyond a year: This is where the doors open — speaking invitations, inbound opportunities, conversations with people you respect. Not because you got lucky, but because you became findable and stayed consistent.
The engineers who win at this aren’t more talented. They just didn’t quit in month two.
Conclusion
Writing in public is the rare career move with almost no downside and enormous, compounding upside. It sharpens your thinking, builds your reputation while you sleep, and turns your everyday work into a body of evidence that advances your career on your behalf.
You don’t need to be an expert. You don’t need a perfect platform. You don’t need much time. You need one topic, a cadence you can keep, and the willingness to hit publish before you feel ready.
Start this week. Write 400 words about one thing you figured out. Your future career will thank you. I promise mine did.