DEV Community

Cover image for Yesterday Was Not Coding… It Was “Reality Check” Day 😅
Bharath Kumar_30
Bharath Kumar_30

Posted on

Yesterday Was Not Coding… It Was “Reality Check” Day 😅

Yesterday I thought it would be a normal coding day

.

  1. Open laptop.
  2. Write some FastAPI routes.
  3. Push code.
  4. Sleep peacefully.

But no.

My guide said:

  • “Do code review.”
  • “Show demo.”
  • “Screen record everything.”
  • “Push to Git.”
  • “Check database.”
  • “Check hosting.”

And suddenly my calm developer life turned into production mode 😭

Code Review Time

First task:

Review my own code.

That moment when you open your own project and think:

“Who wrote this logic bro?”

Oh wait… it was me.

I had to check:

  • Service structure
  • OAuth flow
  • Token storage
  • Folder organization
  • Error handling

That’s when I realized:

Writing code is easy.
Maintaining clean architecture is hard.

Screen Recording the Demo

Next instruction:

“Record screen and explain.”

Explaining your own system on screen is different from just running it.

You suddenly notice:

  • That one messy function
  • That confusing route name
  • That hardcoded value 😅 But honestly, screen recording forced me to understand my own architecture clearly.

That was useful.

Push to Git

Then came the classic:

“Push everything to Git.”

Yes, I use Git properly.

But pushing after review feels serious.

Now it’s not just “my local experiment.”

It becomes:

Official version.

Database Check

Then I had to explain:

  • Why I chose PostgreSQL
  • How tokens are stored
  • How encryption is handled
  • How user-platform relation works Suddenly this was not just a coding project.

It became:

System design discussion.

Hosting Review

Then hosting.

I have VPS with full access.

So I explained:

  • FastAPI backend
  • Uvicorn
  • Nginx
  • PostgreSQL
  • systemd services

When I said that, even I felt:

“Okay… this is actually production-style setup.”

What I Learned Yesterday

Yesterday wasn’t about adding features.

It was about:

  • Understanding architecture
  • Explaining decisions
  • Cleaning code
  • Thinking like an engineer Sometimes growth doesn’t come from writing new code.

It comes from reviewing old code.

End of Day Feeling

Was I tired?

Yes.

Was it worth it?

Absolutely.

Because now I understand my own system deeper.

And that confidence is powerful.

Top comments (0)