You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we could create more coding "usable", standalone coding examples that students can clone and play around with. We can choose to use any number of them during our recitations to supplement our "lecturing" (i.e. reading off of notes), rather than talk about them abstractly as snippets embedded within our long-form notes.
Another side discussion is about whether or not we want to include Makefiles with those notes – on one hand, I think it's at least a common courtesy, and we should hold ourselves to our own standards as far as distributing code with Makefiles (plus, we can include cool alternative compilation rules, like make debug or make alternate which can define different pre-processor variables), but on the other hand, since this stuff is public, I'm wondering if security/giving away the answers is a problem.
What are your thoughts?
The text was updated successfully, but these errors were encountered:
I think we could create more coding "usable", standalone coding examples that students can clone and play around with. We can choose to use any number of them during our recitations to supplement our "lecturing" (i.e. reading off of notes), rather than talk about them abstractly as snippets embedded within our long-form notes.
Another side discussion is about whether or not we want to include Makefiles with those notes – on one hand, I think it's at least a common courtesy, and we should hold ourselves to our own standards as far as distributing code with Makefiles (plus, we can include cool alternative compilation rules, like
make debug
ormake alternate
which can define different pre-processor variables), but on the other hand, since this stuff is public, I'm wondering if security/giving away the answers is a problem.What are your thoughts?
The text was updated successfully, but these errors were encountered: