Student Handbook & Learning Model

Welcome to Tech Minds Academy — Abuja's hands-on engineering and digital technology school. Whether you are attending classes in person at our physical campus (G5 Plaza, Before AEDC Office, Sabon-Gari Road, Bwari, Abuja, Nigeria) or joining a Live Online Cohort from anywhere in Nigeria or across the globe, you are stepping into a disciplined, builder-focused engineering community.

This handbook explains how we teach, how your work is evaluated, what we expect from every student each week, and how to get the highest return from your time at Tech Minds Academy.

Before Your First Day of Class

Complete these three onboarding steps before Week 1 begins:

1. Read this Student Handbook in full so you understand our weekly rhythm and grading standards.
2. Configure your computer using our Developer Environment Setup Guide.
3. Create your GitHub account and test your terminal setup with the Git & GitHub Student Workflow.

---

Campus & Cohort Formats

Tech Minds Academy operates two synchronized learning formats built on the exact same 2026 Curricula, project briefs, and evaluation standards:

Feature	Abuja Physical Campus (Bwari)	Live Online Cohort
Location	G5 Plaza (Before AEDC Office), Sabon-Gari Road, Bwari, Abuja	Interactive live video classrooms + cloud lab workspaces
Instruction	3 mentor-led classes per week + open studio lab access	3 live instructor-led sessions per week + recorded replays
Power & Workspace	Backup power supply, collaborative desks, local mentor support	Offline-resilient tooling setup + asynchronous mentor support
Code Reviews	In-person pair debugging + GitHub Pull Request feedback	Screen-share debugging + GitHub Pull Request feedback
Demo Day	Live presentation at Bwari Campus (streamed to guests)	Live virtual stage presentation to mentors & hiring guests

Official Contact & Student Support Desk:

• Website: techmindsacademy.org
• Email: info@techmindsacademy.org
• Phone / WhatsApp Support: (+234) 814 732 8332
• Campus Hours: Monday – Saturday, 9:00 AM – 5:00 PM WAT

---

How We Learn: The Project-First Philosophy

At the heart of every Tech Minds Academy course is one non-negotiable conviction:

"Reading about code without writing it creates an illusion of understanding."

Watching ten hours of tutorials feels productive, yet the moment you face a blank file in VS Code, your mind goes blank. Real engineering fluency comes only from deliberate practice — typing every line yourself, breaking things, reading error messages, consulting documentation, and shipping working deliverables every single week.

Our Three-Pillar Instructional Model

1. 3-Days-Per-Week Mentor-Led Sessions Each week features three structured, interactive classes where your instructor introduces core mental models, writes live code from a blank editor (no pre-baked slide reading), and walks through real-world edge cases.
2. Guided Studio Lab Hours Between and after classes, studio lab hours give you dedicated time to tackle exercises while mentors circulate to unblock bugs, ask probing questions, and review your logic. Instead of handing you the answer, mentors will ask: "What did Chrome DevTools show you?" or "What happens if you log that variable on line 14?"
3. Weekly From-Scratch Projects Every single week concludes with a concrete project brief. You do not fill in blanks inside a pre-written template — you create the folder, initialize Git, write the code from scratch, validate your output, and push it to your public portfolio.

---

Standardized Evaluation Rubric (40 / 30 / 30)

Tech Minds Academy does not award certificates merely for paying tuition or sitting in a classroom. Every programme across all four faculties (Web & Full-Stack, AI & Agentic Engineering, Data, Cloud & Cyber Security, and Growth & Foundations) uses our standardized 40 / 30 / 30 Evaluation Model:

Assessment Component	Weight	What Is Evaluated	Passing Standard
Weekly Projects	40%	Functionality, code cleanliness, adherence to weekly brief, Git commit history, and timely submission.	At least 80% of weekly projects submitted and approved.
Stage Assessments	30%	End-of-stage conceptual quizzes, timed practical challenges, and 1-on-1 mentor code reviews.	Demonstrated mastery of core stage concepts before advancing.
Capstone Project	30%	A complete, production-grade final system built from scratch, documented with a README.md, deployed live, and defended on Demo Day.	Mandatory — 100% of Capstone requirements met and defended.

Certification Requirements

To graduate and receive your verified Tech Minds Academy Certificate of Completion, you must satisfy all three criteria:

• Achieve a cumulative score of 70% or higher across Weekly Projects, Stage Assessments, and your Capstone.
• Complete, deploy, and present your Capstone Project (you cannot pass a course on weekly scores alone while skipping the Capstone).
• Maintain at least 80% attendance across scheduled cohort sessions (or submit approved make-up lab work within 48 hours of an excused absence).

Project Grading Scale

When mentors review your weekly GitHub submissions or Capstone repository, each deliverable is scored on a 4-tier engineering rubric:

• 90% – 100% (Distinction / Production-Ready): Exceeds the brief; zero validation or console errors; clean semantic architecture; thoughtful edge-case handling; crisp documentation and atomic Git commits.
• 70% – 89% (Merit / Competent Builder): Meets all core functional requirements; clean readable code; minor stylistic improvements suggested in review.
• 50% – 69% (Developing — Revision Required): Partially working or missing key requirements (e.g., missing form labels, broken responsive layout, hardcoded secrets). Must be refactored and re-submitted within 5 days.
• Below 50% (Incomplete / Unacceptable): Does not run, misses the core objective, or violates Academic Integrity policies.

---

Weekly Student Cadence

Successful Tech Minds students treat learning like a professional software sprint. Here is the exact five-step weekly loop you will follow from Week 1 to Week 12+:

  [1. LEARN] ──► [2. BUILD] ──► [3. PUSH] ──► [4. REVIEW] ──► [5. ITERATE]
  Live classes   Blank folder   Git commit     Mentor PR &     Refactor &
  & lab notes    from scratch   & GitHub push  rubric notes    ship fixes

1. Learn (Sessions 1 & 2): Attend live sessions actively. Type along with the instructor, take structured notes in Markdown, and experiment with small variations immediately after class.
2. Build From Scratch (Session 3 & Lab Hours): Read the weekly project brief carefully. Break the problem into small milestones before writing code. Build the solution from an empty directory without copying old templates.
3. Push to GitHub (Submission Deadline): Commit your work in logical steps with clear commit messages (see our Git & GitHub Workflow) and push to a clean repository with a descriptive README.md.
4. Mentor Code Review: Your instructor inspects your code structure, accessibility, responsiveness, error handling, and commit history — leaving line-by-line feedback just like a Senior Engineer on a real product team.
5. Iterate & Refactor: Apply your mentor's feedback promptly. Fixing the flaws pointed out in code review is where the deepest learning happens.

Expected Time Commitment

• Live Classroom Instruction: 5 – 7 hours per week (across 3 sessions)
• Independent Coding, Labs & Weekly Project: 8 – 12 hours per week
• Total Weekly Investment: 13 – 19 hours per week

---

Academic Integrity & Responsible AI Use

In 2026, AI assistants (ChatGPT, Claude, GitHub Copilot, Gemini) are part of every modern developer's toolkit — in fact, we teach dedicated programmes in Prompt Engineering & AI Tools and Agentic Software Engineering. However, how you use AI during foundational courses determines whether you become a capable engineer or someone who collapses during a technical interview.

The Golden Rule of AI at Tech Minds

Never commit or submit a single line of code that you cannot explain line-by-line during a live verbal code review with your mentor.

During Stage Assessments and Capstone defences, mentors regularly point to a function, CSS Grid rule, or SQL query in your submission and ask: "Why did you choose this approach, and what happens if we change this line?" If you pasted AI output blindly and cannot explain your own code, the submission receives an automatic 0% until rebuilt from scratch.

Green-Light vs Red-Light AI Usage

Green-Light (Encouraged — AI as a Tutor)	Red-Light (Prohibited — AI as a Crutch)
Asking an AI to explain an error message you do not understand after reading it yourself.	Pasting the Tech Minds weekly project brief into ChatGPT and copying the generated code.
Asking: "Can you quiz me with 5 questions on CSS Flexbox justify-content vs align-items?"	Turning on inline AI autocomplete (Copilot/Codeium) during foundational HTML, CSS, JS, or Python weeks.
Sharing your own working code and asking: "Are there accessibility issues I missed here?"	Submitting code copied from another student's GitHub repository or an online template.
Using AI for debugging hints after spending at least 20 minutes inspecting DevTools/logs yourself.	Generating your Capstone README.md or architecture without verifying accuracy against your code.

Turn Off Autocomplete in Foundational Tracks

