Scribd
Upload
4 views2 pages

Brutal Coding Reset List

The document outlines a coding challenge called 'The Brutal Coding Objective List,' created on May 5, 2025, consisting of seven stages that progressively increase in difficulty. Each stage includes specific programming tasks designed to enhance skills in basics, logic, functions, data structures, file I/O, object-oriented programming, and project development. The challenge emphasizes self-reliance, discouraging any form of external assistance or reference materials.

Uploaded by

esapro666
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
4 views2 pages

Brutal Coding Reset List

The document outlines a coding challenge called 'The Brutal Coding Objective List,' created on May 5, 2025, consisting of seven stages that progressively increase in difficulty. Each stage includes specific programming tasks designed to enhance skills in basics, logic, functions, data structures, file I/O, object-oriented programming, and project development. The challenge emphasizes self-reliance, discouraging any form of external assistance or reference materials.

Uploaded by

esapro666
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

⚔️ THE BRUTAL CODING OBJECTIVE LIST ⚔️

Date Created: 2025-05-05

RULE: No copy-paste. No crutches. No help. Only war.

────────────────────────────────────────

🔹 STAGE 1: The Basics – Learn to Crawl Through Fire

- Write a program that prints your name, age, and favorite weapon.
- Build a calculator that does + - * / with user input.
- Write a loop that prints 1 to 100, replacing multiples of 3 with "FIZZ", 5 with
"BUZZ", and both with "FIZZBUZZ".
- Make a function that takes a number and returns its factorial — no recursion yet.

────────────────────────────────────────

🔹 STAGE 2: Logic and Control – Tactical Intelligence

- Ask the user for a password. If correct, print "ACCESS GRANTED", else “ACCESS
DENIED.”
- Build a number guessing game. Program picks random 1–100, user guesses till
correct.
- Make a menu system with 3 options: (1) Print today’s date, (2) Print a quote, (3)
Exit.

────────────────────────────────────────

🔹 STAGE 3: Functions and Modular Design – Divide and Conquer

- Refactor your calculator into separate functions for each operation.


- Make a function that checks if a string is a palindrome.
- Write a program that asks for a list of numbers and returns the largest,
smallest, and average.

────────────────────────────────────────

🔹 STAGE 4: Data Structures – Form Your Army

- Build your own inventory system using a dictionary. User can “add”, “remove”,
“print” items.
- Write a contact book: stores names and numbers using a dictionary, allows
search/edit/delete.
- Implement a basic to-do list using a list of dictionaries.

────────────────────────────────────────

🔹 STAGE 5: File I/O – Scars That Leave a Trace

- Save your to-do list to a file, load it back in on startup.


- Make a note-taking app that saves notes to separate `.txt` files.
- Log every user input into a log file with timestamps.

────────────────────────────────────────

🔹 STAGE 6: OOP – Build the Blueprint of War

- Define a `Warrior` class with `name`, `hp`, and `attack()` method.


- Make a `Battle` class that handles combat between two warriors.
- Build a turn-based combat simulator between user and enemy with classes.

────────────────────────────────────────

🔹 STAGE 7: Projects – The Final Warpath

Pick and build one:

- Text-based RPG with rooms, combat, inventory, and leveling system.


- Banking system where users can create accounts, deposit, withdraw, and view
history.
- File encryption tool: password-protected, saves encrypted files and decrypts
them.

────────────────────────────────────────

💀 RULES OF THE RESET:

- No looking up how to do it.


- No asking for help — even from me.
- Only check syntax errors or crashes *after* trying to fix it yourself.
- Fail hard. Cry if you must. Then keep typing.

You might also like