Skip to main content

Command Palette

Search for a command to run...

day 0: why i'm logging DSA in public

not another solved-problem dump

Updated
1 min read
day 0: why i'm logging DSA in public
U
hey, i'm uttkarsh. posting my leetcode attempts here in real time, no editing for dignity.

i've solved over 500 problems on leetcode and i still freeze on hards. that's the sentence i needed to say out loud before writing this.

final year, placement season, applying to backend roles at companies that interview hard. and that gap, knowing DSA vs solving a hard under pressure, is the most honest problem i have right now.

so i'm doing the unglamorous thing: solving in public, daily, starting tomorrow. not for the streak, but because writing down what i got wrong is the only thing that's ever actually made it stick.

this won't be a polished "optimal solution" blog. it'll look like what it is, someone trying to get good enough, fast enough, before the interviews that decide a lot. some days i'll nail something clean. some days i'll post a rough solution because honest is more useful than impressive.

if you're prepping under the same pressure, i'd rather have you watching this in real time than show up once it's done. and if you spot a better approach, tell me. that's worth more than a like. day 0. see you tomorrow.

leetcode: https://leetcode.com/u/yhqz · portfolio: uttkarsh.dev

stack trace

Part 1 of 1

daily dsa problems, traced. what i solved, how i got there, and where it broke along the way.