Experience
4+ years
Projects
22 shipped
Tech Stack
35 technologies
Hello World! I'm Sushil
/**
* Full-stack developer crafting elegant solutions.
* Passionate about clean code, great UX, and shipping fast.
*/
Software engineer with about 4 years driving end-to-end delivery, mentoring teammates, and aligning stakeholders to outcomes. Scales impact with AI-assisted workflows (planning, code, QA), improving velocity and quality while keeping teams focused on business value.
## EXPERIENCE.log
// git log --oneline --career
## SKILL.json
{
"version": "1.0.0",
"languages": {
},
"frameworks / libraries": {
},
"databases / services": {
},
"tools": {
}
}
## PROJECTS.featured
// Top projects — click to explore
Prediction Game
A real-time sports prediction platform. Create a challenge in under a minute, share one link with your crew, and watch the live leaderboard shift as answers come in.
+1
## POSTS.recent
// Latest writings and articles
AI did not reduce my workload but It increased my throughput
I’m not doing less - I’m doing more: more experiments, more automation, more “small” ideas that actually make it to production. Lately I’ve been rotating between Codex 5.3 and Opus 4.6. Both are strong, but they optimize for different failure modes and once you treat them that way, picking the right one gets easy. Codex 5.3: depth + correctness Codex doesn’t rush. Give it a complex problem and it goes deep. One time, I asked it to persist AG Grid state (columns, ordering, filtering, sorts the full setup) against a specific version. It fetched archived docs, dug into node_modules, tracing the relevant APIs, validating assumptions, built a plan. One shot. Done. Explore → Reason heavily → Verify → Completeness over speed Codex fixes root causes, not symptoms. Minimum changes, maximum effect. Opus 4.6: Fast builder with strong UI instincts Opus is different. It follows instructions precisely - and that’s genuinely powerful. It’s fast, excellent at UI (seriously impressive), great at tool calls & best-in-class for building things from scratch And Claude Code’s harness makes it even better. 💡 Pro tip: With Opus, be explicit about intent, not just what. Tell it why you want something and watch it fly. My decision rule •🎯 High cost of mistake → Codex first •🎯 Speed to visible output → Opus first Two models. Very different strengths. Yes, Prompting matters. So does knowing which model won't start making things up when it gets tired. #AIEngineering #AINative #opus #codex #AgenticAI
The Workflow Shift That Changed How I Build Software
I've been coding with AI for a while now, but this workflow shift actually changed how I think about development. I used to open an IDE or a CLI tool and pull up a ticket. It works. But recently I switched to Codex (https://chatgpt.com/codex) a chat-first interface where the entire left panel is just my active projects. Here's what makes it different: I'm usually juggling 3-4 repos at once. I prompt in one project, and while the agent processes, I switch to another and keep working. No tmux sessions. No tracking which terminal belongs to which repo. No mental overhead of "wait, which window was that build running in?" ⚡ All projects visible in one sidebar ⚡ Queue multiple prompts across repos ⚡ Run, test, view diffs, and commit directly from the interface The speed caught me off guard. I'm getting most of my work done this way now, not because the models got better (though they did), but because the UX finally makes sense for parallel workflows. I think 2026 is the year these UI-first AI coding tools go mainstream. CLI tools had their moment and they're still great for certain workflows, but managing terminal history and multiple tabs on a laptop starts to feel brittle. The real shift isn't the AI. It's learning when to take control and when to let it run. Many of us have gotten decent at prompting. We know how much context to give. We know which parts need human judgment. That's when the workflow becomes effortless. One reality check: this workflow amplifies both productivity and mistakes. You need stronger discipline around reviewing diffs because you're shipping faster than your brain can context-switch. The mental model shift is worth it-just don't skip the review step. #AIEngineering #SoftwareEngineering #DevTooling #AIWorkflows #DeveloperExperience
I Rebuilt My Portfolio in 5 Hours. Three Years Ago It Took 5 Days
I rebuilt my portfolio website in under 5 hours. Three years ago, it took me 4-5 days. Here's what I did differently. The experiment: Set up three parallel git worktrees. Gave Claude Opus 4.6, GPT-5.3 Codex, and Gemini the same task - redesign my portfolio using Anthropic's frontend skill. Asked each model for 3 completely different iterations. Got 9 designs in about an hour. The workflow: Gemini struggled. The UI had too many issues to be useful. Codex and Opus? Both impressive. Codex nailed the visual design - one iteration looked so good I immediately knew it could work. But it wasn't functional yet. So I took that Codex design and ran it through both models again: ⚡ Codex: Stayed fast and clean. The code was flawless, structured, minimal but effective. It delivered the MVP beautifully. ⚡ Opus: Went deeper. Built working shortcuts, proper navigation, mobile-responsive details. The decision: After 3-4 hours with each, I chose Opus. Spent extra credits refining it. (Thanks Anthropic for $50 credit) The level of polish shocked me. What surprised me: I didn't plan this website. I iterated into it. We're at a point where development isn't about building from scratch - it's about steering AI toward what you're looking for. 🌟 Live at sushilkamble.com #AICoding #SoftwareEngineering #AIEngineering #DevTooling
## CONTACT.info
// Quick ways to reach me