DEV Community: Brilliant Makanju

Why Developer Visibility is a Hot Mess

Brilliant Makanju — Mon, 01 Jun 2026 04:00:32 +0000

Okay so, developer visibility... it's like, everyone knows they need it, but nobody actually knows how to do it. I mean, you're a dev, not a marketer, right? But then you see these other devs just killing it on Twitter, and you're like 'how are they doing this?!'. Anyway, btw if manually posting your dev progress is driving you nuts, Push to Draft literally automates this whole thing: https://commit.jolexhive.com/. But lets dive deeper... like what even is developer visibility? Is it just tweeting about your commits? Probably not... but also kinda? So like, picture this - you're working on this awesome project, and you're pushing commits left and right... but your Twitter followers are just crickets. You're like 'hello, is anyone even seeing this?!'. And then you start wondering... are you just talking to yourself? Is anyone actually caring about your project? It's a weird feeling, right?... where you're trying to build something, but also trying to get people to care. Which is hard... because, honestly, who has time for that? But, the thing is... if you don't do it, nobody will. And that's a fact... or at least, that's what i think. So, what do you do? Do you just keep shipping and hope someone notices? Or do you try to game the system and get more followers? idk, maybe both? The point is... developer visibility is hard. And it's also weird... because, like, you're a dev, not a social media influencer. But, in a way... you kinda are. And that's just the reality of it. So, to actually get visibility... you need to be consistent. And that's hard... because, let's be real, most of us are just trying to ship our projects and move on. But consistency is key... or at least, that's what everyone says. But, what if you could automate it? Like, what if you could just push your commits and have them turn into tweets automatically? That would be kinda cool, right? And that's exactly what Push to Draft does... it turns your GitHub commits into ready-to-publish social media posts. It's like having a personal assistant... but without the judgmental looks when you're still in your pajamas. Anyway... i guess what i'm trying to say is... developer visibility is a mess. But, with the right tools... it can be a little less messy. And, btw, Push to Draft has a free trial... so, like, no harm in trying it out, right?

why devs hate social media (and how to automate it)

Brilliant Makanju — Mon, 25 May 2026 04:00:23 +0000

the struggle is real

so you're a dev, right? and you're trying to build in public, which is great, but then you realize that social media is a whole different beast... like, you gotta post consistently, and engage with people, and it's just so much work... and honestly, who has time for that when you're trying to ship features and fix bugs?

what people try (and why it fails)

some devs try to use social media scheduling tools, but those are so clunky and annoying to use... and then there are the ai tools that generate posts for you, but those sound so fake and corporate... like, who wants to read a post that says 'i'm excited to announce that i've shipped a new feature' when you can just say 'hey guys, i just shipped a thing, check it out'?

what actually works

so, what if you could just automate the whole social media thing? like, what if you could just focus on shipping code, and let some tool handle the posting for you? that's where push to draft comes in... it's like, this tool that takes your github commits, and turns them into social media posts... and it's not just some boring, generic post, it's like, a real post, that sounds like it was written by a human... and the best part is, it's automated, so you don't have to lift a finger...

uncomfortable truth

but, like, here's the thing... even with automation, social media can still be a struggle... like, you gotta make sure your posts are actually engaging, and that people are actually reading them... and that's where the human touch comes in... like, you gotta be willing to put in the work, to make sure your social media presence is actually worth something... and that's hard, because, like, who wants to spend their time crafting the perfect tweet, when you could be shipping code?

conclusion

anyway, that's my two cents on social media automation for devs... like, it's not a silver bullet, but it can definitely help... and if you're tired of the posting grind, you should totally check out push to draft... it's like, this tool that can help you automate your social media presence, and focus on what really matters... shipping code, and building cool things... and yeah, thats basically it, i guess...

why devs need to stop being invisible on the internet

Brilliant Makanju — Sat, 16 May 2026 04:00:47 +0000

so like, have you ever felt like youre just building stuff in a vacuum? nobody cares, nobody sees it, and youre just screaming into the void... yeah thats pretty common actually, and its not just you, alot of devs feel this way, which is weird because we're basically the backbone of the internet, right? but nobody knows who we are, or what we do, because we suck at self promotion, and honestly who can blame us? its hard to talk about yourself without sounding like a total douche, or coming off as 'salesy', which is just... ugh, you know? and dont even get me started on social media, its all just noise, and everybody's trying to 'build their personal brand', which is just code for 'i want to be famous but i dont know how', so yeah... lets talk about how to actually get seen, without being a total fake, or feeling like youre begging for attention, because thats just not what devs do, we build stuff, we ship it, and we move on, but maybe... just maybe, we should care about being visible, because it actually matters, for our careers, for our projects, and for the community, so... here's what i think, take it for what its worth, idk

