Devlog #2

Time logged: 2h 16m
Emotional damage: minimal
Coffee consumed: classified
Bugs defeated: several
Bugs created: also several

---

The Great Construction Phase

I opened the project like a surgeon preparing for an operation.
Except instead of scalpels, I had:

• React components
• Express routes
• And a database that behaves like a moody houseplant

Folders appeared.
Files multiplied.
Imports broke.
Imports were fixed.
I felt powerful.

---

The “Why Is This Not Working?” Arc

At some point, I wrote code so elegant it should’ve been framed.
Then I ran it.

It immediately threw an error.
Classic.

I spent a solid 14 minutes staring at the screen like:

“Explain yourself.”

Eventually, I found the problems.
Victory tasted sweet.

---

The Backend Awakens

Express booted up like a sleepy dragon.
SQLite whispered:

“I’m small… but I will store your deepest secrets.”

Endpoints were created:

• GET /notes - for reading your questionable ideas
• POST /notes - for adding new questionable ideas
• DELETE /notes - for removing the really questionable ones

Everything worked.
Until it didn’t.
Then it worked again.
I don’t question it anymore.

---

Frontend Chaos (React Edition)

I built components like a lego master:

• NoteList - where your thoughts go to hang out
• NoteEditor - where new chaos is born
• SearchBar - because sometimes you forget what chaos you wrote

React was cooperative today.
Mostly.
Except when it wasn’t.
But we don’t talk about that.

---

The Legendary “Why Won’t You Connect?” Saga

Frontend and backend behaved like two siblings forced to share a room.

Frontend:

“I can’t find the server.”

Backend:

“I’m literally right here.”

Me:

“Both of you, stop.”

Eventually, they made peace.
The API worked.
I celebrated by saving a note titled “IT WORKS!!!”

---

Final Thoughts

After 2 hours and 16 minutes:

• The app runs
• The notes save
• The database behaves
• The components render
• And I only threatened to delete the whole project twice

Honestly?
A successful dev session.