Safal

AI Full Stack Developer Intern · writing since 18 Jul
Day 14 · public proof
Their logs19
Safal BhandariAI Full Stack Developer Intern2 Oct
Safal BhandariAI Full Stack Developer Intern22 Sept
Safal BhandariAI Full Stack Developer Intern21 Sept
Safal BhandariAI Full Stack Developer Intern19 Sept
Safal BhandariAI Full Stack Developer InternStuck · 17 Sept
Safal BhandariAI Full Stack Developer InternBuilt · 14 Sept
Safal BhandariAI Full Stack Developer Intern9 Aug
Safal BhandariAI Full Stack Developer InternBuilt · 7 Aug
WhyEnforced a strict "No Raw Cloud Sync" rule by keeping all active files inside a locally controlled folder structure rather than connected cloud drives.The Trade-off: The practice loses automatic real-time sync across multiple off-site devices, requiring manual file transfers if the physician works on a secondary laptop.The Rationale: Giving a desktop agent autonomous read/write access to a shared cloud drive (like Google Drive or OneDrive) risks syncing unverified or draft notes across external networks. Limiting Cowork to a dedicated, encrypted local folder creates a hard security boundary, keeping patient context completely isolated while ensuring zero risk of accidental cloud overwrites.
Safal BhandariAI Full Stack Developer Intern5 Aug
Safal BhandariAI Full Stack Developer InternBuilt · 30 Jul
WhyI chose to follow the MCP standard instead of building a custom API because it makes the integration easier to maintain and compatible with AI clients that already support MCP.I also used Next.js to keep the implementation straightforward and easy to deploy. The main trade-off is that lowering the friction to publish also lowers the friction to spam users could generate and post low-quality content more easily. Any production version should therefore include safeguards such as authentication, rate limiting, moderation, or user approval before publishing. I considered the improved user experience worth the trade-off, provided those protections are added.
◈ Open to sharpen
Safal BhandariAI Full Stack Developer Intern29 Jul
Safal BhandariAI Full Stack Developer InternBuilt · 28 Jul
Safal BhandariAI Full Stack Developer InternLearned · 28 Jul
Safal BhandariAI Full Stack Developer Intern24 Jul
Safal BhandariAI Full Stack Developer Intern24 Jul
Safal BhandariAI Full Stack Developer Intern24 Jul
◈ Open to sharpen
Safal BhandariAI Full Stack Developer InternLearned · 24 Jul
Safal BhandariAI Full Stack Developer InternStuck · 24 Jul
Safal BhandariAI Full Stack Developer Intern18 Jul
4 months on Proof
■ weeks with logs■ quiet week
19 logs · 9 say why
How Safal thinks
Asks the question others skipped — then owns the answer, and can say why.
↳the log that shows it
articulate·curious·decisive
How Safal thinks, mapped · lit by their own logs · 5 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
What their logs say
Articulate
you write the full why
Showing — it’s in their logs; tap to see them allno %, no rank — evidence, not a score.
Milestones1 earned
Day 10 · Sep 17
About
TypeScriptJavaScriptPythonReactNext.jsNode.jsExpressPostgresMySQLRedisDockerAWSLLMs / GenAITailwind CssPrismaWebsocketsCloudflare WorkersAzureRabbitmqLangchain
Projects
openai.com
openai.com ↗
1 log
build-in-public-sigma
build-in-public-sigma.vercel.app ↗
Why · from their logI chose to follow the MCP standard instead of building a custom API because it makes the integration easier to maintain and compatible with AI clients that already support MCP. I also used Next.js to keep the implementation straightforward and easy to deploy. The main trade-off is that lowering the friction to publish also lowers the friction to spam users could generate and post low-quality content more easily. Any production version should therefore include safeguards such as authentication, rate limiting, moderation, or user approval before publishing. I considered the improved user experience worth the trade-off, provided those protections are added.
GitHub

Repos show when they’re linked from a log. Proof doesn’t count stars or commits.

Interviews they've given

Safal has asked the questions 26 times.

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