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

  ## 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