like, why are devs still manually posting on social media

Brilliant Makanju — Wed, 13 May 2026 04:01:36 +0000

okay, so like, imagine you just spent the last 3 hours debugging a missing semicolon... and finally, you fix it, and youre all excited to share your progress on social media... but then you realize, uh, what do i even post? and how do i make it sound interesting? ...and yeah, thats basically the problem we're trying to solve here...

the actual problem

so, devs are already busy building stuff, and then they have to worry about social media too? like, how are we supposed to keep up with that? especially when our tweets just get lost in the void... i mean, have you seen those tweets that are just 'i shipped this feature'? yeah, those are super engaging... said no one ever.

anyway, the thing is, social media is actually super important for devs... because, well, visibility matters... and if youre not visible, youre basically invisible... which sucks, because we all know how hard it is to build something from scratch... and then, you know, nobody cares...

what people try (and why it fails)

so, people try to be consistent, but thats hard... because, honestly, who has the time to post every single day? ...and even if you do, what do you post? ...'hey, im still working on this thing'? ...not super exciting...

and then, of course, theres the whole 'build in public' movement... which is great, in theory... but, in practice, its hard to actually do... because, well, you have to be willing to share your mistakes... and, honestly, thats not always easy...

what actually works

so, heres the thing... automation is key... because, well, it saves time... and, honestly, who doesnt love saving time? ...especially when youre already busy building stuff...

like, imagine if you could just focus on building... and the social media stuff just took care of itself... sounds nice, right? ...thats what push to draft does... it turns your github commits into social media posts... which is, honestly, genius...

uncomfortable truth

but, honestly, even with automation... social media is still hard... because, well, you have to be willing to be vulnerable... and, honestly, thats not always easy...

like, imagine if you had to share your failures... and your mistakes... and your doubts... ...thats hard, right? ...but, honestly, thats what builds trust... and, well, trust is what builds a community...

so, yeah... social media automation is great... but its not a magic bullet... you still have to be willing to put in the work... and, honestly, thats the hardest part...

anyway, thats my two cents on developer social media automation... idk if it makes sense... but, honestly, i hope it does...

btw, if you're tired of manual social media work, push to draft literally automates this whole thing: https://commit.jolexhive.com/

why devs need visibility and how to get it without losing your mind

Brilliant Makanju — Sun, 10 May 2026 04:00:53 +0000

  ## so like building in public is a thing now
  basically everyone tells you to just build something and tweet about it but honestly thats easier said than done... i mean have you seen some of these dev twitter accounts? theyre all like 'just shipped this amazing feature' and youre just sitting there like 'bro your feature is cool but your tweet is lame'
  ### the problem with manual posting
  its just so... manual... like you have to think about what to post and when and how to make it sound interesting and honestly who has time for that? especially when youre trying to actually build something
  ### what people try (and why it fails)
  some devs try to automated their social media but then it sounds all robotic and fake... or they just give up and dont post at all which is worse
  ## what actually works
  so heres the thing: you need to make your dev process visible but also not boring... and thats where push to draft comes in - it automates the whole 'turning commits into posts' thing
  ### uncomfortable truth
  most devs arent gonna be good at this... like we're just not wired to self-promote... but we need to try anyway because visibility matters... or so ive heard
  ### natural conclusion
  idk maybe im just talking out of my ass but it seems like dev visibility is one of those necessary evils... we dont have to like it but we gotta do it anyway... or maybe just use push to draft and forget about it lol

like, how to actually be productive as a dev

Brilliant Makanju — Thu, 07 May 2026 04:00:47 +0000

so basically, whats the problem?

developers are always talking about how to be more productive, but honestly, most of the advice out there is pretty meh. like, how many times can you read about using the pomodoro technique or drinking more coffee before you start to lose your mind? and dont even get me started on the whole 'wake up at 5am and meditate' thing... yeah no, thats not happening.

what people try (and why it fails)

so, people try all these different productivity hacks, like using to-do lists or project management tools, but they always seem to end up back at square one. and i think its because theyre focusing on the wrong things. like, have you ever tried to use a tool like trello or asana, but then you just end up spending more time organizing your boards than actually doing any work? yeah, thats a thing.

