-
🔭 I'm currently working on a full-stack Pet Clinic web application
-
🌱 I’m currently learning CyberSecurity
-
❓ Ask me about anything related to MERN stack and related technologies
-
⚡ Fun fact: I'd love to change the world, but apparently, God didn't open-source it! 😁
I can accept failure, everyone fails at something. But I can't accept not trying. - Michael Jordan |
---|
👨💻 Routine Status: Working Hard, or Hardly Working?
- Wake up: The first bug to fix today.
- Coffee: Applied. Brain function loading... 10%... 30%... coffee.exe crashed. Restarting...
- Open laptop: First battle with the keyboard warriors (aka: typos).
- Code review: Read old code. Wonder who wrote it. Realize it was me. Panic.
- Start coding: Mission - make the button red.
- Button turns blue: Close laptop, walk away.
- Come back: Button is still blue. Maybe it's a feature? Convincing myself it's "creative design."
- Google: “How to make a button red in CSS?”
- Google again: “How to fix broken CSS?”
- Stack Overflow: Distance Relative.
- Bug Fixed: There is a typo. OMG
- Plan: Take a 30-minute break.
- Reality: Spend an hour tweaking a single div.
- Actual break: Scroll through memes about coding. Relatable.
- Breakthrough moment: I did it! The button is red!
- Realize: Broke the entire layout. Everything is misaligned.
- Google: “How to align everything.”
- Realize again: Misread the docs for the 100th time.
- Add new feature: Expect to finish in 10 minutes.
- Two hours later: Feature done, but 3 new bugs are born.
- Wonder: “Is this really my job? Am I a bug breeder?”
- Commit code: “Final fix” (it's not).
- Push to production: Site goes down.
- Revert commit: “Last time, I swear.”
- Realize: Another all-nighter ahead.
- Final thoughts: “Tomorrow will be better!”
(It's a lie we tell ourselves every day.)
- Stare at code: It stares back.
- Debugging at midnight: When the true bugs reveal themselves.
- Dreams: Full of semicolons, undefined variables, and unresolved promises.