đ€ I shipped my first ânext big thingâ sometime in 2010, posted the link on Hacker News, and refreshed the page every ten minutes. Zero comments, zero stars, zero anything. The code was fine; the silence was deafening.
It took a few more lonely launches before the obvious finally clicked.
đĄDoing the work is only half of the equation. The other half is letting the right people know the work existsâideally without sounding like a walking billboard. Iâm not claiming this is a universal law (Derek Sivers makes a good case that sharing goals too early can kill motivation), but in my experience shipping in total secrecy rarely ends well either.
Of course, skill alone still isnât enough. Luck, persistence, and the occasional after-work drink all sneak into the outcome. Iâve seen brilliant engineers stall because the timing was off, and average ideas take off because someone mentioned them to the right person on the right day.
To get better at the âtellingâ part, I forced myself to write these short newslettersâbite-sized lessons from the trenches. Some posts flop, some spread farther than I expect (Iâm still unsure why), but the rhythm keeps the muscle alive.
đ When I do end up at a networking event (once every few months, tops), I skip the elevator pitch about mindnow and jump straight into a story: how we squeezed a machine-learning prototype into a Raspberry Pi with limited RAM, or that time a legacy Oracle monster was replaced by four microservices over one frantic weekend. People remember the struggleâand the punchline.
This âshow, then tellâ pattern travels well. I watched someone demo a hacked electric skateboard at a Maker Faire. Right place, right artefact, very little small talk.
There are plenty of other stages: conferences, meetups, guest articles, open-source. A tiny repo I put on GitHub years ago was once demoed on a Google Cloud livestreamâsomeone there emailed me to ask how Iâd solved a corner case, which instantly made my whole week (Iâm still riding that dopamine).
Short-half-life platforms like Twitter or Mastodon feel repetitive because you end up posting the same link three times in one week. Post anyway. The feed moves so fast that a repeat is fresh for most of your followers.
đ Over time, these tiny signals stack. You become âthe person who built that weird automation scriptâ or âthe gal who keeps dropping solid Kubernetes tips.â When someone runs into a related problem, your name pops up in their headâand suddenly youâre on a call discussing a paid gig.
Other Newsletter Issues:
Worried your codebase might be full of AI slop?
I've been reviewing code for 15 years. Let me take a look at yours and tell you honestly what's built to last and what isn't.
Learn about the AI Audit →No-Bullshit CTO Guide
268 pages of practical advice for CTOs and tech leads. Everything I know about building teams, scaling technology, and being a good technical founder â compiled into a printable PDF.
Get the guide →
5 Comments
Absolutely, getting your work recognized is crucial. I’ve found that using specific, searchable keywords related to my projects in blog posts and discussions really helps increase visibility. Also, engaging with others in your field through comments can surprisingly boost your project’s profile because it shows you’re not just about broadcasting your achievements but also contributing to a community. This interaction has led to more meaningful connections and even collaborations, which wouldn’t have been possible if I had just focused on the coding side of things and ignored the importance of communication and visibility online.
I switched to using QR codes at presentations to directly link to my portfolio and GitHub. It boosted audience engagement instantly, helping people dive into my projects on the spot. Also, sharing progress on niche tech forums amplified visibility among those really into my tech area. Simple shifts in sharing methods can significantly impact how our work is perceived and connected with.
I totally agree, getting your projects noticed is a game changer. I started blogging about my code adventures and it really helped me connect with like-minded folks. Also, speaking at local meetups boosted my confidence and expanded my network. It’s funny, but jumping into discussions on tech forums has also led to some unexpected collaborations. Keeping it simple and genuine works wonders.
Sharing our projects and achievements is as important as creating them. It’s about being in the middle between being a maker and a storyteller.
It’s like, you’re in your tech bubble, coding away, thinking you’re the next Jobs or Gates. But hey, if no one knows what you’re up to, does it even matter? We gotta get out there, share our GitHub repos, blog about our hacks, maybe even do a tech talk or two. Let’s geek out loud, people!