Upcoming Sessions
Past Sessions
3 Series
86 Sessions
CS
Computer Science · session
Computer Science
[3 of n] TITLE. How to Program --- for people who think they already can.
SCHEDULE. Monday, Wednesday, Friday at 9:00 PM EDT, for multiple weeks. Attendance limited to people who attended prior sessions in the sequence.
EXPECTATION. That you will attend every session in the sequence, especially at the beginning, with occasional excused absences later on. That you will actively contribute to the sessions by speaking up, proposing coding solutions, and discussing the solutions of others.
PREREQUISITE. Knowledge in any programming language of the concepts of variable, expression, assignment statement, conditional statement, loop (while and for), 1- and 2-dimensional array, procedure/function/method.
GOAL. Learning the skill of programming. The subject of the tutorial is the programming process, not any particular programming language. Programming is codified into 80+ rules that you will learn, and practice using as we code communally in class. One of those rules is “Code with deliberation”, and you will be expected to do so by announcing for every line of code you suggest why it is a logical next thing to write according to rule #i. The skills learned are applicable for (essentially) every programming language, e.g., Java, Python, C/C++, JavaScript, FORTRAN, BASIC, etc.
SL
TT
Tim T
2
Session ended.
CS
Computer Science · session
Computer Science
[2 of n] TITLE. How to Program --- for people who think they already can.
SCHEDULE. Monday, Wednesday, Friday at 9:00 PM EDT, for multiple weeks. [If you missed Session "1 of n" on 6/23 you will are welcome to join this session "2 of n" provided you request and schedule a makeup beforehand.]
EXPECTATION. That you will attend every session in the sequence, especially at the beginning, with occasional excused absences later on. That you will actively contribute to the sessions by speaking up, proposing coding solutions, and discussing the solutions of others.
PREREQUISITE. Knowledge in any programming language of the concepts of variable, expression, assignment statement, conditional statement, loop (while and for), 1- and 2-dimensional array, procedure/function/method.
GOAL. Learning the skill of programming. The subject of the tutorial is the programming process, not any particular programming language. Programming is codified into 80+ rules that you will learn, and practice using as we code communally in class. One of those rules is “Code with deliberation”, and you will be expected to do so by announcing for every line of code you suggest why it is a logical next thing to write according to rule #i. The skills learned are applicable for (essentially) every programming language, e.g., Java, Python, C/C++, JavaScript, FORTRAN, BASIC, etc.
SL
TT
Tim T
14
Session ended.
CS
Computer Science · session
Computer Science
{MAKEUP FOR ANYONE WHO MISSED THE 6/23} [1 of n] TITLE. How to Program --- for people who think they already can.
SCHEDULE. Monday, Wednesday, Friday at 9:00 PM EDT, for multiple weeks.
EXPECTATION. That you will attend every session in the sequence, especially at the beginning, with occasional excused absences later on. That you will actively contribute to the sessions by speaking up, proposing coding solutions, and discussing the solutions of others.
PREREQUISITE. Knowledge in any programming language of the concepts of variable, expression, assignment statement, conditional statement, loop (while and for), 1- and 2-dimensional array, procedure/function/method.
GOAL. Learning the skill of programming. The subject of the tutorial is the programming process, not any particular programming language. Programming is codified into 80+ rules that you will learn, and practice using as we code communally in class. One of those rules is “Code with deliberation”, and you will be expected to do so by announcing for every line of code you suggest why it is a logical next thing to write according to rule #i. The skills learned are applicable for (essentially) every programming language, e.g., Java, Python, C/C++, JavaScript, FORTRAN, BASIC, etc.
SL
TT
Tim T
3
Session ended.
CS
Computer Science · session
Computer Science
[1 of n] TITLE. How to Program --- for people who think they already can.
SCHEDULE. Monday, Wednesday, Friday at 9:00 PM EDT, for multiple weeks.
EXPECTATION. That you will attend every session in the sequence, especially at the beginning, with occasional excused absences later on. That you will actively contribute to the sessions by speaking up, proposing coding solutions, and discussing the solutions of others.
PREREQUISITE. Knowledge in any programming language of the concepts of variable, expression, assignment statement, conditional statement, loop (while and for), 1- and 2-dimensional array, procedure/function/method.
GOAL. Learning the skill of programming. The subject of the tutorial is the programming process, not any particular programming language. Programming is codified into 80+ rules that you will learn, and practice using as we code communally in class. One of those rules is “Code with deliberation”, and you will be expected to do so by announcing for every line of code you suggest why it is a logical next thing to write according to rule #i. The skills learned are applicable for (essentially) every programming language, e.g., Java, Python, C/C++, JavaScript, FORTRAN, BASIC, etc.
SL
TT
Tim T
7
Session ended.
CS
Computer Science · session
Computer Science
[Organizational]. {Saturday, 6/19, 10:30PM EDT (for India); Sunday, 6/20, 12 noon (for USA)}
The SHW Q3 roadmap “deprioritizes CS” (see footer). It remains to be seen what this means for CS going forward. I am hosting this Session on the assumption that I will offer CS sessions and cohorts this summer. My goal in this Session will be to assess the nature of individual Learner interest and availability.
In support of the discussion, I have prepared two documents: one lists CS Topics (https://drive.google.com/file/d/1iMka7ZxrDr2eSouHr70IJCZIQstrYUmW/view?usp=sharing), and the other lists possible Session sequences that could draw on those topics (https://drive.google.com/file/d/1iMka7ZxrDr2eSouHr70IJCZIQstrYUmW/view?usp=sharing). Both documents link to slide decks that serve as "reference implementations" for Session material.
The Session will be structured around a discussion of what Programming is all about, so that the Session can serve as an overview of the field. From there, I will attempt to learn where Learner interests lie, so that summer offerings can best be planned and scheduled.
SL
TT
Tim T
1
Session ended.
CS
Computer Science · session
Computer Science
[Organizational]. {Saturday, 6/19, 10:30PM EDT (for India); Sunday, 6/20, 12 noon (for USA)}
The SHW Q3 roadmap “deprioritizes CS” (see footer). It remains to be seen what this means for CS going forward. I am hosting this Session on the assumption that I will offer CS sessions and cohorts this summer. My goal in this Session will be to assess the nature of individual Learner interest and availability.
In support of the discussion, I have prepared two documents: one lists CS Topics (https://drive.google.com/file/d/1iMka7ZxrDr2eSouHr70IJCZIQstrYUmW/view?usp=sharing), and the other lists possible Session sequences that could draw on those topics (https://drive.google.com/file/d/1iMka7ZxrDr2eSouHr70IJCZIQstrYUmW/view?usp=sharing). Both documents link to slide decks that serve as "reference implementations" for Session material.
The Session will be structured around a discussion of what Programming is all about, so that the Session can serve as an overview of the field. From there, I will attempt to learn where Learner interests lie, so that summer offerings can best be planned and scheduled.
SL
TT
Tim T
2
Session ended.
CS
Computer Science · session
Computer Science
There is much interest in computer programming, but did you ever wonder about the LIMITS of computing? Can EVERYTHNG be computed? If not, what is SOMETHING that can’t be computed? Is there a breakthrough around the corner that will change what can and can’t be computed? And for that matter, what does it even mean to COMPUTE something? Would you be surprised to learn that in a rather precise mathematical sense, most things are UNCOMPUTABLE? And what about the SOUL?
Come and find out answers to such trifles.
SL
TT
Tim T
1
Session ended.
E
Enrichment · session
Enrichment
DIVIDE AND CONQUER is a general-purpose problem-solving technique said to derive from Julius Caesar’s approach in 58 BC to defeating Gaul. Given a problem P, how do you solve it?
I will present the technique in some generality, and will illustrate it for problems P such as “Plan a road trip across country”, “Hammer a nail”, and “Write a computer program to do x”. No knowledge of driving, carpentry, or computer programming is required.
In Computer Science, Divide and Conquer has been carefully studied for programming, and I will bring that precision to my description of the technique for general problem solving. Divide and Conquer is said by some to be one of the fundamental tools in the toolkit of Life.
Cross-listed with Computer Science: Stepwise Refinement (https://schoolhouse.world/session/4169). Please register for THIS Session, and not THAT Session.
SL
TT
Tim T
6
Session ended.
CS
Computer Science · session
Computer Science
STEPWISE REFINEMENT. [Cross listed with https://schoolhouse.world/session/4170. Please register for THAT Session, not THIS Session.]
I have been surprised by the number of people who teach or study programming, yet are not familiar with the elementary but fundamental technique called “Programming by Stepwise Refinement”. This session aims to remedy the situation for Tutors and Learners, alike.
There is so little content in this subject that is exclusive to programming that I have cross-listed the Session with Enrichment/General Problem Solving (https://schoolhouse.world/session/4170). Please register for THAT Session rather than THIS Session.
SL
TT
Tim T
1
Session ended.
E
Enrichment · session
Enrichment
SESSION 17B (Thursday at 6:00 PM EDT; repeated Thursday, at 7:00 PM EDT)
TOPIC: Collaborative team effort to create/curate the new/soon-to-be-released Unofficial Schoolhouse Wiki.
THIS SESSION: Status update, followed by working meeting to write pages on software Tools.
PREP and FURTHER COMMUNICATION: Join and see #test-wiki for any further communications.
SL
TT
Tim T
5
Session ended.
E
Enrichment · session
Enrichment
SESSION 17B (Thursday at 6:00 PM EDT; repeated Thursday, at 7:00 PM EDT)
TOPIC: Collaborative team effort to create/curate the new/soon-to-be-released Unofficial Schoolhouse Wiki.
THIS SESSION: Status update, followed by working meeting to write pages on software Tools.
PREP and FURTHER COMMUNICATION: Join and see #test-wiki for any further communications.
SL
TT
Tim T
0
Session ended.
E
Enrichment · session
Enrichment
SESSION 16A (Sunday at 5:00 PM EDT; repeated on Monday, at 8:00 PM EDT)
TOPIC: Collaborative team effort to create/curate the new/soon-to-be-released Unofficial Schoolhouse Wiki.
THIS SESSION: It is time to document your favorite tutoring TOOLS. I plan to pick one or more such tools that you feel are important to describe in the Wiki, and work collaboratively to do so. Alternatively, based on the interest of attendees, we may pick a tool that we all want to learn (as opposed to already use), but that seems important to know and publicize.
PREP and FURTHER COMMUNICATION: Join and see #test-wiki for any further communications.
SL
TT
Tim T
1
Session ended.
E
Enrichment · session
Enrichment
SESSION 16A (Sunday at 5:00 PM EDT; repeated on Monday, at 8:00 PM EDT)
TOPIC: Collaborative team effort to create/curate the new/soon-to-be-released Unofficial Schoolhouse Wiki.
THIS SESSION: It is time to document your favorite tutoring TOOLS. I plan to pick one or more such tools that you feel are important to describe in the Wiki, and work collaboratively to do so. Alternatively, based on the interest of attendees, we may pick a tool that we all want to learn (as opposed to already use), but that seems important to know and publicize.
PREP and FURTHER COMMUNICATION: Join and see #test-wiki for any further communications.
SL
TT
Tim T
0
Session ended.
E
Enrichment · session
Enrichment
This will be a meeting of Tutors who are using (or intending to use) Enrichment as a vehicle for conducting a mini-series on some subject of their own interest. Because the curriculum of such a series is not KA-canned, but is of their own making, a mechanism is needed to describe the series (in greater detail than can be fit in a tiny little Description box), and advertise it to the Community.
We will brainstorm about the role of the Wiki, and learn details about its use for this purpose.
SL
TT
Tim T
2
Session ended.
E
Enrichment · session
Enrichment
SESSION 15B (Thursday at 6:00 PM EDT; repeated Thursday, at 7:00 PM EDT)
TOPIC: Collaborative team effort to create/curate the new/soon-to-be-released Unofficial Schoolhouse Wiki.
THIS SESSION: Progress report. Then a guided work session on FAQ, Technologies, Best Practices.
PREP and FURTHER COMMUNICATION: See #test-wiki for any further communications.
SL
TT
Tim T
0
Session ended.
E
Enrichment · session
Enrichment
SESSION 15B (Thursday at 6:00 PM EDT; repeated Thursday, at 7:00 PM EDT)
TOPIC: Collaborative team effort to create/curate the new/soon-to-be-released Unofficial Schoolhouse Wiki.
THIS SESSION: Progress report. Then a guided work session on FAQ, Technologies, Best Practices.
PREP and FURTHER COMMUNICATION: See #test-wiki for any further communications.
SL
TT
Tim T
0
Session ended.
E
Enrichment · session
Enrichment
Test session. Please ignore.
SL
TT
Tim T
1
Session ended.
E
Enrichment · session
Enrichment
SESSION 14A (Sunday at 5:00 PM EDT; repeated on Monday, at 8:00 PM EDT)
TOPIC: Collaborative team effort to create/curate the new/soon-to-be-released Unofficial Schoolhouse Wiki.
THIS SESSION: Progress report. Then a guided work session.
PREP and FURTHER COMMUNICATION: See #test-wiki for any further communications.
SL
TT
Tim T
1
Session ended.
E
Enrichment · session
Enrichment
SESSION 14A (Sunday at 5:00 PM EDT; repeated on Monday, at 8:00 PM EDT)
TOPIC: Collaborative team effort to create/curate the new/soon-to-be-released Unofficial Schoolhouse Wiki.
THIS SESSION: Progress report. Then a guided work session.
PREP and FURTHER COMMUNICATION: See #test-wiki for any further communications.
SL
TT
Tim T
0
Session ended.
E
Enrichment · session
Enrichment
SESSION 13A (Thursday at 6:00 PM EDT; repeated Thursday, at 7:00 PM EDT)
TOPIC: Collaborative team effort to create/curate the new/soon-to-be-released Unofficial Schoolhouse Wiki.
THIS SESSION: Discussion: (a) Technology/Best Practices pages, e.g., Kahoot! (b) Continuing massive FAQ effort!
PREP and FURTHER COMMUNICATION: See #test-wiki for any further communications.
Registration
SL
TT
Tim T
0
Session ended.
E
Enrichment · session
Enrichment
SESSION 13A (Thursday at 6:00 PM EDT; repeated Thursday, at 7:00 PM EDT)
TOPIC: Collaborative team effort to create/curate the new/soon-to-be-released Unofficial Schoolhouse Wiki.
THIS SESSION: Discussion: (a) Technology/Best Practices pages, e.g., Kahoot! (b) Continuing massive FAQ effort!
PREP and FURTHER COMMUNICATION: See #test-wiki for any further communications.
SL
TT
Tim T
0
Session ended.
E
Enrichment · session
Enrichment
SESSION 12A (Sunday at 5:00 PM EDT; repeated on Monday, at 8:00 PM EDT)
TOPIC: Collaborative team effort to create/curate the new/soon-to-be-released Unofficial Schoolhouse Wiki.
THIS SESSION: Discussion: (a) Technology pages, e.g., Kahoot! (b) Launching a massive FAQ effort!
PREP and FURTHER COMMUNICATION: See #test-wiki for any further communications.
SL
TT
Tim T
0
Session ended.
E
Enrichment · session
Enrichment
SESSION 12A (Sunday at 5:00 PM EDT; repeated on Monday, at 8:00 PM EDT)
TOPIC: Collaborative team effort to create/curate the new/soon-to-be-released Unofficial Schoolhouse Wiki.
THIS SESSION: Discussion: (a) Technology pages, e.g., Kahoot! (b) Launching a massive FAQ effort!
PREP and FURTHER COMMUNICATION: See #test-wiki for any further communications.
SL
TT
Tim T
0
Session ended.
E
Enrichment · session
Enrichment
SESSION 11B (Thursday at 6:00 PM EDT; repeated Thursday, at 7:00 PM EDT)
TOPIC: @Ada M asked, and @Mariah O reposted: “How do we systematically encourage Tutors to reflect on their Sessions, and to improve, both by themselves and with each-other?”
Wiki section Best Practices (https://shw.teitelbaum.us/doku.php?id=best_practices) is designed to do just that --- to encourage mindfulness about one’s choices in tutoring, and to encourage a relentless will for reflection and self-improvement.
START by coming to this Session, critiquing the Wiki section, and contributing to making it better.
SL
TT
Tim T
0
Session ended.