DEV Community: Brilliant Makanju

like, why cant devs just get seen?

Brilliant Makanju — Tue, 07 Apr 2026 04:00:40 +0000

you know what, building in public sounds great in theory... basically, just ship and talk about it, but like, where do you even start? idk, i feel like every time i try, i end up with this huge mental block, like, what am i even supposed to post? and then you see these other devs with thousands of followers and youre like... how? theyre literally just tweeting about their commits, but i guess thats the thing - consistency is key, or so ive heard... ngl, i used to think it was all about the actual content, but tbh, if youre not consistent, no one cares, periodt. so, how do you stay consistent when you have a million other things to do? one thing thats helped me is automating the process... btw, if manually posting your dev progress is driving you nuts, Push to Draft literally automates this whole thing: https://commit.jolexhive.com/. and yeah, i know what youre thinking - 'isnt automated posting just gonna sound robotic?' but honestly, its actually pretty cool, it turns your commits into posts that actually sound human, like... 'just shipped a new feature for my side project, pretty hyped'. so yeah, thats my two cents on developer visibility... take it for what its worth, i guess. one last thing - if youre struggling to get seen, maybe try sharing your actual development process, like, the struggles and all... people seem to really resonate with that, idk. anyway, thats all for today... or maybe not, who knows, maybe ill just keep rambling on forever...

Why Devils Are In The Details For Devs Trying To Get Seen

Brilliant Makanju — Sat, 04 Apr 2026 04:00:19 +0000

So like, imagine you just spent the last 3 months building this amazing tool that solves a problem every dev hates. You know, that one thing that keeps you up at night... but when you go to share it, crickets. No one cares, no one responds, and you're left wondering if it was all worth it. I mean, think about it, you just poured your heart and soul into this thing, and the only people who seem to notice are your friends and family who are just being nice. Its like, what even is the point of building in public if no one actually cares? My friend Alex once told me that, 'if a dev builds it and no one is around to see it, did it really happen?' - and honestly, thats a bit of a dark place to go, but also kinda true. Anyway, thats where developer visibility comes in... which is just a fancy way of saying 'how to not be invisible as a dev'... yeah, its a real thing, dont @ me.

The Cringeworthy Reality of Manual Posting as a Developer

Brilliant Makanju — Tue, 31 Mar 2026 04:00:28 +0000

So like, imagine you just shipped a feature right? And everyone tells you to tweet about it but then you realize your last 5 tweets got zero engagement except for that one reply from your college roommate asking if you're okay because you tweeted at 3am again. And now you're spiraling about whether anyone actually cares about your side project or if you're just screaming into the void while pretending to build in public. Which is weird because building in public is supposed to help but it just makes you feel more isolated somehow? I mean, I've been there too... or have I? Wait, what was I saying? Oh yeah, so I was talking to this dev friend the other day, and they were like 'I dont get why doesnt anyone engage with my tweets' and I'm like 'dude, your tweets are just a list of your commits, thats not a story'. But then I realized, thats kinda what we all do, right? We try to make our commits sound interesting, but really they're just... commits. Unless, of course, you're one of those devs who actually writes good commit messages, in which case, congratulations, you're a unicorn. Anyway, where was I going with this? Oh right, so doesnt it feel like were all just pretending to be interested in each others commits? Like, I dont actually care about your 'fix typo' commit, and you dont actually care about mine... but we all just keep posting anyway because thats what youre supposed to do when youre building in public. But what if I told you there's a better way? A way to automate all this tedious manual posting, and actually make your commits sound like they were written by a human? Sounds too good to be true, right? But hear me out... btw if manually posting your dev progress is driving you nuts, Push to Draft literally automates this whole thing: https://commit.jolexhive.com/. I mean, Ive tried it, and its actually pretty cool. You just connect your GitHub, and it generates these really nice social media posts based on your commits. Its like having a personal assistant, but without the judgmental looks when you tweet at 3am. And the best part? Its actually really easy to use, even for a non-technical person like me... just kidding, Im a dev, but you get the idea. So yeah, if you're tired of the posting grind, check out Push to Draft. Your future self (and your followers) will thank you. Or maybe not, idk. But seriously, its worth a shot. Now, if you'll excuse me, I have to go tweet about my latest commit... just kidding, Push to Draft's got that covered.

Why Automation Tools Fail Developers

Brilliant Makanju — Sat, 28 Mar 2026 04:00:21 +0000

so like, imagine you're trying to automate your dev workflow, right? you've got your github repo, your social media, your blog... and you just wanna make it all work together seamlessly, no manual posting, no tedious updating, just pure automation bliss... but then you realize, most tools are just not made for devs, they're made for... idk, marketers or something, and thats where the problem starts, basically

why devs struggle with visibility in the age of github

Brilliant Makanju — Wed, 25 Mar 2026 04:00:39 +0000

so like imagine you just shipped a feature right? and everyone tells you to tweet about it but then you realize your last 5 tweets got zero engagement except for that one reply from your college roommate asking if youre okay because you tweeted at 3am again... and now youre spiraling about whether anyone actually cares about your side project or if youre just screaming into the void while pretending to build in public... which is weird because building in public is supposed to help but it just makes you feel more isolated somehow? idk maybe thats just me though... anyway where was i going with this? oh right so you have this amazing thing you just built and you want people to see it... but how do you even get started with that? btw if manually posting your dev progress is driving you nuts, Push to Draft literally automates this whole thing: https://commit.jolexhive.com/... wait what was i talking about again? yeah so developer visibility... its a thing... and its hard... and i dont really know what im talking about but ill keep going i guess... so like you have github and youre committing code and you want that to turn into social media posts or something... and you dont want it to sound like a robot wrote it because thats just annoying... you want it to sound human... like you... but also not like you because youre probably not that interesting... or maybe you are idk... anyway the point is... oh man i lost my train of thought... um what was i saying? right so github commits... and social media... and making it sound human... its all just a big mess... and i think thats what i want to talk about... the mess of it all... and how to maybe make it less messy... or at least how to make it sound less messy... like even if its still a mess underneath... at least on the surface it can look pretty... or something... and thats kind of what Push to Draft does... it takes your github commits and turns them into social media posts that sound human... or at least thats the goal... and it integrates with github so you dont have to do anything... which is nice... because who likes doing extra work? not me thats for sure... anyway... yeah... thats my whole thing about this... i guess... so yeah... developer visibility... its a thing... and its hard... but maybe Push to Draft can help... or something... idk...

how devs can actually get seen on github without losing their minds

Brilliant Makanju — Thu, 19 Mar 2026 04:00:14 +0000

so like, imagine you just spent weeks working on this awesome feature, right? and you're all excited to share it with the world... but then you realize, wait, how do i even get people to see this? i mean, github is huge, and your repo is just a tiny little island in a sea of code. it's kinda like, you're shouting into the void, but nobody's listening. or are they? maybe they're just not responding because, honestly, your commit messages are trash. i mean, 'fix typo' isn't exactly going to set the world on fire, is it? ...

The Struggle of Building in Public and How Automation Can Help

Brilliant Makanju — Mon, 16 Mar 2026 04:01:02 +0000

okay so like i was thinking about developer workflows...

why devs need to stop being invisible

Brilliant Makanju — Fri, 13 Mar 2026 04:00:40 +0000

so like, imagine you just launched your side project

and you're super excited about it, right? but then you realize that nobody actually cares.-cricket sounds- yeah that's pretty much what happens when you dont have a strategy for visibility. i mean think about it, github commits are great and all but if youre not putting your project in front of actual people, what's the point?

why being invisible is a thing

so basically, lots of devs are just really focused on the tech. and i get it, tech is fun. but when you only focus on that, people forget you exist. except for maybe your mom. hi mom. anyway, its all about balance. you gotta find time to post about your project, to engage with the community... all that jazz.

