haas:spring2021:sysprog:projects:sppx
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| haas:spring2021:sysprog:projects:sppx [2021/01/28 12:59] – created wedge | haas:spring2021:sysprog:projects:sppx [2021/01/28 13:24] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 15: | Line 15: | ||
| * discussing the chapter (in the class discord) | * discussing the chapter (in the class discord) | ||
| * experimenting/ | * experimenting/ | ||
| + | * identifying a UNIX tool or program you'd like to implement, making use of pertinent concepts (announce this in discord; where possible, I'd like each person to do a DIFFERENT thing) | ||
| * implementing some UNIX tool or program that incorporates content covered in the given chapter (and where applicable, builds upon previous chapters). While not exclusively limited to programming problems at the end of each chapter, they are a good starting point (clear with me any deviations from that pattern). | * implementing some UNIX tool or program that incorporates content covered in the given chapter (and where applicable, builds upon previous chapters). While not exclusively limited to programming problems at the end of each chapter, they are a good starting point (clear with me any deviations from that pattern). | ||
| + | * code should include statement of limitations (what functionality does your code implement, what, especially compared to standard system tools, does it not implement) | ||
| + | * no compiler notes, warnings, syntax errors, logical errors, or runtime errors (if there are compiler flags to issue, they should be clearly documented in the code/ | ||
| + | * if you are implementing a UNIX tool (even if with only a subset of functionality), | ||
| + | |||
| + | The overall aim is to enable you to challenge yourself, explore areas and concepts you are not familiar with, and grow as a programmer and problem solver. I don't want to see you just doing things the way you are familiar with (simply because you've always done them that way). | ||
| The outline of semester progress: | The outline of semester progress: | ||
| - | ^ week ^ project | + | ^ week ^ project |
| - | | 2 | spp0 | Chapters 1 and 2 | 13 | | + | | 2 | spp0 | Chapters 1 and 2 |
| - | | 3 | | + | | 3 | |
| - | | 4 | | + | | 4 | |
| - | | 5 | | + | | 5 | |
| - | | 6 | | + | | 6 | |
| - | | 7 | | + | | 7 | |
| - | | 8 | | + | | 8 | |
| - | | 9 | | + | | 9 | |
| - | | 10 | | + | | 10 | |
| - | | 11 | | + | | 11 | |
| - | | 12 | | + | | 12 | |
| | 13-15 | eoce | Chapters 13, 14, 15 | | | | 13-15 | eoce | Chapters 13, 14, 15 | | | ||
| + | |||
| + | < | ||
| + | TOTAL: | ||
| + | *:sppX:read indicated chapter in book [PTS/PTS] | ||
| + | *: | ||
| + | *: | ||
| + | *: | ||
| + | *: | ||
| + | *: | ||
| + | *: | ||
| + | *: | ||
| + | *:sppX:no warnings, compiler notes in code [PTS/PTS] | ||
| + | *:sppX:no syntax errors in code [PTS/PTS] | ||
| + | *:sppX:no logical errors in code [PTS/PTS] | ||
| + | *:sppX:no runtime errors in code [PTS/PTS] | ||
| + | *: | ||
| + | </ | ||
| + | |||
| + | Additionally: | ||
| + | * Solutions not abiding by spirit of project will be subject to a 25% overall deduction | ||
| + | * Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction | ||
| + | * Solutions not utilizing indentation to promote scope and clarity will be subject to a 25% overall deduction | ||
| + | * Solutions not organized and easy to read (assume a terminal at least 90 characters wide, 40 characters tall) are subject to a 25% overall deduction | ||
haas/spring2021/sysprog/projects/sppx.1611838744.txt.gz · Last modified: 2021/01/28 12:59 by wedge
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
