Software engineer. Debugger. Builder of things that usually behave in production because I have already argued with them in staging.
- Make backend-heavy systems less mysterious.
- Build product features end-to-end without acting surprised when edge cases exist.
- Move between React, TypeScript, C#, Go, Java, and server-side glue code without needing a dramatic transition period.
- Debug issues that begin with "this should not be possible" and end with "okay, now it makes sense."
- Help teams ship reliably, review sanely, and panic less.
const ayush = {
mode: "shipping and investigating",
strongestMove: "debugging complex systems",
enjoys: [
"production mysteries",
"backend architecture",
"feature ownership",
"mentoring people",
"turning vague bugs into boring fixes",
],
frontendEnergy: "calm and intentional",
backendEnergy: "let me see the logs",
codeReviewStyle: "kind, direct, and allergic to avoidable nonsense",
};Languages: JavaScript, TypeScript, C#, Go, Java, C/C++
Frameworks: React, Next.js, Vite, Express.js
Passive Buffs: ownership, reliability, debugging patience, production empathy- Untangling messy bugs in large codebases.
- Owning critical features without making them everyone else's long-term problem.
- Translating product ambiguity into technical decisions.
- Supporting junior engineers without turning mentorship into theatre.
- Keeping systems maintainable after the exciting part of shipping is over.
Building software, helping build teams, and trying to keep my GitHub profile at the exact intersection of competent and unserious.
function summonAyush(topic) {
if (topic.includes("debugging") || topic.includes("systems")) {
return "I am already interested.";
}
if (topic.includes("building") || topic.includes("product")) {
return "Let's talk.";
}
return "Still probably let's talk.";
}If you want to collaborate, hire, build, fix, or just compare notes on engineering pain that became engineering taste: