Skip to content

Latest commit

 

History

History
56 lines (34 loc) · 3.77 KB

README.md

File metadata and controls

56 lines (34 loc) · 3.77 KB
Raw

The Software Essentialist (Official Course Repo)

The official course repo for The Software Essentialist course students.

What is this

This is the course repo which houses all of the assignment start/end checkpoints, labs & exercises we'll use in the program.

How to get started?

  • Install Git
  • Install Node v16 or higher on your machine
  • Git clone or fork this repo

How to Get Setup & Complete Your Assignments & Exercises?

Check out the lessons in the "Exercises & Assignment Setup: How to Complete The Phases of Craftship Homework" module.

Relevant instructions for what to do after completing an assignment/exercise

1. Watch the demonstration modules

  • You'll eventually find demonstration modules for each of the assignments. You can use these to compare designs.

2. Get feedback on your work

  • First, get the assignment hashtag: Each assignment has a hashtag to identify it (ie: #palindromeChecker) uniquely. You can find this in the readme for each assignment and exercise. Grab this.
  • Create PR: Create a PR containing your commits for an assignment or exercise.
  • Finally, submit for feedback: Post to #course-chat for feedback from myself, the alumni, and the other community members.

Here's an example:

"I just finished #palindromeChecker here. Would love some feedback on my commits. Start (<insert link to first commit>), end (<insert link to end commit>). Cheers!

3. Review a submission

  • Get to the Discord: Go into the #course-chat channel.
  • Find other submissions: Use the assignment hashtag name to find other submissions. While in the channel, you can use CMD/CTRL + F to bring up the finder in Discord. Type in the hashtag to find other submissions. Find one and pull it up.
  • Two things they did well: Read through their commits, from the starting one and look for 2 things you think they did well. Leave a comments to start a discussion.
  • Two things you found interesting or might do differently & why: Look for 2 parts of their design you either found interesting and start a discussion or comment how you might have implemented things differently.

4. Design it twice (do it again)

  • The last thing you can do is something John Ousterhout recommends, that I highly agree with: design it twice. Do it again. You've likely learned things you'd do differently. Drill it again. Programming is very much a tactile & pattern-matching activity. You just need reference experiences.

How to deal with snags

  • If you get stuck or run into any issues, use the #course-chat channel in Discord to discuss so we can refine things and make 'em smoother.