42 Singapore Piscine — Jaro Gee

This repository contains my solutions and final scores during the 42 Singapore Piscine.

---

About

• Username: Mgee
• School: 42 Singapore @ SUTD
• Run: 8
• Duration: 06 October 2025 – 31 October 2025

The Piscine is a 26-day immersion in C programming, shell, and problem-solving.

It’s tough, intense, and oddly addictive once you get into the flow.

---

Repository Structure

├── Shell00/ 
├── Shell01/
│
├── C00/
├── C01/
├── C02/
├── C03/
├── C04/
├── C05/
├── C06/
├── C07/
├── C08/
├── C09/
├── C10/
├── C11/
├── C12/
├── C13/
│
└── README.md

---

Exam Tips

1. Exam Registration

• Register for the exam
  &&
• Subscribe to the event
• Otherwise you won't be able to take the exam

2. Entering the terminal

• Log into the terminal by entering

  Username: exam
  Password: exam
  

• To access exam shell in terminal

  examshell

• The exam shell only accepts these commands:

  status
  grademe
  finished
  

3. Personal login

• You’ll be prompted for your own username and password.

• When typing your password, nothing will appear — no cursor movement or *.

• Just type it and press Enter.

4. Login window

• You have 10 minutes to log in.

• If you miss it, you’ll need to log out and leave the exam.

5. Allowed items

• Only prescribed medication, a water bottle, and a pen are allowed.

• You’ll be given a blank sheet of paper and ear plugs.

• No electronic devices of any kind.

6. Extracting the questions

• When you access the exam shell, you’ll see brief on-screen instructions and a folder for the current question you’re attempting.

• Each question appears one at a time — complete and submit it before moving on to the next.

• Open another terminal or VScode to work on exam questions.

7. Question order

• You must complete and pass each question in order before moving on to the next.

• Getting stuck on one question means you can’t proceed to any others until that one is solved.

8. Manual

• The terminal man pages are available and allowed.

9. Editor

• VSCode is allowed, but it comes without plugins.

10. Compiling

• Always compile with:

  cc -Wall -Werror -Wextra

  These flags helped me catch errors early and pass several questions.

---

Notes

• I included short test snippets as comments within each file, right below the solution.

• All you have to do is remove the denotation for comments (/**/), compile then run the program to see results

• They’re simple examples meant to check basic logic before submission.

• Norminette compliance varies across exercises — this repo isn’t perfect, but it’s honest.

---

Scores

• BSQ: 50% (Teammate: Ying)

• C00: 60%

• C01: 100%

• C02: 97%

• C03: 100%

• C04: 85%

• C05: 60%

• C06: 100%

• C07: 100%

• C08: 100%

• C09: 100%

• C10: Did Not Attempt

• C11: Did Not Attempt

• C12: Did Not Attempt

• C13: Did Not Attempt

• Shell00: 100%

• Shell01: 92%

• Rush 00: 120% (Teammates: Mmanojku, Mmoe-thu)

• Rush 01: 0%

• Rush 02: 0%

• Exam 00: 10%

• Exam 01: Late

• Exam 02: 0%

• Exam Final: 6%

---

Final Note

• This repo is a snapshot of my learning journey at 42 Singapore.

• It’s not meant to be a perfect reference. Just a record of progress, mistakes, and lessons along the way.

---

Author

• Name: Jaro Gee

• Piscine Run: 8

• Based in: Singapore

Currently learning C, surviving on coffee, and building momentum.

Runbook

See hawkerboys_app/README.md for setup and deployment instructions.