Pat I ch Notes: The “I Fixed That Annoying Stuff” UpdateHey everyone! I just rolled out a new update based on the feedback you gave me.
I tackled the biggest pain points today:Security Upgrade: No more hardcoded keys!
Quality of Life:
Training Tab: Lookin’ cleaner and more organized.
Nav Hover: Fixed that weird hover glitch that followed you between tabs.Check it out and let me know if you find anything else.
So I had this idea. I wanted to make history feel physical, like it actually happened somewhere. Drop a pin. Show the year. Make people guess. That felt more like a game than a textbook.
The first version was a disaster. I tried drawing the world map myself using canvas polygons. Two days of tweaking coordinates and my map still looked like a deformed potato. Africa was a blob. Europe looked like it had been through a war. I finally gave up and switched to a real image.
Getting the map to work took way longer than I expected. Online images were slow. Base64 was huge. SVG was a nightmare. Eventually I just told people to drop a jpg in the same folder. It’s not fancy, but it works and it’s fast.
The pin placement was its own headache. Every event needed exact coordinates. Battle of Hastings needed to hit England. Columbus needed the Caribbean. Hours of refreshing the page and tweaking numbers by tiny amounts. My eyes hurt.
But building the event list was actually fun. I dug through Wikipedia looking for interesting stuff. War, science, politics, exploration, culture, disaster. Each event needed a year, location, description, and a fun fact. I probably spent too much time down rabbit holes. Did you know Beethoven was completely deaf when he conducted his ninth symphony? Or that the Mona Lisa has no eyebrows? I don’t regret a single minute of that.
Difficulty levels were tricky. I mixed obscurity with age. Ancient stuff is harder. Recent stuff is easier. It’s not perfect but it works.
Design wise, I wanted the game to feel warm — like an old atlas, not a corporate dashboard. Parchment colors, a compass rose, serif fonts. I wanted people to feel like they were opening a book from their grandparent’s shelf.
The quit button was a small thing that took too much thought. I realized people need an easy way out. So I put one in the corner and added Escape key support. Small detail, big difference.
What I learned: the little stuff matters. A good map makes the game feel real. A fun fact turns a correct answer into something you actually remember. A visible quit button shows you respect the user’s time.
I also learned that AI is useful for grinding through boilerplate and generating ideas faster than I could alone. But the creative stuff, the polish, the decisions about what actually feels good — that’s still on me. The AI sketches scaffolding. I build the house.
The result is a game that loads instantly, works on any device, and teaches you something without feeling like school. It’s not perfect. I’d love to add more events, better visuals, maybe some sound effects. But it’s solid, it’s fun, and I’m happy with it.
If you play it and learn one thing you didn’t know before, I’ll consider it a win.
aka “I built a plant hydration therapist”
My mom kept drowning her garden. Every. Single. Day. Even after rain. I was like “Mom, you’re watering the tomatoes to death” and she hit me with “Well how am I supposed to know??”
So I built this instead of doing my math homework. Priorities, right?
You punch in some numbers about your field — soil type, moisture, what you’re growing, weather stuff — and it spits out:
No PhD required. No manual. Just sliders and dropdowns.
10,000 real farm records. Messy. Unbalanced. Perfect.
The model had to learn that “High” actually matters, not just predict “Low” every time and call it a day.
Used:
Trashed:
Why? Because irrigation need comes down to like 5 things. The rest is noise. Fight me.
#2d5a3d) — the serious backbone#c9a84c) — warmth so it’s not a hospitalFonts: Literata for headings (book vibes), Plus Jakarta Sans for UI (clean but friendly), DM Mono for numbers (because monospaced numbers make my brain happy).
No charts-for-the-sake-of-charts. Just the confidence bar because “Low: 72%” is way more useful than just “Low.”
Mom tested it. Punched in her garden. Model said:
“Medium irrigation need. Soil moisture is adequate but temperature is rising. Consider watering in the evening to reduce evaporation.”
She looked at me like I hacked the Matrix. I was just like “yeah, JavaScript, whatever” but inside I was doing backflips.
Yeah I used AI. For the boilerplate. For the JavaScript I always forget. For debugging that one stupid bug where the bars wouldn’t render.
Not for the creative decisions. Not for the colors or the flow or the “vibe.” That’s all me.
Think of it as a coding intern who knows everything but has zero taste. I tell it what to build, it spits out code, I fix it, break it, fix it again, and make it actually good.
Before Recovery Quest was Recovery Quest, it was just a mess on my screen at 1am. Idk how else to put it. Let me back up.
I was lying in bed, half scrolling, half thinking about nothing, when this question hit me: why does real life not have a UI?
In games I always know exactly where I stand — health bar, stamina, XP, buffs, debuffs. In real life? Nothing. You wake up and wonder “am I tired or just overthinking it” with no number to check. You’re just guessing your own state all the time.
That bugged me more than it should’ve. So I got up, opened my editor, and started typing with zero plan.
What I had after that session was, with love, extremely boring: a sleep input, a workout log, a nutrition counter.
Nothing different from the five other apps I’d already downloaded and quit on.
Next day I looked at it and realized I’d just rebuilt what I was trying to escape. Cool. Great use of a night.
I changed “sleep hours” to “recovery impact.” I changed “workout logged” to “training XP gained.” Same data, same numbers, just different words.
But seeing “+40 training XP” instead of “workout logged” did something weird. It stopped feeling like filling a form and started feeling like leveling up a character. Who is also me.
That tiny change became the seed for everything else.
After that night I started designing systems for my own life without meaning to. The dashboard became home base. Streaks became a combo system. Recovery score became a condition stat.
None of it was planned, it just kept clicking into place.
I kept things simple: vanilla HTML, CSS, JS, no backend, everything in local storage. I didn’t want infrastructure slowing down an idea I wasn’t even sure about.
And I didn’t want another fitness tracker. There are too many, and most feel identical after week two. I wanted something else — not “what did you do today,” but “what happens if you keep doing this?”
Memory Map started as a throwaway idea — one photo per day on a timeline.
But scrolling back through it later actually hit me. You can watch yourself change, not as stats, but as a person. I went back two weeks once and just stared at it.
I didn’t build this alone.
That night I had a feeling and no idea how to turn it into code. So I talked it through with Claude like a senior dev sitting next to me at 1am asking, “okay, but how would this work?”
It helped me figure out recovery scoring, XP scaling, and why my first streak logic kept breaking. Stuff I’d been stuck on just got untangled.
I still wrote the code and made every decision about what this was. But that back-and-forth made me willing to try things I’d normally overthink out of.
Every time I added something, I’d get that “wait… this is actually a system now” feeling.
Rare enough that I kept chasing it.
Recovery Quest was still rough and missing most of what it has now, but it already changed how I think about habits — not as a checklist, but as mechanics affecting other mechanics.
Hard to go back once you see it that way.
Devlog #1, done. More soon.
Before Recovery Quest was Recovery Quest, it was just a mess on my screen at 1am. Idk how else to put it. Let me back up.
I was lying in bed, half scrolling, half thinking about nothing, when this question hit me: why does real life not have a UI?
In games I always know exactly where I stand — health bar, stamina, XP, buffs, debuffs. In real life? Nothing. You wake up and wonder “am I tired or just overthinking it” with no number to check. You’re just guessing your own state all the time.
That bugged me more than it should’ve. So I got up, opened my editor, and started typing with zero plan.
What I had after that session was, with love, extremely boring: a sleep input, a workout log, a nutrition counter.
Nothing different from the five other apps I’d already downloaded and quit on.
Next day I looked at it and realized I’d just rebuilt what I was trying to escape. Cool. Great use of a night.
I changed “sleep hours” to “recovery impact.” I changed “workout logged” to “training XP gained.” Same data, same numbers, just different words.
But seeing “+40 training XP” instead of “workout logged” did something weird. It stopped feeling like filling a form and started feeling like leveling up a character. Who is also me.
That tiny change became the seed for everything else.
After that night I started designing systems for my own life without meaning to. The dashboard became home base. Streaks became a combo system. Recovery score became a condition stat.
None of it was planned, it just kept clicking into place.
I kept things simple: vanilla HTML, CSS, JS, no backend, everything in local storage. I didn’t want infrastructure slowing down an idea I wasn’t even sure about.
And I didn’t want another fitness tracker. There are too many, and most feel identical after week two. I wanted something else — not “what did you do today,” but “what happens if you keep doing this?”
Memory Map started as a throwaway idea — one photo per day on a timeline.
But scrolling back through it later actually hit me. You can watch yourself change, not as stats, but as a person. I went back two weeks once and just stared at it.
I didn’t build this alone.
That night I had a feeling and no idea how to turn it into code. So I talked it through with Claude like a senior dev sitting next to me at 1am asking, “okay, but how would this work?”
It helped me figure out recovery scoring, XP scaling, and why my first streak logic kept breaking. Stuff I’d been stuck on just got untangled.
I still wrote the code and made every decision about what this was. But that back-and-forth made me willing to try things I’d normally overthink out of.
Every time I added something, I’d get that “wait… this is actually a system now” feeling.
Rare enough that I kept chasing it.
Recovery Quest was still rough and missing most of what it has now, but it already changed how I think about habits — not as a checklist, but as mechanics affecting other mechanics.
Hard to go back once you see it that way.
Devlog #1, done. More soon.
