Am I Cooked? 🔥

Have you ever looked at everything you have to do and thought, “Am I actually cooked?”

That question inspired this project.

I wanted to build something that could take the feeling of being overwhelmed and turn it into something measurable and actionable. Instead of just making another to-do list, I created Am I Cooked? — a productivity tool that analyzes a situation based on available time, workload, difficulty, and energy, then gives the user a Cooked Score from 0–100.

💡 How I Built It

I built the project using HTML, CSS, and JavaScript. The core logic is written in JavaScript and dynamically generates the results, advice, plans, roasts, and checklists based on the user's inputs.

The scoring system combines four factors:

• ⏰ Time available
• 📚 Workload
• 🧠 Difficulty
• 🔋 Energy level

The program then identifies the user's biggest problem, determines whether they are in Prevention, Recovery, or Emergency mode, and generates an appropriate response.

I also wanted the project to feel smarter than a basic calculator. Users can enter a custom situation, and the program analyzes the text to identify categories such as school, sports, presentations, projects, travel, and events. It can then generate situation-specific advice and checklists.

The project also includes randomized roasts, an Anti-Fried Plan, a Cooked Meter, and a checklist that tracks progress. When every task is completed, the user gets the message:

“YOU HAVE BEEN UNCOOKED. The kitchen has been evacuated.”

🧠 What I Learned

The biggest thing I learned was that building a project is not just about making individual features work — it is about making them work together.

I had to learn how to connect user inputs to calculations, calculations to decisions, and those decisions to dynamically generated content. I also learned more about input validation, conditional logic, text detection, state management, and debugging.

One of the more interesting parts was building the custom situation detector. I had to think about how different words could indicate different situations and how the program should respond when multiple categories were detected.

🚧 Challenges

My biggest challenge was managing the amount of logic in the project. Many combinations of inputs, situations, modes, scores, and problems meant the program needed extensive testing and debugging to respond correctly.

I also had to handle invalid or incomplete inputs without letting the program break. This meant adding validation for missing choices, empty custom situations, invalid time or workload values, and other unexpected inputs.

I built Am I Cooked? during the hackathon, and the process taught me that even a silly idea can become a surprisingly complex technical project once you start asking, “What should happen in every possible situation?”

Most importantly, I learned to turn an idea into a working product instead of stopping at the idea itself.

Built With

• css3
• html5
• javascript