https://github.com/binki/calvin-cs212-bingo
hplantin’s CS-212 Bingo project’s starting point (hopefully origin is public domain?).
https://github.com/binki/calvin-cs212-bingo
Last synced: 4 months ago
JSON representation
hplantin’s CS-212 Bingo project’s starting point (hopefully origin is public domain?).
- Host: GitHub
- URL: https://github.com/binki/calvin-cs212-bingo
- Owner: binki
- Created: 2015-11-14T20:48:56.000Z (over 10 years ago)
- Default Branch: master
- Last Pushed: 2016-01-26T05:18:28.000Z (over 10 years ago)
- Last Synced: 2025-02-28T12:43:08.273Z (over 1 year ago)
- Language: Rouge
- Size: 143 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Professor [@hplantin](https://github.com/hplantin) often teaches
[CS-212 at Calvin
College](http://cs.calvin.edu/curriculum/cs/212/hplantin/). His course
includes a number of [programming
projects](http://cs.calvin.edu/curriculum/cs/212/hplantin/syllabus.html)
(depending on the time of year, these may be obfuscated—check out the
raw markup). One such project, Project 4, Bingo, is
[described](http://cs.calvin.edu/curriculum/cs/212/hplantin/projects/P4-Bingo.pdf)
(a [backup is saved to this
repo](https://github.com/binki/calvin-cs212-bingo/blob/ee69ea4bbe0bb8498faf4c77472ec9225b2edce1/P4-Bingo.pdf))
and the student is given [seed
code](http://cs.calvin.edu/curriculum/cs/212/hplantin/projects/prog4.zip)
(a subset of this archive was imported on 2015-11-14 as [commit
51ba2eab8cfe89b434f089258001d8ad7ef57ddb](https://github.com/binki/calvin-cs212-bingo/commit/51ba2eab8cfe89b434f089258001d8ad7ef57ddb))
for implementing the project.
[This repository](https://github.com/binki/calvin-cs212-bingo)’s
purpose is to improve upon that seed code to make it more exemplary.
1. Follow the widely accepted best practices and conventions for the
languages and tools used. For example, a C# class would use
properties rather than getter methods.
2. Be as functional as it should be.
3. Follow guidelines on how to write good code disseminated by
professors. For example, students are encouraged to use Test
Driven Development.
Of course, improvements are expected to be sporadic and few. But if
you have any ideas, please open an issue, etc. Hopefully @hplantin
takes it over and uses the suggestions next semester…?