olivierjm/learn

self-paced way of learning the basics of javascript

Hi, I'm Olivier JM

Thanks for checking out my profile, I am a passionate software engineer who enjoys getting things done. I maintain a few opensource repositories here on Github in my freetime and I do contribute to other opensource projects from time to time, I enjoy mentoring junior devs and those getting started in their software development carrier, feel free to reach out.

• In my past life I worked at:
  • Bongohive as a contractor for the e-Granary Digital Library project
  • Hackersguild as a software engineer, later to senior and Javascript bootcamp instructor
  • Sparkman Center at UAB as a lead engineer consultant - Remote
  • The ZIG as a senior software engineer
  • DoubleGDP as a senior Ruby on Rails/Reactjs software engineer
  • Rural Coding Series as a volunteer lead instructor in different technology camps to teach rural kids programming
• I used to write articles on medium and at olivierjm.dev
• LinkedIn Profile https://linkedin.com/in/olivierjm
• You can reach me at [email protected]
• My resume can be found here

learn's Issues

add a readme

Add a proper readme file with:

• how the repo should be used
• what each directory does and how to use it
• guide for contributors

Add notes for Variables

There will be need for good notes and examples of variables and there should be a good check to make sure the person has understood variables.

We might need a markdown file in here but this #5 and this #6 will need to be resolved first.
Thoughts are very welcome

looking ahead

We could eventually make this into a GitHub organization and have other repo alike this one, like learn-py or learn-react then exercises we could apply for GitHub Classroom.

Accessiblity

How best can these resources be accessible, would it be possible to have a web version of doing the exercises ? 🤔🤔🤔

Add an issue template

Github has templates that we can use as templates for creating issues, this will include creating custom labels for things like labels, typos and other labels we think will be best to describe what kind of an issue it is.

Vanilla JS repo

@OlivierJM @leemlwando I was thinking like a beginner and came across one thing we didn't consider. Those who are new and just coming from HTML and CSS. They won't understand what NodeJS, Jest or NPM is. Instead of just letting them install those, some might give up and quit trying to install them. Why not create a branch or directory which just uses vanilla JS. It'll quite easy for them to learn, unlike just taking them direct to using node. Something you can think about.

Topic Structure

@OlivierJM i have had a challange writing about a topic in a single file. so i was thinking, we could create subfolders that would help us build small specif concepts on a particular topic.

Best way of learning

What is your suggestion on how best this repo can be used?
The aim is to make sure that people are learning from the sources they can trust,
I thought of adding test to check if they have done what is required, but how do we keep track of that ?

Should we allow them to fork, then make PRs of their work so that we can take a look at it and review it ? or we can have another way of submission? remember this has to be open to the public

add projects

@leemwando suggested that project based learning would be a good thing for newbies.

This is good, we can include a small project in each directory as part of exercises to help newbies understand the implementation of what they have just learned.

Homepage

It would be good to have a static page with how to use the provided resources beyond the readme, this can be hosted by GitHub pages or surge.sh.

Exercises

We need exercises in all topics, this will help in writing tests ahead of time.

I have written few tests because of this, the more I figure about the exercises the more tests I will write.
Remember the tests will always fail until the user has done the exercises.

Table of contents

As part of making this more clear to people who are new to both Github and Js itself, we will need to add table of contents in the main readme, we can following the structure order which can be linking back to the respective directories.

I will give an example of this later on today.

Contribution guide

We can use a standard contribution guide as the one mentioned here https://www.contributor-covenant.org

This will be very important and a good guide to those who want to contribute.

adding markdown files

Would it be a good option to have a markdown version of the equivalent javascript file in each directory?
This would help people read everything in a clean way even on GitHub without having to clone the repo, they won't be able to use the exercises but it would help just like notes

add notes for intro

This is the introduction of both the repo and the javascript

It should be very beginner friendly and attractive enough for new beginners to find it helpful.