When taking HTML Mastery, CSS Mastery, JavaScript Fundamentals, or introductory Python, disable AI ghost-text autocomplete extensions in VS Code. Your fingers and brain need to internalize syntax, tag closing, and bracket matching first. Once you reach advanced frameworks and agentic engineering, we will teach you how to orchestrate AI coding agents at high velocity.

---

Attendance, Communication & Getting Unstuck

Attendance Policy

• Arrive on time: Physical students at G5 Plaza Bwari should be seated with laptops booted 5 minutes before class starts. Online students should join with working audio and VS Code ready.
• Excused absences: Power outages, urgent medical situations, or unavoidable commitments happen. Notify your cohort coordinator via our official channel before class starts whenever possible, watch the session replay (or review lab notes), and submit your check-in exercise within 48 hours.
• Three consecutive unannounced absences trigger an academic welfare check-in from student support.

Official Communication Channels

1. Cohort Discord / Slack Workspace: Primary hub for announcements, daily coding questions, code snippets, resource sharing, and peer collaboration.
2. Cohort WhatsApp Broadcast: Urgent schedule updates, campus power/logistics notices, and submission reminders.
3. GitHub Issues & Pull Requests: Technical feedback on weekly projects and Capstone milestones.
4. Email (info@techmindsacademy.org): Official transcripts, tuition receipts, deferrals, and administrative requests.

The "20-Minute Rule" & How to Ask Great Technical Questions

When you hit a bug, follow the 20-Minute Rule:

• Spend 20 focused minutes reading the exact error message, checking line numbers, inspecting Chrome DevTools or terminal output, and testing one hypothesis at a time.
• If you are still stuck at minute 21, do not stay silent for days! Post immediately in your cohort help channel.

Never post: "My code is not working, please help." (Mentors cannot debug what they cannot see.)

Always post using the 4-part bug template:

1. Goal: What I am trying to build (e.g., "Centring navigation links vertically in Week 7 Flexbox navbar").
2. Expected vs Actual: What I expected to happen vs what actually happened (include the exact error text or screenshot).
3. Code Snippet / Repo Link: Formatted code block (using triple backticks) or link to your GitHub branch.
4. What I Already Tried: What you checked in DevTools or changed over the past 20 minutes.

---

Code of Conduct

Tech Minds Academy is a high-trust, inclusive professional environment for learners of all backgrounds, ages, and experience levels. Every student, mentor, and staff member agrees to uphold these standards:

1. Respect Every Learner's Starting Point: Nobody is born knowing what a <div> or a for loop is. Never mock a classmate's question. Celebrate progress and help peers debug without taking over their keyboard.
2. Zero Tolerance for Harassment or Discrimination: Harassment, bullying, discriminatory remarks (based on gender, ethnicity, religion, age, or disability), or disruptive conduct on campus or online results in immediate disciplinary action up to expulsion.
3. Care for Campus Equipment & Facilities: At our G5 Plaza Bwari campus, keep lab desks clean, respect backup power guidelines (do not plug unauthorized high-wattage appliances into workstation circuits), and silence phone ringers during live instruction.
4. Professional Digital Etiquette: Use your real name on cohort platforms, keep discussions constructive, and never share cohort meeting links or internal student contact details publicly.

---

Capstone Demo Day Standards

The final week of every Tech Minds programme culminates in Capstone Demo Day — your transition from student to verified builder.

Every Capstone Must Include:

1. Clean Public GitHub Repository (or portfolio dossier for non-code tracks) with a logical commit trail spanning the build — never a single giant "final upload" commit on the last night.
2. Professional README.md containing:
   • Project title, live URL, and screenshot
   • Problem statement and target user
   • Tech stack and architecture overview
   • Local setup instructions
   • Key technical challenges solved
3. Live Public Deployment: Hosted on GitHub Pages, Vercel, Netlify, Railway, or cloud infrastructure depending on your track.
4. 10-Minute Live Demo & Technical Defence:
   • 2 mins: Problem overview & architecture
   • 4 mins: Live walkthrough of working features on desktop and mobile
   • 4 mins: Code walkthrough & live Q&A from mentors

---

Ready to Begin?

Follow your next onboarding steps in order:

1. Developer Environment Setup — Install VS Code, Chrome, Git, Node.js, and configure your machine for fast, low-data-usage development.
2. Git & GitHub Student Workflow — Master the daily commands you will use to save and submit every weekly project.
3. Explore All Courses & Pathways — Dive into Week 1 of your enrolled track, starting with HTML Mastery if you are on the Web & Full-Stack pathway.