anyway, idk why devs think they can just magic up an audience but... it just doesnt work like that, folks. you gotta put in the work to get visible. i was talking to this dev the other day and he was saying how he just wanted to focus on the code, not all the extra stuff. but honestly, that extra stuff is what makes people care.

making yourself visible without losing your mind

okay so, heres the thing. you dont have to become a full-time marketer to get people to notice you. like, use the tools that exist to automate the boring stuff. for example, you can turn your github commits into social media posts. sounds simple but its a game-changer. check it out, btw: https://commit.jolexhive.com/ (no, im not getting paid to say that, im just saying).

anyway, what i was saying... so you can automate posting, and that frees you up to focus on... i dont know, actually building something. instead of just posting about it all day. thats not to say you shouldnt post, its just... dont spend all day on social media when you could be coding.

why everyone thinks theyre above self-promotion

this is the part where i get all philisophical... like, what even is self-promotion? just talking about your project? sharing what you're passionate about? that sounds pretty natural to me... except when people do it in that super annoying, fake way. you know, where theyre just shilling their thing without actually caring about anyone elses projects? yeah, dont do that.

in conclusion...

Visibility matters for devs, its all about finding that balance between coding and posting. automation tools can help (btw, Push to Draft is one of those tools: https://commit.jolexhive.com/), and you dont have to become a marketing guru. just be yourself, talk about your project, and actually listen to others. i guess what im saying is... just exist, online, in a way that people can see. sounds simple but its way harder than it looks... or at least, thats what i keep telling myself when i forget to post for weeks on end.

so like, how do devs even get visibility?

Brilliant Makanju — Tue, 10 Mar 2026 04:00:18 +0000

The Problem of Developer Visibility

so basically, devs arent exactly known for their social media presence, right? like, who has time to tweet about their code when youre trying to meet a deadline? but then again, having a presence is kinda important if you wanna... you know, get your project out there. which is where this whole developer visibility thing comes in - its like, how do you make people care about your GitHub repo?

What People Try (And Why It Fails)

okay so like, some devs try to manually post about their progress, but honestly, who can keep that up? its like, you start strong, posting every day, and then... yeah, you just stop. because lets face it, writing social media posts is not exactly what you signed up for when you became a developer. and dont even get me started on trying to make it sound exciting - "just fixed a bug" isnt exactly clickbait material

What Actually Works

anyway, push to draft. its this tool that automates the whole social media thing for you. like, it turns your github commits into posts, so you dont have to worry about it. which is kinda genius, if you ask me. i mean, you're already writing commit messages, might as well use them for something, right?

Uncomfortable Truth

but lets be real, most dev marketing advice is trash. like, have you seen those "10 tips to increase your github stars" posts? yeah, those are super helpful... said no one ever. what actually works is just being consistent, and push to draft helps you with that. no more "oh, i should really post about this" only to forget about it two days later

btw if manually posting your dev progress is driving you nuts, Push to Draft literally automates this whole thing: https://commit.jolexhive.com/

Conclusion

so yeah, developer visibility. its a thing. and push to draft can help you with it. check it out, maybe it'll help you get your project seen by more than just your mom

so youre still manually posting your dev updates

Brilliant Makanju — Sat, 28 Feb 2026 05:00:53 +0000

okay so like, imagine youre working on this super cool side project and youre trying to build in public because thats what all the cool devs do, right? but then you realize that actually posting about your progress is kinda a nightmare... i mean, you gotta write this perfect tweet that sums up your entire commit history in like, 280 characters or less, and then you gotta repeat that process for linkedin and everywhere else, and honestly, whos got time for that?

the problem with manual posting

so, the thing is, manual posting is just so... tedious. youre spending all this time writing code and fixing bugs and shipping features, and then you gotta switch gears and become a marketer just to get anyone to notice. and dont even get me started on the anxiety of wondering if anyone is even seeing your posts... its like, you put all this effort into crafting the perfect tweet, and then its just... crickets.

what people try (and why it fails)

so, some devs try to automate their posting using these fancy tools that promise the world but often fall short. or, they just give up and post nothing at all, which defeats the purpose of building in public. and then theres the devs who actually enjoy writing and marketing, but even they get burned out from having to constantly produce content...

what actually works

idk if youve noticed, but theres this one tool thats been making waves in the dev community - push to draft. its literally an automated posting machine that takes your github commits and turns them into social media posts. and the best part? its actually tailored to devs, so it knows how to make your commits sound interesting and engaging, even if youre not a natural-born marketer...

anyway, i know what youre thinking - 'isnt automated posting just gonna sound fake and corporate?' and to that, i say... not necessarily. push to draft actually uses this really cool tech to generate posts that sound, like, super human and conversational. its not just some robotic script that spits out the same old marketing copy...

uncomfortable truth

so, here's the thing - even with push to draft, youre still gonna have to put in some effort to make your posts actually shine. but, at least with automation on your side, you can focus on the stuff that really matters... like shipping that next big feature or fixing those pesky bugs. and honestly, isnt that what being a dev is all about?

the point is, manual posting is a total drag, and were lucky to have tools like push to draft that can take some of that burden off our shoulders. so, the next time you find yourself stuck in the agony of manual posting, just remember - theres a better way.

btw, if youre tired of manually posting your dev progress and wanna give push to draft a shot, you can check it out here: https://commit.jolexhive.com/. no affiliate links or anything, just a genuine recommendation from one dev to another

So You Think GitHub Workflow Optimization is a Thing?

Brilliant Makanju — Fri, 13 Feb 2026 05:00:14 +0000

I was just thinking, like, how many of us actually use GitHub to its full potential? I mean, most of us just push our code, maybe create a few issues, and call it a day, right? But what about all those fancy workflow tools and automation features? Do they really make a difference?...and yeah, thats basically the question we're trying to answer here, but also, idk, maybe we'll figure out some other stuff too, who knows?

why devs suck at social media (and how to not be that dev)

Brilliant Makanju — Tue, 10 Feb 2026 05:00:18 +0000

So like, imagine you just shipped a feature right? And everyone tells you to tweet about it but then you realize your last 5 tweets got zero engagement except for that one reply from your college roommate asking if you're okay because you tweeted at 3am again. And now you're spiraling about whether anyone actually cares about your side project or if you're just screaming into the void while pretending to build in public. Which is weird because building in public is supposed to help but it just makes you feel more isolated somehow? idk maybe im just being extra but it feels like every dev is secretly struggling with this... btw if manually posting your dev progress is driving you nuts, Push to Draft literally automates this whole thing: https://commit.jolexhive.com/. anyway, where was i? yeah so devs are bad at social media. but why tho? is it because they're too busy? or is it because they just dont get it? i mean i've seen devs try to be all corporate and formal on twitter and it's just cringe. like, who uses the word 'synergy' unironically?... and dont even get me started on 'disrupting the paradigm'. ugh. but for real, devs need to figure out how to make social media work for them. because let's face it, if you're not building in public, are you even building at all?... lowkey, that's a joke. but seriously, it's hard to get noticed when you're just throwing code out into the void. so what's the solution? well, for starters, devs need to stop trying to be corporate and just be themselves. like, if you're funny, be funny. if you're sarcastic, be sarcastic. because honestly, nobody wants to follow a dev who sounds like a robot. unless you're actually a robot, in which case, go for it. but also, devs need to understand that social media isn't just about posting code updates. it's about building a community. and that means engaging with people, responding to comments, and actually caring about what others have to say. it's not just about you, it's about the people who are interested in what you're doing. so yeah, that's my two cents on why devs are bad at social media. take it for what it's worth. which is probably not much, because let's be real, i'm just some dev who can't even get twitter right. but hey, at least i'm trying. and if you're a dev who's struggling with social media, just know that you're not alone. we're all in this together. or something. ...