Karthik
3rd year CSE, building in stealth. · writing since 5 Jul
Day 14 of 30Open to roles
Day 21 · public proof
How Karthik thinks
Decides and owns the call — moves before being told.
↳the log that shows itarticulate·curious·decisive
◈ Open to being sharpened
How Karthik thinks, mapped · lit by their own logs · 5 showing
How they reason · the four moves
Alternative
name the option you didn't take
Tradeoff
state the cost of the call
How they work · the qualities founders read for
Curious
you ask, not just assert
Articulate
you write the full why
Ownership
you own the call & the miss
Showing — it’s in their logs; tap to see them allno %, no rank — evidence, not a score.
Milestones2 earned
Day 20 · Oct 06Day 10 · Aug 05
About
C/C++PythonGoTypeScriptJavaCDockerLinuxWebassemblyOpenglReactGitCmakeGhidraWiresharkBlenderMatlabSqlEbpfLLMs / GenAI
Mock interviews
Karthik has asked the questions 6 times.
Nobody is scored in these. What you are reading is what they chose to write about their own hour. Sit one →
Karthik · the character an interview can’t show
28 logs over 14 weeks — read from their own words.
Shown so far: Adjusts and Makes the tools better.
Character · what an interview can’t reach
✓Shown
Adjusts — updates when the evidence changes
Whys deepened from ~172 to ~289 characters — self-correction, in the open.
✓Shown
Makes the tools better
3 reports they filed got fixed — they improve what they use, not just what they're paid to.
Proof · reports they got fixed
20 Aug
The judgment behind it ↓
And the technical judgment holds up
Evidence1
Alternative8
Assumption1
Tradeoff3
The arc · they didn’t start here
Early
172
character whys
→
Lately
289
twice the depth
Showed up · 18 days
1 stuck + 0 hard days, logged anyway. Nobody farms honest bad days — that’s why this counts and a streak doesn’t.
A hard day, in their words
To develop a lightweight Xorg based server for pure work, similar to Ice WM but as a bare compositor. The issue stemmed from Wayland having issues and not rendering info properly.
Read Karthik’s 28 logs ↓sign in to connect with them
Their logs28
◈ Open to sharpen
◈ Open to sharpen
◈ Open to sharpen
▶ Played as a game · Pick & Defend
You cannot build on a shaky foundation. You'll look for shortcuts or for ways to scaffold your foundation, which doesn't work in the long run. · I'll know I was right in 2 weeks if: In the two weeks, if I started the topic, I stall and crash, but revising, I end up making slow progress.
◈ Open to sharpen
◈ Open to sharpen
▶ Played as a game · Pick & Defend
Information. The button must be tactile. It must show acknowledgement of the click, and if you disable the button and have a little loader, you acknowledge the click and let the user know it's in progress. · I'll know I was right in 2 weeks if: There isn't any complaints about the buttons being slow to respond. People are surprisingly calm when they're well informed.
▶ Played as a game · Pick & Defend
Debouncing reduces overhead. The person may retype and edit quite commonly. The point is to reduce excess traffic as much as possible without impacting the front facing service, and throttling has a chance of hurting multiple fast legitimate movements. Debouncing prevents that by putting control in the hands of the user, not of an arbitrary number. · I'll know I was right in 2 weeks if: Nobody ever noticed a change in their operations with the platform, because optimisation shouldn't happen at the cost of UX.
▶ Played as a game · Pick & Defend
I actually am currently the latter, and it's great for interfacing and communicating with technical individuals. But at the end of the day, depth is skill. And it's not a linear increase, but much more substantial. · I'll know I was right in 2 weeks if: I do well in a possible internship I'm looking forward to.
◈ Open to sharpen
▶ Played as a game · Pick & Defend
While I love VPS's(DigitalOcean my beloved), and while I will espouse the amazing benefits of homelabbing, a company requires reliable function. And the more abstracted away something is, the lesser the chance of breaking in prod. · I'll know I was right in 2 weeks if: When the VPS goes down because someone accidentally modified the firewalls ruleset but my site on Vercel is running fine.
Want a page like this?
Write what you tried, a few lines a day. People who’d hire you read it.
Start your Proof