Once Upon a Keyboardโฆ
A Full-Stack Dev Learnerโs Quest to Code, Write, and Survive Infinite Console Errors
It all started with a single line of code. Or maybe it was the 100th error message. Either way, Iโm Kush: part-time bug creator, full-time debugger, and accidental storyteller of the chaos that is learning to code.
Chapter 1: The Daily Grind Every morning, I wage war against my to-do list:
9 AM: โToday, Iโll finally understand React state management!โ
11 AM: [Finds self Googling โwhy is my API returning potato ๐ฅโ]
3 PM: Defeats a cryptic error by adding a comma. Declares victory.
Midnight: Writes a Medium post titled โHow I Fixed Nothing for 8 Hours (And Why It Mattered).โ
The Tools of My Trade My stack? Today itโs Node.js & Reactโtomorrow, who knows?
Why I Blog Like Itโs My Job Because nobody tells you the real coding milestones:
The first time you cry-laugh at a typo.
The day you accidentally rm -rf something important.
The moment a stranger says โyour post saved my sanity.โ
Join Me Ifโฆ
Youโve ever shouted โIT WORKED ON MY MACHINE!โ into the void.
You want raw, unfiltered notes from someone still eating ramen while debugging.
You believe tech isnโt about geniusโitโs about showing up, breaking things, and writing about it.
The Quest Continues Iโm out here chasing that mythical โsenior developerโ title. Until then, Iโll be:
Writing daily: Tutorials that start with โI barely get this, but hereโs howโฆโ,
Connecting: With fellow code warriors who laugh at โundefined is not a function.โ
The 100-Subscriber Bet
Help me unleash chaos: โIf I hit 100 subs, Iโll flood YouTube with daily shorts of:
โณ Timelapses of my desk devolving into a coffee-cup wasteland, ๐ Unhinged โBEFORE/AFTERโ edits of my code (spoiler: the โafterโ is still broken).
Until then? Follow me on ๐ฅ YouTube ๏ปฟ
๏ปฟ
