If there is uptake the plan is to build out a toolset to help with managing a portfolio of arbs.
I've been able to 'release' some simple tools into the public with plotly/django, but having to also then figure out things like gunicorn, dbms, vps hosting etc. is quite time consuming.
My biggest issue is that a lot of these frameworks seem to add complexity (under the guise of simplicity) as opposed to making things simpler. They just become more things to manage. Maybe I'm missing something and someone can point me in the right direction.
There are lots of pros on here who will find things like this trivial, but for someone like me (independent with limited professional dev training) the time investment is high as is the cost of "switching" between what seem to be mutually exclusive tasks (web dev/ops, and local analytics work).
Maybe spend the time finding a market with a problem that is lucrative enough to then spend time solving. And then figure out how to validate the problem...and then find a solution that you can get to market in a week or two (if not sooner).
This stuff isn't rocket science its just fucking hard work.
A good "cowboy" is one that gets the job done but can also build a sustainable, changeable process in their wake.
A good "drone" is able to spot ineffective parts of the system/process and change it.
As an aside, I really dislike the cowboy and drone nomenclature.
Coding is easy, testing and maintaining is hard.
Flyers should be 100% banned - just so much waste.
One of the marketing struggles I've had is just getting people to care. I did have a bit of an "If you build it, they will come" attitude because I had confidence in the quality of the work...but even that seems to be irrelevant if you can't get people interested.
As an introvert by nature (extrovert by necessity), I wonder what I'm missing that others seems to grasp innately, because the consequences are fatal for an entrepreneur if you can't convince others to at least try the thing you're offering.
How many times have you encountered a piece of software that is utter garbage from a ui/ux/engg. perspective but gets used ALL THE TIME? plenty of b2b examples of this including back ends of banks. They are awful, but they work. The business solves a very real customer problem and the tech is just a supporting (although still critical) act. As long as the problem gets solved, the tech. does not really matter. There is obviously more nuance to this vis a vis software maintenance etc. but when starting up, the tech should matter to you less than finding a valid problem.
But I think they are highlighting an important thing here that most of us struggle with...building is fun, progress is discrete and clear, the feedback loop is very tight. Selling and marketing to people sucks, its clunky, the feedback loops are variable, and if you're inclined more to being an introvert it is very exhausting.
I'm not sure the author is conditioned to fail as much as they are just more inclined to build.