Final Presentation, Oral Code Defense & Official WIL Certification
Deliver your 15-minute live technical walkthrough and oral code defense before the Sputnik Devs Engineering Board and claim your cryptographically signed WIL Certificate & Transcript.
Engineering Implementation Tasks
Branch: feat/day-19Complete your Day 19 logbook summary and final self-reflection in `docs/DAILY_CADENCE_AND_LOGBOOK.md`.
Walk through your merged Pull Requests, Swagger endpoints, and test suite.
Complete the 4-Pillar Oral Code Defense with your Pod Coordinator.
Download your stamped University WIL Logbook PDF and Official Verifiable Certificate.
Core Sandbox Scope (RES-CORE — Final Capstone Defense): Finalize 'docs/DAILY_CADENCE_AND_LOGBOOK.md' and walk through your merged PRs, Swagger endpoints, Dockerfile, and 'SputnikResidence.Tests' suite.
Core student accommodation occupancy, room capacity guardrails, maintenance ticket lifecycle, comment workflows, xUnit verification, and Docker production readiness.
SputnikDevs.Residence.SandboxApi & SputnikResidence.TestsRoom, Student, MaintenanceTicket, TicketCommentSputnikDevs.Residence.SandboxApi, SputnikResidence.Tests & docs/DAILY_CADENCE_AND_LOGBOOK.mdfeat/day-19 (main stays clean)Final PR merged, 152 Notional Hours verified, and Official WIL Certificate & Academic Transcript issued.
☁️ Cloud Devcontainer Active (4GB RAM Laptop → GitHub Codespaces 16GB Cloud VM) • ⚡ Async Defense Window Enabled
Zero Hardware & Zero Billing Rule: Always launch your 2-core Codespace on your personal fork (github.com/<your-username>/sputnikdevs-residence-sandbox)—never on the Sputnik-Devs-Pty-Ltd org repo—so it runs 100% on your free 120 personal core-hours/month without local 4GB RAM strain or Organization billing blocks.
Live End-to-End Test Mode (GitHub PR Auto-Sync + 3-Min Spoken/Written Code Defense)
Use this Specimen account to test Step 1 (Auto-Sync PR from GitHub) and Step 2 (3-Minute Timed Voice/Written Code Defense) without touching Brian Mkandla's live cohort profile.
Sync & Log Day 19 Pull Request from GitHub
Already pushed your code and opened a Pull Request on GitHub? Click Auto-Sync Latest PR from GitHub to pull your PR link, changed files, commit summary, and next sprint milestone automatically—no double typing required.
3-Minute Timed & Webcam-Proctored Technical Code Defense
Your camera opens in a lightweight Picture-in-Picture window while you defend your Day 19 Pull Request diff by speaking into your microphone (🎙️ Speak Answer) or typing in your own words. Three low-bandwidth verification snapshots (~15KB each at Start, Mid-Defense, and Final Submit), clipboard-paste blocks, and tab switches are logged for Kenneth Takudzwa Katsande & Takudzwa Mupanesure (@Takudzwamz).
Interactive Code Architecture Self-Audit Simulator
Use this optional 60-second practice deck while writing your code to make sure you can trace your execution path, edge cases, and architectural trade-offs before starting your 3-Minute Timed Code Defense above.
Core Concept Drill: Final Presentation, Oral Code Defense & Official WIL Certification
Walk us through the complete lifecycle of a `POST /api/v1/tickets/{id}/comments` request in your API from HTTP request to PostgreSQL persistence.
Client Request -> CORS & ModelState Pipeline (Program.cs)
-> Controller Guardrails & Enum/Entity Validation (TicketsController.cs)
-> EF Core Change Tracking / AsNoTracking & PostgreSQL 16 (SandboxDbContext.cs)
-> Automated Unit & Integration Verification (SputnikResidence.Tests)
Why This Pattern Matters in Production
What was the most important engineering lesson you learned moving from university coursework to daily PR-reviewed software engineering?
Client Request -> CORS & ModelState Pipeline (Program.cs)
-> Controller Guardrails & Enum/Entity Validation (TicketsController.cs)
-> EF Core Change Tracking / AsNoTracking & PostgreSQL 16 (SandboxDbContext.cs)
-> Automated Unit & Integration Verification (SputnikResidence.Tests)
Live Requirement Change & Refactoring Drill
In your Final Exit Defense, if we ask you to compare how you validated and persisted data on Day 03 (Domain Models) vs Day 12 (Comments & Roles) vs Day 16 (Integration Tests), how do the layers work together to prevent invalid state from ever reaching PostgreSQL?
Client Request -> CORS & ModelState Pipeline (Program.cs)
-> Controller Guardrails & Enum/Entity Validation (TicketsController.cs)
-> EF Core Change Tracking / AsNoTracking & PostgreSQL 16 (SandboxDbContext.cs)
-> Automated Unit & Integration Verification (SputnikResidence.Tests)
Proving Happy Path & Negative/Boundary Cases
If you were onboarding the next cohort of WIL engineers onto `sputnikdevs-residence-sandbox` tomorrow, which single piece of code or test in your repository would you show them first as the gold standard, and why?
Client Request -> CORS & ModelState Pipeline (Program.cs)
-> Controller Guardrails & Enum/Entity Validation (TicketsController.cs)
-> EF Core Change Tracking / AsNoTracking & PostgreSQL 16 (SandboxDbContext.cs)
-> Automated Unit & Integration Verification (SputnikResidence.Tests)
Check off each verification gate below as you inspect your own Pull Request diff:
Verified Pull Request & Standup Logbook (6 Entries)
Benchmarked materialized views (v_nsfas_arrears_aging) and composite B-Tree indexes with EXPLAIN ANALYZE.
Completed Docker multi-stage Dockerfile, health checks, and 84% xUnit code coverage.
Passed Day 9 Mid-Sprint Architecture Review and added X-Execution-Time-Ms telemetry.
Optimized GET /api/residents with AsNoTracking() and pagination metadata.
Merged PR #1 with green CI build and verified PostgreSQL 16 container health checks.
Completed onboarding orientation, configured GitHub Codespaces & Docker PostgreSQL 16 sandbox.
| Day | Engineering Summary & PR | Sign-Off & Reviewer | Defense Score | Hours | Verification |
|---|---|---|---|---|---|
|
D19
28 Oct
|
Benchmarked materialized views (v_nsfas_arrears_aging) and composite B-Tree indexes with EXPLAIN ANALYZE.
|
Kenneth Takudzwa Katsande & Takudzwa Mupanesure
Lead: Takudzwa Mupanesure
|
4.0 / 4.0 | 8 h | Dual-Verified ✓✓ |
|
D19
20 Oct
|
Completed Docker multi-stage Dockerfile, health checks, and 84% xUnit code coverage.
|
Kenneth Takudzwa Katsande & Takudzwa Mupanesure
Lead: Takudzwa Mupanesure
|
4.0 / 4.0 | 8 h | Dual-Verified ✓✓ |
|
D10
13 Oct
|
Passed Day 9 Mid-Sprint Architecture Review and added X-Execution-Time-Ms telemetry.
|
Sipho Mokoena
Lead: Takudzwa Mupanesure
|
4.0 / 4.0 | 8 h | Dual-Verified ✓✓ |
|
D05
06 Oct
|
Optimized GET /api/residents with AsNoTracking() and pagination metadata.
|
Brian Ndlovu
Lead: Takudzwa Mupanesure
|
4.0 / 4.0 | 8 h | Dual-Verified ✓✓ |
|
D02
03 Oct
|
Merged PR #1 with green CI build and verified PostgreSQL 16 container health checks.
|
Lerato Dlamini
Lead: Takudzwa Mupanesure
|
4.0 / 4.0 | 8 h | Dual-Verified ✓✓ |
|
D01
02 Oct
|
Completed onboarding orientation, configured GitHub Codespaces & Docker PostgreSQL 16 sandbox.
|
Sipho Mokoena
Lead: Takudzwa Mupanesure
|
4.0 / 4.0 | 8 h | Dual-Verified ✓✓ |
🛠️ Hardware, Connectivity & Hardship Log (Zero-Barrier WIL)
Working on a 4GB RAM laptop, experiencing Eskom loadshedding, or facing mobile data constraints? Log it below and we immediately provision a cloud or async engineering workaround (such as a 16GB RAM GitHub Codespaces Cloud Devcontainer) so your sprint never stops.
Reported Issue: Local Visual Studio & Docker Desktop freeze when running .NET 10 SDK alongside PostgreSQL 16 container on 4GB RAM.
Reported Issue: Scheduled power outage during morning 09:00 SAST window; inverter battery lasts 90 minutes.