My Insight & Constructive Criticism After Pretending To Be A Developer Exploring Steem & Github For The First Time

28일 전

Bernie's post got me in the mindset to pretend I was a badass blockchain developer exploring Steem for the first time.

So, it's freewrite time... but a different one than usual...


Let's begin on this journey...

  • If I went to Steem.com as a curious developer, and ignored the fake looping stream of blockchain activity from 6 imaginary accounts (sigh), I'd likely see Developer tab and head there. P.S. I can only see this tab if my browser is maximized as the scaling of the page isn't dynamic.

  • The big reveal! Not a lot of options with bare bones text for half a trackpad scroll if you go down, which caps off with another button to press to "Start Building." I guess I'll just click it.

  • Ok, this is a little more promising. I flipped through several tabs and it seems like there's sufficient info for a tech guru to get rolling.

My main takeaway is that I'd need to get familiar with the API portal to do anything. I think this portal overview page above needs to be much more prominently advertised. It's thorough and very valuable.

  • After this resources page, the next step seems to be the Github Dev Portal. This appears promising, so now it's time to get into the weeds to see what's going on!

Hmm, under the "develop" branch, things look rather stale. Maybe those are older issues or higher level folders, and all of the fresh activity fueling our technological advancement is within. From what I can find, that's not really the case. Unless I'm missing some big veins here, it looks like only a small amount of developers are active here, and activity is pretty sparse. New activity seems pretty light.

Critical role playing as newbie: Does this mean not much development is going on at Steem or Steemit? Seems pretty boring and not much going on. Ehh.

  • First impressions are important, but I'm not completely scared off yet. I'll check out the issues tab to see what the pulse is...

The 44 open issues all seem pretty old. Is this a ghost town? Why are so many issues still open? Spoiler alert, the closed issues tab list has one closed issue as of 11 days ago, and then NOTHING since January 3, 2019. That doesn't seem exciting to me as a "developer exploring Steem."

  • I'll check the pull requests then... There's got to be some life there. Just 5 in the last 9 days by one Steemian, one in July, and then nothing since January.

  • Maybe I'm looking at this wrong. I'll try to zoom out and see the bigger picture. Luckily I stumbled around to find this.

Commits:

Additions:

This is pretty disappointing, even if it's not accurate (maybe). This is what people are going to see when they dig around for the first time.

Still trying to be optimistic, I fumbled around to find this, which looked promising with other 50 sub-portals. However, most are very stale.


It's my conclusion (as a random dev exploring Steem for the first time), that the Dev Portal seems relatively barren and mundane. Where's the budding life of a top blockchain I'd want to get my hands on?

I suppose the API code that's already written is where the excitement is and motivation to get involved should becoming from?

I'll see if the community can elaborate and educate me on that last question. I'm not


I'm not bashing here. It's vital that we put our best foot forward if we can new users and devs to flock to Steem. In all honesty, and I'm not a programmer at all, this would've completely turned me off or left me hanging without a direction for a next step.

If I visited Steem curious, I'd have a hard time getting excited about taking the next step. That interest would likely need to come from signing up to start blogging/reading blogs to get a better idea of things.

If not, how else would I be able to learn about development on Steem or Steemit without familiarity with the ins and outs of browsing the blogging platforms... if I got that far?

There's not much on YouTube and it's hard to search on Steemit. We've been conditioned to accept the latter, but it's likely shooting ourselves in the foot in the name of new adopters.

Thanks,
@steemmatt

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
STEEMKR.COM IS SPONSORED BY
ADVERTISEMENT
Sort Order:  trending

As a developer, I tend to look at a project's Github page first, more particularly at the README in order to find resources, figure out how to run the project, learn more about the status of the project. As long as the last commit isn't years or months old, there's an indication that somebody is working on it and it's not an abandoned project.

In terms of wanting to develop within a framework or contributing to a project, you want to have some type of documentation laying out how the project is designed, laid out, use cases, examples, etc. Naturally looking at Steem's README, you are guided to the developer's portal so that's at least working.

The current introduction fails as it just jumps into resources without explaining what Steem is from a high level perspective which other libraries and projects I have worked on have elaborated significantly on. Here's an example of decent documentation and you'll notice a clear difference in the effort taken to allow new users to get opportunities to understand what they might potentially be working with.

Most developers don't understand blockchain and most developers will struggle on understanding a particular architecture or design without documentation and diagrams to educate them along the way. The dumber you assume the developers reading your documentation are, the better and richer the documentation will tend to be. And the more likely you will be able to attract new talent and probably inexperienced talent to your project.

@steemmatt,
My first 2 years on this chain was useless. Daily posted some sh!ts and comment others (I still do)! After all I started my own token project and had no enough money to pay for tribes! But that weakness built an opportunity to start my next journey as a developer! I am still scratching the surface, but so far so good! So what you do today is worthy more than wasting time with posting something that worth few STEEM today!
!trdovoter 100

Cheers~

·

Congratulations @theguruasia, you are successfuly trended the post that shared by @steemmatt!
@steemmatt got 6 TRDO & @theguruasia got 4 TRDO!

"Call TRDO, Your Comment Worth Something!"

To view or trade TRDO go to steem-engine.com
Join TRDO Discord Channel or Join TRDO Web Site

Interesting...seems sloppy or insincere motivation.

·

I'm not sure what to make of it, but I'm glad two people involved there took the time to reply here with some info.

Good to see that ads are going to be a part of the Tribe model.
Lets hope that more users and community owners take advantage of this service.

·

Congratulations @trendo.marketing, you are successfuly trended the post that shared by @steemmatt!
@steemmatt got 6 TRDO & @trendo.marketing got 4 TRDO!

"Call TRDO, Your Comment Worth Something!"

To view or trade TRDO go to steem-engine.com
Join TRDO Discord Channel or Join TRDO Web Site

First impressions as you say...

I'm not a dev at all so github and all that is very alien territory for me.

I hope some of the dev's in the know can pitch in on this...

Maybe @inertia could give some more insight?

·

Yep, finding activity on the devportal is a needle in a haystack, which is a problem. Only one person is working on it right now (me).

The hypothetical developer looking for activity would probably want to stick to the documentation, as the OP suggested. However, there's a good chance they'd look at the organization, if they saw a lack of activity in documentation.

If they did stick to documentation, then the OP on the right track. The OP even found the list of forks, but github UI wasn't much help there. My devportal fork is:

https://github.com/inertia186/devportal

And my active branches are:

https://github.com/inertia186/devportal/branches/active

And I organize these issues here:

https://github.com/inertia186/devportal/projects/1

Even the most active github users might never locate all that. The point of my fork is not to reach the developers on the platform. It's to reach the folks at Steemit, Inc. so they can merge my pull requests so that then my documentation can reach the developers on the platform.

·
·

Thank you for all the extra information on this @inertia.

Congratulations @theguruasia, 100% upvote has been shared with your successful call on the post that shared by @steemmatt!


Support @trendotoken projects by delegating : 100SP , 200SP , 500SP , 1000SP , 2000SP