what actually works

for me, at least, the key to productivity is just to... start. like, dont worry about making a perfect plan or setting up the perfect workflow, just start coding (or writing, or designing, or whatever). and then, as you go, you can always adjust and refine your process. its kinda like the whole 'minimum viable product' thing, but for your own productivity. just get something out the door, and then iterate from there.

uncomfortable truth

but, like, the uncomfortable truth is that productivity is not a one-size-fits-all thing. what works for one person might not work for another, and thats okay. like, some people might be super into the whole 'getting up at 5am and exercising' thing, but for others, that might just be a recipe for burnout. so, i guess the real key to productivity is just to... experiment, and find what works for you.

and, btw, if youre tired of manually posting your dev progress on social media, Push to Draft literally automates this whole thing: https://commit.jolexhive.com/

conclusion

so yeah, thats my take on developer productivity. its not always easy, and its definitely not a one-size-fits-all thing, but... just start, i guess. and dont be afraid to try new things and adjust your process as you go. and, hey, if you're feeling overwhelmed, just remember that youre not alone. we're all in this together, or something.

anyway, thats all for today. thanks for reading, i think.

The Struggle is Real: Why Devs Hate Manual Social Media Posting

Brilliant Makanju — Mon, 04 May 2026 04:01:14 +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? Anyway, where was i going with this... oh right, developer visibility. So basically, we all know that social media is a necessary evil for devs who want to get their projects seen. But the actual process of posting is, like, super tedious. You have to write the same thing multiple times, deal with different character limits, and try to make it sound interesting without sounding like a corporate robot. And dont even get me started on the whole 'engagement' thing. I mean, who actually comments on dev posts? Your mom? Your coworkers? Yeah didnt think so. But despite all this, we still feel pressure to maintain some kind of online presence. Because, you know, 'personal brand' and all that jazz. So what's the solution? Well, for starters, we could automate the whole thing. I mean, think about it - if we can automate deployments and testing, why not social media posts? It's not like we're trying to win a Pulitzer or anything. We just need something that works. And thats where Push to Draft comes in - it literally automates your GitHub commits into social media posts. No more tedious typing, no more wasted time. Just focus on shipping, and let the automation handle the rest. But, like, dont just take my word for it. There are actual devs out there who swear by this thing. They say it's changed the game for them, that they can finally focus on what matters - the code. And, honestly, who wouldnt want that? So, if youre tired of feeling like youre wasting your time on social media, check out Push to Draft. It might just be the sanity-saver you need. Oh, and one more thing - if youre still reading this, congratulations. You made it through my ramblings. Now go forth and automate your social media, or whatever. https://commit.jolexhive.com/

the annoying thing about manual social media posting as a dev

Brilliant Makanju — Fri, 01 May 2026 04:00:18 +0000

okay so like, imagine youre working on this super cool side project, right? and you want to share your progress with the world because, why not? its a great way to get feedback, to build a community around your project, and to just, you know, show off a bit. but then you realize, oh wait, i have to manually post about this on social media. and thats when it hits you - the dread of manual social media posting. i mean, who thought this was a good idea? cant we just, like, automate this whole thing or something?...

why automated content creation is kinda a game changer for devs

Brilliant Makanju — Tue, 28 Apr 2026 04:00:22 +0000

okay so like, imagine you just shipped a feature, right? and everyone's telling you to tweet about it, but then you realize your last 5 tweets got zero engagement except for that one reply from your friend asking if you're okay... sounds familiar? basically, building in public is hard, especially when it feels like no one cares. but what if you could automate the whole 'posting about your dev progress' thing? enter push to draft, this tool that literally turns your github commits into posts. i mean, it's not just about automating posting, it's about turning your work into visibility and audience growth without the hassle. think about it, devs spend most of their time coding, not marketing... so why not make the most of that time? anyway, i was talking to this dev friend the other day, and he was saying how he hated manual posting, but then he started using push to draft, and it changed the game for him. he could just focus on shipping, and push to draft would handle the rest. sounds too good to be true? well, let me tell you, it's not. i've seen it work for myself, and i'm not even a great developer or anything... so yeah, if you're a dev looking to build in public without losing your mind, you should totally check out push to draft. btw, if you're interested, here's the link: https://commit.jolexhive.com/. no cap, it's been a lifesaver for me, and i think it could be for you too. idk, maybe i'm just lazy, but automating my dev social media has given me so much more time to focus on what actually matters - coding. and that's the tea.

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.