Umesh
UI / Frontend Developer · Mumbai · writing since 29 Jun
Open to roles
Day 23 · public proof
How Umesh thinks
Asks the question others skipped — then owns the answer, and can say why.
↳the log that shows itarticulate·curious·decisive
◈ Open to being sharpened
How Umesh thinks, mapped · lit by their own logs · 6 showing
How they reason · the four moves
Evidence
argue from what you saw, not what you assumed
Alternative
name the option you didn't take
Assumption
surface what you're taking on faith
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 · Sep 09Day 10 · Jul 31
The climb
The shape of Umesh’s 25 entries
beta · being tunedUmesh is moving.
29 Jun → 18 Sept
up when they grow · flat when they hold steady · a dip when they go quiet — it’s the shape of their work, not a score.
up when they grow · flat when they hold steady · a dip when they go quiet — it’s the shape of their work, not a score.
Then → now
Then: Spend some time looking for open source repo for good first issues.
Now: Tailwind over Plain CSS / modules.
Now: Tailwind over Plain CSS / modules.
Every valley named in their own words. Nobody can fake a climb.
About
JavaScriptTypeScriptReactNext.jsNode.jsPythonMySQLHtml5Css3ScssBootstrapTailwind CssReact RouterRest ApisGitJestFigma
Mock interviews
21 Sept · Safal asked
No public reading from this one.
Nobody is scored in these. What you are reading is what they chose to write about their own hour. Sit one →
Umesh · the character an interview can’t show
25 logs over 12 weeks — read from their own words.
Shown so far: Honest when it's not working and Makes the tools better.
Character · what an interview can’t reach
✓Shown
Honest when it's not working
5 stuck and 1 hard days, logged plainly instead of hidden.
Proof · from their own logs
29 Jun
✓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
7 Sept
The judgment behind it ↓
And the technical judgment holds up
Evidence2
Alternative10
Assumption3
Tradeoff0
The arc · they didn’t start here
Early
427
character whys
→
Lately
0
steady
Showed up · 23 days
5 stuck + 1 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
I'm stuck on Promises & Async/Await in JavaScript, and was avoiding it from learning for months even when it was asked in interviews. So today finally tried to learn it, I understa
Read Umesh’s 25 logs ↓sign in to connect with them
Recent logs25
▶ Played as a game · Pick & Defend
Both startups and big companies can be good or bad, I dont want to judge just by the label of it. · I'll know I was right in 2 weeks if: I can explain why I chose the role beyond just the company is Startup or big company, but because of their actual work, learning, culture and team turn out how i expected
▶ Played as a game · Pick & Defend
Tailwind helps to build and move faster with it and keep the styling consistent without spending too much time setting up and naming CSS classes · I'll know I was right in 2 weeks if: I have styled multiple components quickly without writing too many custom CSS rules and the design still looks clean and consistent
▶ Played as a game · Pick & Defend
I want to understand the problem on my own first, but I don't think spending hours stuck is productive when I could learn from someone else's approach. · I'll know I was right in 2 weeks if: I can work through difficult bugs independently and recognise sooner when I'm stuck in a loop and should ask for help.
▶ Played as a game · Pick & Defend
As i am already applying regularly, So sharpening fundamentals and doing interview prep is worth more than applying to roles, as if i got into assessments or interview rounds, i dont want to lose my chance because of my weak fundamentals or basic interview questions · I'll know I was right in 2 weeks if: I can confidently explain my projects and answer common interview questions , and feel comfortable during the interviews or technical assessments. I perform better in interviews and dont get stuck on basic fundamentals concepts.
▶ Played as a game · Pick & Defend
Building small projects give more clear idea about the things then only studing the theory deeply · I'll know I was right in 2 weeks if: I'll know I was right if I can solve SQL questions without checking my notes and can explain why the sql queries works or which sql queries to use to solve that problem instead of only remembering the syntax and mugging up
▶ Played as a game · Pick & Defend
Because i already know that topic , it will be easy to understand when already know half and will other half to understand easier. · I'll know I was right in 2 weeks if: I can explain confident the core concepts, without taking a look at my notes and then ready to start the new topic. Like for ex. currently i am revising sql fundamentals and learning some advanced sql, but only after having a strong fundamental knowledge i will go ahead and learn new skill , like i have to learn python