Schedule

Day 1

July 16, 2026

09:30

Settle in and configure screen sharing on the 'smart' TV 😬
10:00
Opening remarks
Day 1 · Session 1

Session 1 notes
Attendees and Context

Four-day working session to develop NCERT computer science textbooks for grades 11 and 12
Team: mix of IIT faculty, school teachers, industry practitioners, and curriculum developers

Curriculum Scope and Design Principles

Core question: what should a student know after two years of CS, independent of market/job value?
70/30 split agreed after comparing CS and AI curricula:

70% core CS concepts: programming principles, complexity, basic data structures, algorithms
30% new and contemporary topics

Computational thinking identified as a major emphasis that was lost in recent drafts; needs restoration
Two flavors of computational thinking to balance:

Greek/algorithmic: abstract a real-world problem into a mathematical model, solve with defined steps
Data-centric (Indian tradition): observe data, find patterns, iterate toward conclusions (underpins AI/ML)

Procedural and data-centric approaches are not mutually exclusive; both need representation

Programming Pedagogy: The Core Debate

Target audience is highly heterogeneous: some students arrive with coding experience, many have none
Current failure mode: students memorize code for exams rather than understanding it
Root cause: syntax and cryptic compiler errors overwhelm beginners before they can think about problems
Desired sequence: problem articulation → solution design → only then, code implementation
Key principle: thinking must precede execution, not the reverse

Block-Based Editing as a Bridge

Block-based visual programming (Scratch/Snap) proposed as the bridge between thinking and writing code
Rationale: removes syntax friction so students can focus on problem-solving logic
Precedent: Harvard CS50 opens with Scratch for one week at undergraduate level
Snap (Berkeley) preferred over Scratch: more features, closer to real language constructs, smoother transition to Python
Sriram and Viraj (now resigned) were strong advocates; their exit has left the decision somewhat fluid
Risk flagged: teachers and students may perceive block-based coding as “dumbing down”

Reframe needed: this is not easier programming, it is a different entry point for thinking
The chapter itself must convey this through its structure, not through two pages of theory

Snap vs. Python: Current State

Decision on Snap vs. Python-first is still open following departure of key advocates
Next step: review the programming learning path (how students begin, grow, and deepen)
Anup joining to share flowchart experience as one alternative/complement to block-based editing
Other options on the table: pseudocode, English-language description, flowcharts, unplugged activities
Goal: whichever path is chosen, more students should choose CS by interest, not just salary prospects

Writing the Textbook: Key Challenges

Chapter structure must implicitly convey pedagogical motivation, not state it explicitly
Start each lesson with a problem; find a solution; then introduce the tool or syntax
Avoid leading with interface instructions (e.g., “here is where to find the block in Scratch”)
Examples should move beyond classical formula-substitution problems toward open-ended, data-rich scenarios

Concern raised: students coming from 10th standard may struggle with ill-defined, multi-solution problems
Counterpoint: this can be scaffolded carefully; school teachers’ input is essential here

Collective wisdom of the group is the intended mechanism; no single person covers all aspects

Next Steps

Reach out to Berkeley Snap team for support
Explore whether they can provide resources or collaboration for curriculum integration.

Anup to present flowchart experience to the group
Share findings on pitfalls and benefits to inform the decision on flowchart-based exposition.

Finalize programming learning path decision (Snap, Python, or hybrid)
Review options as a group over the four days; resolve what was left fluid after Sriram and Biraj's departure.

Develop school-level examples for the data-centric computational thinking strand
School teachers to contribute examples that are accessible to students coming from 10th standard.
10:30

Review and recap of what we have so far
11:00

Coffee at Nescafe
11:30

Anup's presentation on flowcharts

Join Zoom
12:30

Discussion: finalizing the plan ahead
13:00

Lunch back at the guest house
14:30

Small-group discussions / breakout rooms
16:00

Coffee at Nescafe
16:30

Small-group discussions continue
18:00

Consolidate, review, and plan for tomorrow

Day 2

July 17, 2026

To be announced

Schedule to be confirmed

Day 3

July 18, 2026

To be announced

Schedule to be confirmed

Day 4

July 19, 2026

To be announced

Schedule to be confirmed

Enter the workshop password

Schedule

Day 1

Settle in and configure screen sharing on the 'smart' TV 😬

Opening remarks

Review and recap of what we have so far

Coffee at Nescafe

Anup's presentation on flowcharts

Discussion: finalizing the plan ahead

Lunch back at the guest house

Small-group discussions / breakout rooms

Coffee at Nescafe

Small-group discussions continue

Consolidate, review, and plan for tomorrow

Day 2

Schedule to be confirmed

Day 3

Schedule to be confirmed

Day 4

Schedule to be confirmed