KWL Chart#
Working with your KWL Repo#
Important
The main branch should only contain material that has been reviewed and approved by the instructors.
Work on a specific branch for each activity you work on
when it is ready for review, create a PR from the item-specifc branch to
main.when it is approved, merge into main.
Minimum Rows#
# KWL Chart
<!-- replace the _ in the table or add new rows as needed -->
| Topic | Know | Want to Know | Learned |
| ------| ------- | ------ | ------- |
| Git | _ | _ | _ |
| GitHub | _ | _ | _ |
| Terminal | _ | _ | _ |
| IDE | _ | _ | _ |
| text editors | _ | _ | _ |
|file system | _ | _ |_ |
|bash | _ | _ | _ |
|abstraction | _ | _ | _ |
|programming languages | _ | _ | _ |
|git workflows | _ | _ | _ |
| git branches | _ | _ | _ |
| bash redirects | _ | _ | _ |
|number systems | _ | _ | _ |
| merge conflicts | _ | _ | _ |
| documentation | _ | _ | _ |
| templating | _ | _ | _ |
|bash scripting | _ | _ | _ |
| developer tools | _ | _ | _ |
| networking | _ | _ | _ |
|ssh | _ | _ | _ |
| ssh keys | _ | _ | _ |
|compiling | _ | _ | _ |
| linking | _ | _ | _ |
| building | _ | _ | _ |
| machine representation | _ | _ | _ |
| integers | _ | _ | _ |
| floating point | _ | _ | _ |
|logic gates | _ | _ | _ |
| ALU | _ | _ | _ |
| binary operations | _ | _ | _ |
| memory | _ | _ | _ |
| cache | _ | _ | _ |
| register | _ | _ | _ |
| clock | _ | _ | _ |
| Concurrency | _ | _ | _ |
Required Files#
This lists the files for reference, but mostly you can keep track by badge issue checklists.
| date | file | type |
|---|---|---|
| 2024-01-25 | brain.md | /_practice |
| 2024-01-30 | gitgui.md | /_practice |
| 2024-01-30 | gitgui.md | /_review |
| 2024-02-01 | branches.md | /_review |
| 2024-02-01 | terminal-vocab.md | /_prepare |
| 2024-02-01 | branches-forks.md | /_practice |
| 2024-02-06 | terminalpractice.md | /_practice |
| 2024-02-06 | terminal_review.md | /_review |
| 2024-02-06 | software.md | /_prepare |
| 2024-02-06 | terminal_organization_adv.md | /_practice |
| 2024-02-08 | commit-def.md | /_review |
| 2024-02-15 | docs_ecosystems.md | /_practice |
| 2024-02-20 | newlanguage.md | /_practice |
| 2024-02-22 | methods.md | /_practice |
| 2024-02-22 | methods.md | /_review |
| 2024-02-22 | software.md` about how that project adheres to and deviates from the unix philosophy. Be specific, using links to specific lines of code or specific sections in the documentation that support your claims. Provide at least one example of both adhering and deviating from the philosophy and three total examples (that is 2 examples for one side and one for the other). You can see what badge `software.md | /_practice |
| 2024-02-27 | favorite_git_workflow.md | /_review |
| 2024-02-27 | workflows.md | /_practice |
| 2024-02-27 | gitdef.md | /_prepare |
| 2024-02-27 | idethoughts.md | /_prepare |
| 2024-02-27 | workflows.md | /_practice |
| 2024-02-29 | gitislike.md | /_practice |
| 2024-02-29 | gitplumbingreview.md | /_review |
| 2024-02-29 | gitplumbingdetail.md | /_practice |
| 2024-03-05 | tagtypes.md | /_practice |
| 2024-03-05 | tagtypeexplore.md | /_review |
| 2024-03-07 | hash_num_prep.md | /_prepare |
| 2024-03-07 | gitcounts.md | /_review |
| 2024-03-07 | gitcounts_scenarios.md | /_practice |
| 2024-03-21 | newide.md | /_review |
| 2024-03-21 | settingssync.md | /_practice |
| 2024-03-21 | frequentide.md | /_practice |
| 2024-03-21 | newide.md | /_practice |
| 2024-03-26 | hpc.md | /_review |
| 2024-03-26 | hpc.md | /_practice |
| 2024-04-02 | octal.md | /_review |
| 2024-04-02 | octal.md | /_practice |
| 2024-04-04 | fractionalbinary.md | /_prepare |
| 2024-04-04 | floatexpt.md | /_practice |
| 2024-04-09 | operators.md | /_prepare |
| 2024-04-09 | bitwise.md | /_review |
| 2024-04-09 | addertypes.md | /_practice |
| 2024-04-09 | bitwise.md | /_practice |
| 2024-04-11 | systemsabstractions.md | /_practice |
| 2024-04-16 | threaded.md | /_review |
| 2024-04-16 | threaded.md | /_practice |
| 2024-04-16 | systeminteraction.md | /_practice |
| 2024-04-23 | dev_insights.md | /_prepare |