🤖 When I was younger, I liked to build things (still do), and I was very often surprised that people were not just flocking to my fantastic new project once I released it.
After some time, I understood the truth.
💡It really helps if you are good at two things - doing stuff and telling others about it. Being good at one of them is also acceptable if you have a partner who can support you with the other part.
To start getting good at talking about things, I started writing and sharing my thoughts. Bits and pieces of my experience that some people might find helpful.
👍 And when I’m at networking events (which happens very rarely), I usually talk about the cool projects that we’ve built at mindnow, not about who we are and why we’re fantastic. It’s cool to share the stories of how we managed to do X with Y limitations, and everyone ended up happy.
There are also many other ways to make yourself visible - conferences, contributing to open-source libraries, writing guides, books, whitepapers.
🚀 I think making a name for yourself like “the person who built that cool thing” or “the guy who posts stories on LinkedIn” is fun. The next time someone, who saw your value, thinks of something related to your area of expertise - they’ll come to you.
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!