ENET 301 · SYLLABUS
The JTWAYNE CODE
Practice shared syntax, reusable tools, testing and responsible development.
Learning outcomes
- Document purpose and assumptions
- Check concrete results
- Describe scope and execution bounds
Module schedule
MODULE 1 · Study → Live lab → Practice
A shared coding contract
The JTWAYNE CODE is ENET’s shared-rules vision, not a second language or a finished interoperability system. Today: one statement per line, clear names, explicit blocks and a small allowlisted toolkit. Document the purpose and inputs of a program.
Assignment: Write a purpose comment and describe one program input.
MODULE 2 · Study → Live lab → Practice
Scope & predictable results
A function’s parameters are local to that call. Reuse pure functions for calculations instead of changing shared state. ENET functions are named calls, not first-class values.
Assignment: Add a function that triples its input without changing value.
MODULE 3 · Study → Live lab → Practice
Test a concrete result
Tests compare an actual result to a known expected value. ENET 0.1 has no assert command; express a check with if. Passing one example does not prove every input is correct.
Assignment: Add tests for square(0) and square(-3).
MODULE 4 · Study → Live lab → Practice
Safe, bounded programs
The classroom interpreter does not execute host JavaScript, access files or make network calls. Execution is bounded at 10,000 steps, with limits on source, output and nesting. Keep workloads small; these limits are not a full security audit.
Assignment: Try a smaller task count and explain why bounds matter.
Final project: A documented and tested ENET utility
Document and test a square utility using zero, positive and negative cases.
- Include a purpose comment
- Implement square without changing shared state
- Emit a PASS or FAIL line for each of three cases
Review correctness against the sample output, readability, comments and the documented limits of your prototype. Extend and test additional inputs after completing the sample.