so you wanna automate your dev workflow right? because who wants to spend hours tweeting about each commit but also you still want to seem active and engaged...
anyway part of the problem is devs tend to focus on the tech and forget about the actual people consuming their content...
like imagine you're scrolling through twitter and all you see are automated posts with zero personality does that get you excited? or does it make you feel like some fake robot is trying to sell you something?
even worse what if people start calling you out on that fake automation thing happened to my friend john (not his real name)...
Understanding Automation
okay so what exactly is this automation magic? basically its just scripting your workflow so you dont have to think about it...
but here's the thing though it only works if you set it up right...
speaking of which...
Automation Pitfalls
Invisibility Complex
so like for real automation can make devs seem invisible...
Fake Engagement Frenzy
btw have you ever scrolled through a dev's tweets and all you see are automated replies like 'nice commit!' or 'check out my latest feature!' sounds like aBot to me...
Delayed Project Syndrome
wait what was i saying about project delays? oh right...
this is all because of...
Automation Anxiety
like when you automate everything you start wondering if people actually care about your project...
Humanizing Automation
okay so how do you make automation less robotic?...
one way is to integrate human-like copywriting...
or like how push to draft does it for you honestly it's like having your own personal social media manager...
btw if you're tired of this whole automation conundrum push to draft literally automates this whole thing: https://commit.jolexhive.com/
...
anyway thats my take on dev automation workflows what do you think? are you guilty of falling into these pitfalls? let me know in the comments...
...and btw this article was written at 2am so excuse any typos...
Top comments (0)