I need MOAR negative Feedback!

in Synergy Builders3 days ago

One thing that I did not anticipate, is how hard it has been to bait you all into criticizing me. It's like you all "like me" or something 😍. I had expected at least a few "shove off"s, but no - nothing of the sort!

But still I can tell you want to! Friends for a long time, don't respond.

Accept my friend request - leave me ghosted! I want your criticism :)

untitled.gif

Let's go through them again:

I don't understand = Explain it like I'm 5
Too vague - Get specific
Too wide
We dont need beem - We're doing it anyway
Too quick (voting)
Too tight (payout)
Remove Travel
Remove hive power
Should be done by one dev and raspberry pi rejected

New Feedback - Are you aware we already have Frontends?

image.png

Now that I have been specific, we get a new class of criticism. I'm ready for it - here we go! "I don't like a specific thing about what you are doing". I will need to make sub-lists for these.

We chose 4 champions, which I think can stand on their own. Number 4 is the beemhive-nectar stuff, so mostly I think that has been validated - asked and answered.

Yesterday I reached out to @ura-soul again (, again). Poor guy, he has to put up with me extra because lots of you are too (insert the thing you are here, busy, uncertain, fence sitting), so I have to go back to this kind soul who would just like to rest his eyes.

But he gave me some great feedback -

Isn't this repeat work?

And of course not! Its so obvious to me - but that's why I can't see it. That's why I need the feedback

In the case of FiscalForge - he asked if we were repeating work from Keychain Store, Distriator or SpendHBD, or even HiveDebit. Frankly I think some or all of these apps will use our FiscalForge, and I use or plan to use all of these things; in the case of Keychain, exclusively and extensively integrated into the things we are building and already have built.

I onboarded @jthomasewsky - He's going to give me a HiveDebit card for Ecobank in Talent Land Guadalajara. We are friends.

And of course - this brings up a lot of tutorials and maybe even branding work that HAF "apps" will need, because I'm pretty sure people are thinking they are going to download it on their phone. But no, if you read carefully (I'm sorry - what else can I do but type more?), you will see - FiscalForge doesn't even include a front-end!

It's an API and yeah most projects would probably build a front end and "make their mark", but it is specifically because I see all these use cases - that we decided that a HAF app would be just the thing to bring it all together.

In order to explain HAF app more, I will get @blocktrades on for a technical discussion about it.


Immediately after the comment, I reached out to @mengao , an amazing developer of the SkateHive community front-end, and we started working through my inability to articulate (yet!) the distinctions between what I am doing and "all the other front-ends, including the open source ones".

But that is the next post.

Without this rapid stressful period, it would have taken me months or maybe years to figure out how to say all this stuff in ways people understand.

Do you get it now?

I NEED YOUR FEEDBACK

Simple Vision
4 specific Champion Modules

and if you like -

vote my proposal bro

Sort:  

Hey, this is your lucky day - giving negative feedback is my job 😈 (as a translation reviewer).

  1. The reason why I'm not voting for the proposal is the payout in 11 days. I don't think this makes you look unreliable, I think it makes you look contrarian. If you want to change the fundamentals of how the DHF works, you'll have to convince a significant part of the community first. I'm sure it would be convenient to receive the money up front, but I haven't seen a good reason why we would agree, setting a dangerous precedent for future proposals. Working for a DAO is never going to be like a real job.

  2. Receiving Hive Power from the fund is also something anyone would like, but not necessary for the success of the project. I'd also remove the travel but keep a 10k marketing/communication budget. Improving structured communication between Hive devs would be useful indeed.

  3. Throwing around the names of RedHat and Mithril is only confusing me. Is this project technically related to Mithril.js at all? Certainly not for the beem upgrade? And what makes you think that you can achieve RedHat's level of professionalism?

  4. Why is there only one developer in a team of eight?

  5. I don't like the packaging of very different tools. I'm interested in Nectar and yourFrontend, the badge thing is not a priority, just nice to have, and the FiscalForge would probably benefit from cooperating with other teams.

  6. While the HiveTools website looks nice, the yourFrontend service looks ugly and barebones - worse than hive dot blog. Will you add instructions and examples of how to apply style sheets to the feed?

And finally a feature request: as a Hive blogger, the microservice I need is a way to schedule future posts, in a way that's easier than running a cron job + beem. Currently I'm using PeakD for this, but I don't want to depend on them too much, and I'm not sure how many scheduled posts they allow.

you get all the votes. its saturday now but I will be taking notes and keep on posting!

I can give you plenty of feedback, just join me on a voice call and I'll put my mic close to my speakers till they screech like crazy!!... I jest ofcourse.

It's surprisingly hard to get feedback, this is why you constantly get inundated with customer surveys and all that other junk..

I actually don't have any real feedback to give, Someone taking on the maintenance of beem is good though normally you'd just update the existing lib rather than branch it off into it's own new lib but I can understand why you would do so, (npm package management stuff and what not)

Having multiple libs is great, even though a lot will eventually be superseded by WAX when it get's released for more languages that is and is completed, even then choice is good!

Same with what was mentioned about repeated work, there is no such thing! having choice and more that one entity running/building out an idea is what we NEED.

Just like we need a KeyChain alternative cause choice matters and it's also less points of failure..

Anyways I digress...

I'm a hive witness supporting the blockchain please consider voting for me! - Find out more here!

Bro! Nailed it!

The issue with updating beem is holger80 is effectively dead. disappearing dev bro, everybody knows.

Love that feedback, and I really would love to get you on a podcast!

(shill those links 😍 let me boost you)

You’re practically begging for a roast now but everyone’s just being weirdly nice. Maybe they’re scared you’ll actually take their advice and outshine them all. Keep hustling Mr Eco

untitled.gif

We dont need beem - We're doing it anyway

That's what decentralization means, isn't it? Different "we" have different ideas, and eventually what comes out of the mix of everything should be better than something centralized. At least that's how things are, in theory.

I love these theories!

Now I am putting them into practise! I wonder - does HIVE think this "is worth money"?

I guess we will see... The DHF seems to be in a hedgehog mode recently.

Love that thought! Good way to put it

untitled.gif

Hey, keep going! 😎👍

Appreciate you!

We're all in the same boat! 😎

we most likely like you 🤩🤩

Thanks for this!

I spent a semester (a couple years ago) trying to teach some bright students how to do some development work on Hive.

That experiment mostly failed and that was mostly because the tools you are aiming to “fix” were so broken and disjointed that my students could not even replicate the tutorial exercises, much less create their own stuff.

Sorry this isn’t negative enough, but that’s the feedback I have to give at the moment.

Sounds like you are the type of guy who might want to vote on this proposal! Appreciate the validation there with your personal experience either way!