What is this?Sign in

ESAKI

Fullstackdeveloper · Sivakasi · writing since 8 Jun
Open to roles
Day 36 · public proof
Their logs30
ESAKI RAJFullstackdeveloperFree write · 9h
WhyWe use loose coupling because it makes the application easier to manage, change, and grow without affecting other parts of the system.
ESAKI RAJFullstackdeveloperFree write · 11h
ESAKI RAJFullstackdeveloperFree write · 2d
ESAKI RAJFullstackdeveloperFree write · 2d
Whybecause financial briefs demand strict data integrity and zero downtime: missing fields are left absent rather than defaulted to zero, and production resilience requires handling Sage UK Start tier 405 limits, deduplicating OAuth token refreshes to eliminate race conditions, and verifying that failed syncs preserve existing complete store data without corrupting the ledger.
Mock · feedback from an interviewer
ESAKI RAJFullstackdeveloperFree write · 3d
ESAKI RAJFullstackdeveloperFree write · 3d
ESAKI RAJFullstackdeveloperFree write · 3d
WhyExecutive briefs demand absolute data integrity: we strictly enforced "absent, never defaulted" so missing Sage fields are never disguised as fake zeroes or synthetic defaults.To make the integration production-ready, we engineered proactive OAuth token rotation with in-flight deduplication to prevent 401/400 race conditions, isolated UK Start tier 405 purchase restrictions so sales and bank sync unaffected, and added atomic file persistence to prevent store corruption during background syncs.
ESAKI RAJFullstackdeveloperBuilt · 4d
ESAKI RAJFullstackdeveloperNoticed · 5d
ESAKI RAJFullstackdeveloperLearned · 5d
ESAKI RAJFullstackdeveloperBuilt · 6d
ESAKI RAJFullstackdeveloperFree write · 6d
ESAKI RAJFullstackdeveloperFree write · 3 Nov
ESAKI RAJFullstackdeveloperFree write · 2 Nov
ESAKI RAJFullstackdeveloperBuilt · 1 Nov
ESAKI RAJFullstackdeveloperLearned · 31 Oct
ESAKI RAJFullstackdeveloperFree write · 30 Oct
ESAKI RAJFullstackdeveloperFree write · 30 Oct
ESAKI RAJFullstackdeveloperFree write · 29 Oct
ESAKI RAJFullstackdeveloperFree write · 23 Oct
ESAKI RAJFullstackdeveloperFree write · 18 Oct
ESAKI RAJFullstackdeveloperStuck · 16 Oct
ESAKI RAJFullstackdeveloperLearned · 15 Oct
ESAKI RAJFullstackdeveloperFree write · 14 Oct
ESAKI RAJFullstackdeveloperFree write · 13 Oct
ESAKI RAJFullstackdeveloperFree write · 13 Oct
ESAKI RAJFullstackdeveloperFree write · 11 Oct
ESAKI RAJFullstackdeveloperFree write · 10 Oct
ESAKI RAJFullstackdeveloperFree write · 10 Oct
ESAKI RAJFullstackdeveloperLearned · 6 Oct
5 months on Proof
■ weeks with logs■ quiet week
61 logs · 33 say why
How ESAKI thinks
Decides and owns the call — moves before being told.
↳the log that shows it
articulate·curious·decisive
◈ Open to being sharpened
How ESAKI thinks, mapped · lit by their own logs · 7 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
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 30 · Nov 03Day 10 · Sep 17
About

Passionate Full Stack Developer skilled in React.js, JavaScript, PHP, Laravel, and MySQL. Experienced in building responsive web applications and REST APIs. Eager to learn, solve problems, and develop scalable solutions.

JavaScriptReactMySQLPhpLaravelCssBoostrapHtml
🎓 BBA · Sri Krishnasamy Arts and Science College · 2022
Careerself-reported
Jan 2026 – Jun 2026
web developer
innovasoftmax · bangalore
Mock interviews
10 Nov · Safal asked

No public reading from this one.

10 Nov · Radhakrishnan asked

No public reading from this one.

3 Nov · prachi asked

No public reading from this one.

7 Oct · Radhakrishnan asked

No public reading from this one.

5 Oct · Karthik asked

Recently, I had a great mock interview with Karthik. It was a very valuable experience that helped me understand my strengths and areas for improvement. The questions and discussion gave me a better perspective on technical concepts, especially cybersecurity and ethical hacking. I also received some valuable advice that inspired me to learn and improve further. Thank you, Karthik, for your time and guidance. It was a really good learning experience!

Nobody is scored in these. What you are reading is what they chose to write about their own hour. Sit one →

Want a page like this?
Write what you tried, a few lines a day. People who’d hire you read it.
Start your Proof