Stabilizer has done quite a bit to keep HBD stable on the internal market although the spread is still not ideal and the amount of liquidity is extremely limited.
HBD is on literally one exchange externally and is pretty much left to do whatever and isn't an accurate indicator of HBDs PEG. Generally the haircut rule and internal markets are the only really indicators of it's stability at the moment and it's far from being perfect, and orders of magnitude worse than any other stable coin in existence today.
I'd argue it's better than nothing and I feel you'd likely agree but ofcourse it doesn't mean we should sit on our hands.
Hive fundamental issue has always been a lack of awareness, exchange listings, news coverage, user friendly UI/UX & onboarding procedures to name just a few and frankly I don't see this improving anytime within the next year. VSC might change this and accelerate some progress towards better UX/UI and onboarding but it's not going to be quick by any means.
With regards to paying coders specifically. I Imagine a system where coding tasks can be put up for coders, either individual or a team, can place BIDs on them of a price they want paying for the work, they person added the task could put up a price or price range they are willing to pay or the chain is willing to offer depending on what is going to pay for such thing in the end.
The job would be payed upon recept of functioning code, that is then merged and tested into the main code base, only then would payout be recieved.
The problem I have imagining atm is who gets the jobs.. How do we decide on that?
Is it decentralized done via stake based voting like the DHF. Natureally we'd require anyone bidding for a job to display coding background and previous projects, best done with github accounts as history of code contributions is easy to look at on there.
But it's deciding who we go with thats the part I can figure out right now.
I mean.. We could just make it a bounty system. Here is task.. it pays this much, if you build it and it gets tested and merged into the codebase cool you get paid..
But here another issue crops up.. Who decided if it's good code? Obviously the witnesses.. but. not many of the witnesses have exceptional code experience or knowledge of the HIVE codebase. Does the core team decide? the people in control of the codebase and sourcecode.. i.e blocktrades and a few others? Granted it's not total control, in an ideal world witnesses should actually review the code they are running when new versions come out but in reality many just trust blocktrades and the rest. Not all witnesses mind.. The concensus ones are all very familiar with the code and actually do proper reviews.
Anyway I digress..
I can imagine most of the system. just certain parts might require more thought..
Perhaps a google doc is in order to write down and design this thing.