Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

8. Managing User Accounts #85

Open
twof opened this issue Jul 25, 2017 · 2 comments
Open

8. Managing User Accounts #85

twof opened this issue Jul 25, 2017 · 2 comments

Comments

@twof
Copy link

twof commented Jul 25, 2017

Parts of the tutorial drop vocabulary on the students that they wouldn't have seen up to this point and I can see this being super confusing.

The following paragraph in particular is really bad. Even as an experienced developer, it's extremely jargon dense. Firebase needs to be explained in a way that would make sense to people who have never seen any of the terms used.

"The Firebase Realtime Database is a NoSQL database that can be used to store and retrieve data for our app. The Realtime Database is optimized for reading and writing quickly. Data is stored as a JSON object and the entire database can be thought of as a giant JSON tree. Data is written at specific locations defined by relative paths (associated keys) and can be retrieved using the same path. As data is added to the JSON tree, it becomes a node in the existing JSON structure."

Terms used:
NoSQL
database
JSON
JSON tree
relative path
associated key

Some of the above is copied from firebase documentation with little alteration:
https://firebase.google.com/docs/database/web/structure-data

This has been a general problem throughout playgrounds and tutorials. I'd suggest minimizing the usage of terms that would need defining for students of the expected experience level, and defining them directly before usage when they can't be avoided.

@ocwang
Copy link
Contributor

ocwang commented Jul 25, 2017

Good point! I'll take some time to re-write this so it's easier to understand.

Please feel free to point out any other paragraphs or sections you feel are confusing, jargon-dense, or introduce new concepts too quickly.

@ocwang
Copy link
Contributor

ocwang commented Apr 23, 2018

This tutorial, in general, assumes too much prior knowledge and is too feature-heavy. Would be good to do revisions that simplifies language, prunes unneeded features and slows down the pace of tutorial.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants