- shortcutfoo.com
- speedcoder.net
- speedtyper.dev
- typing.io
- how-to-type.com
- thepracticetest.com
- mltype
- Typer
VSC is the text editor you will use to write code at HYF. And it's way more than just a text editor! Take a look through these links to start learning all you can do with VSC. You don't need to understand everything right away, there will be more than enough time to practice:
- academind VSC tutorial
- shortcuts cheatsheet
- The Coding Train
- VSC Intro from VSC
- Tips for HTML/CSS/JS
- Are you using Windows?
- Writing Good READMEs
- awesome README templates
- README Driven Development
- relative vs. absolute paths
- The Coding Train
- Matt's Lectures and Tutorials
- Jesse Showalter
- Enough to be Dangerous
- CLI games:
- A huge cheat sheet
- Installing NPM and Node.js
- What is a
package.jsonfile? - Running NPM Scripts
- Learn to visualize what happens inside of Git with:
- learngitbranching + a Video Guide
- git-school
- ohmygit - a git game
- Git and GitHub for Poets (also talks about GitHub)
- merge-a-matic
- Git Katas
- git-it
- Understand how to use Atomic Commits
- rebasic
- lab.github.com/githubtraining
- Getting Started with GitHub
- Creating a GitHub Repository
- Connecting to GitHub with SSH
- Creating a local repo and push
- GitHub & VSCode
- and much more at hackyourfuture.github.io/study
- lab.github.com:
- The Net Ninja
- Building Software Together a student's guide to being a compassionate programmer - The technical parts are more advanced than what you're learning now, but all the rest is gold.
- Adding collaborators to a repository
- about code reviews
- requesting a code review
- prevent pushing to
main - Git Workflow for 2
- Pull Requests
- Git & GitHub for Poets
- The Net Ninja: 11
- linking PRs to Issues: reference 1, reference 2
- closing Issues using keywords
For now you can think of Continuous Integration is a fancy way to say "automatically check your code before you merge". Your project repositories will all have CI scripts to help maintain a quality and consistent code base.
hint: remember to enable GitHub Actions in your repository!
- Mozilla
- Brian Daigle codes of conduct and github walk-through: https://www.youtube.com/watch?v=c6b6B9oN4Vg
- Explained with Legos
- And with recipes
- Open Source vs. Closed Source
- Free/Libre vs. Open Source (think "free speech", not "free food")
To learn more about all things Open, check out the Open Knowledge Foundation and Open Knowledge Belgium.
The license attached to an Open Source project is not just a detail! Check out these links to learn more about the many licenses available:
- opensource.org
- choosealicense.com
- techsoup
- infoworld
- copyleft: what is this?, copyleft.org
- :) ErikMcClure/bad-licenses
The Code of Conduct in an Open Source project describes how contributors should treat each other. Open Source projects are about sharing and welcoming:
Contributor Guidelines are important to standardize coding practices and workflows for an Open Source project. You could think of it as describing how the code should be treated:
- mozillascience
- docs.github.com
- Templates
- Examples
- opensource.guide
- freecodecamp
- contribution-guide.org
- redhat
- better-programming
- Small contributions matter!
and finally ...
- HYF modules are often updated, recordings from past classes may not match this gitbook
- When sending a PR's with recording links please ...
- Indicate which class you were teaching
- Which week it was (if the module is more than 1 week)
- a helpful title or description
| Unmesh, Tamer, Samir & Bermarte