Really great points, especially #1. I like to stay up to date on this and I do miss posts as they're scattered and I have limited time to be here. #3 kind of feeds into this too.
#2 is a no brainer, this is really important.
#4 is interesting and I'm not sure, but I think it could be a really good move. I've read plenty in the last days about Steemit being too directionless and that this makes mass adoption hard. I know it doesn't directly apply, but another maxim of programming is that a component should do one thing and do it well. There's some that think that, though I'm not so sure. I like the idea of different clients having different focuses (e.g. the instasteem idea which seems to be in closed production currently).
A lot of great posts have come out of these discussions, it's been interesting. I'd love to see something from @ned or @dan in response soon 🙃
Yeap, me too. That would be nice.
We want to scale the engineering organization first, and will add support and community resources as the market expands. In my opinion, we aren't there yet.
Thanks for the note, and your perspective here 😋 Actually far too often it's the engineering team that is lagging behind so perhaps a good move. 👍
Probably the issue is more about the current user base, but I guess the sub text is: patience!
Can i ask, as an engineer, do you see it as important that the userbase in fact does not grow too much too soon at this point? 🤔 I've heard some people throwing around that idea and it makes a certain amount of sense.
not working, which is "code will fix everything". I will just restate my opinion: code is important, but only if you have real people using it.@sneak, this looks like exactly the type of approach that I specifically outlined as
When you have 10k+ people posting every month on your platform, but you think this is not enough to add a customer support/community manager person to the team, then funny things may happen and funny things usually spiral very fast out of control.
Of course, I may be wrong and we can safely agree to disagree.
I didn't state or believe that "code will fix everything".
I said that in my opinion, it is too early to add support resources yet. We don't even have a mobile app yet.
There is a mobile app, I'm using it right now to post this comment. It's not made by Steemit Inc but it's widely used.
And you are paying -$7000/day to users, or -$210.000/month. That's a lot of money spent for a community "not big enough to justify support resources yet."
Anyway, like I said, we can safely agree to disagree.Its your business, I just own a tiny, tiny part of it...
That payment amount is not based in any way on the size of the community.
I didn't imply that. I was just saying you're already burning an incredible amount of money just to have (a certain number of) people posting. It would make sense to spend at least 2-3% of this just to see why, what and how those people are posting and to extract business intelligence out of it. Since you're already paying A LOT of money just to have them posting...