Building in Public: How Writing and Content Creation Became a Tech Career Strategy

There is a developer somewhere right now who is more employable than you — not because they can code better, but because people know they exist. They share what they build. They write about what they learn. They post their failures alongside their wins. And somehow, recruiters are sliding into their DMs, conference organizers are inviting them to speak, and companies are offering them roles without a single job application.

This is the “build in public” movement, and in 2026 it has become one of the most powerful career levers available to tech professionals worldwide.

What “Building in Public” Actually Means

Building in public is the practice of sharing your work, process, failures, and learnings openly — on social platforms, newsletters, blogs, or GitHub — as you build something, not after it is polished and finished. It is the opposite of the corporate culture of keeping everything under wraps until launch day.

The concept gained traction in the indie hacker community around 2018–2020, when solo developers like Pieter Levels began sharing revenue charts, code decisions, and product failures in real time. Levels built Nomad List and Remote OK while tweeting every milestone and setback. He turned transparency into an audience, and that audience into a business worth millions.

But building in public is no longer just for solo founders. It has become a mainstream career strategy for engineers, designers, product managers, and data scientists working inside companies. The signal is simple: if people can see your thinking, your taste, and your consistency, you do not need a résumé to get opportunities.

Swyx and the “Learn in Public” Framework

In 2018, engineer and writer Shawn Wang — known as swyx — published a short essay called “Learn in Public” that quietly reshaped how thousands of developers think about career growth. His central argument: whatever you are learning, create the resource you wished existed. Write the blog post. Record the tutorial. Tweet the thread. Do it badly at first. Publish it anyway.

The logic is compounding. Every piece of content you publish is a permanent artifact that works for you while you sleep. A blog post explaining how you debugged a tricky Kubernetes networking issue will be read by engineers with the same problem for years. A Twitter/X thread breaking down how you approached a system design interview will be shared hundreds of times. Each artifact expands your surface area for luck.

Swyx’s framework does not require you to be an expert. It requires you to be one step ahead of someone who is struggling with what you just figured out. That is enough. The person who writes for beginners while they are still a beginner has an enormous head start over the person who waits until they feel qualified.

Real Examples That Changed Careers

The pattern of content-driven career acceleration is well documented. Marc Lou, a French developer, built and shipped over 15 small SaaS products while posting every step on X. His transparency about revenue, churn, and code architecture built an audience of over 100,000 followers and generated product sales that outpaced any salary he had ever earned.

Josh Comeau, a former developer at Khan Academy and Gatsby, started writing deeply technical interactive blog posts about CSS and React. The quality and consistency of his writing led to a course business that earns millions annually and a personal brand that rivals companies with marketing departments.

On a smaller scale, hundreds of developers report landing their current roles because a hiring manager or CTO saw a specific GitHub repository, a LinkedIn article, or a Dev.to post. One tweet explaining a clever solution can reach the right person at the right time. This is not luck — it is surface area. The more you publish, the more surface area you have for opportunity to land.

Platforms That Matter in 2026

The platform landscape has shifted. In 2026, the most effective channels for tech professionals are:

X/Twitter remains the fastest distribution channel for short-form technical ideas, product updates, and hot takes. The algorithm rewards consistency and engagement, and the tech community is still deeply concentrated there despite fragmentation.

LinkedIn has quietly become serious territory for long-form technical content. Engineers who dismissed it as a recruitment site are now finding that thoughtful posts about architecture decisions, team dynamics, or career lessons reach hundreds of thousands of views with almost no following required.

Substack and newsletters offer the most durable relationship with an audience. Email subscribers are not subject to algorithm changes. A newsletter with 2,000 engaged subscribers in a niche technical area carries more career weight than 20,000 passive Twitter followers.

Dev.to and Hashnode serve as searchable archives for technical tutorials. A well-SEO’d article about a specific framework issue will drive consistent organic search traffic for years.

GitHub itself is a portfolio. A well-maintained profile with active repositories, clear READMEs, and public commits is the silent version of building in public — visible to every recruiter who looks you up.

How to Start Without an Audience

The most common mistake is waiting until you have something “worth saying.” You do not need 10 years of experience. You need one insight, one problem you just solved, one observation about your field that someone else might find useful.

Start with a commitment to consistency over quality. Publish one piece of content per week for three months. It does not matter if ten people read it. What matters is that you develop the habit, the writing voice, and the library of past work. The audience follows the library, not the other way around.

Pick one platform and go deep before spreading to others. A developer who posts every day on LinkedIn for six months will outperform one who posts sporadically across five platforms.

Document before you teach. If you are not ready to explain something, document it instead — “here is what I tried, here is what happened, here is what I am still figuring out.” That kind of honest narration is often more engaging than polished tutorials.

Metrics That Actually Matter

Vanity metrics — follower counts, likes, impressions — are poor proxies for career impact. The metrics that actually matter are: inbound opportunities (job offers, collaboration requests, speaking invitations), email subscribers, and the quality of replies and conversations your content generates.

A developer with 800 newsletter subscribers in the cloud security niche will be noticed by exactly the companies hiring for cloud security roles. Niche audiences with high intent are more valuable than massive passive ones.

The Risks and How to Navigate Them

Building in public has real risks. Sharing work-in-progress can expose incomplete thinking to critics. Posting about your employer’s tech stack may create legal or reputational issues — always check your employment contract and avoid disclosing proprietary information.

There is also the risk of burnout. Content creation is real labor. Sustainable output is better than explosive starts followed by six months of silence. Treat it like a fitness routine, not a sprint.

The biggest risk, however, is not building in public at all. In a market where AI is compressing the perceived value of generic technical skills, the professionals who are known — who have a visible track record of thinking and building — are the ones who remain irreplaceable.

Sources & Further Reading

• Learn in Public — Shawn Wang (swyx.io)
• Pieter Levels — Building in Public (levels.io)
• How I Built a Thriving Developer Blog — Josh Comeau
• The Build in Public Playbook for Developers — Indie Hackers
• Technical Newsletters on Substack — Substack Discover