Work
ProjectsCase studies, shipped work, and prototypes.Open SourceGitHub, npm, PyPI, and public packages.Hackathons & CompetitionsHackathons, contests, and rapid-build work.Depth
JourneyCareer timeline, roles, and education.AchievementsScholarships, rankings, and milestones.Courses & CertificationsStructured learning, courses, and credentials.SkillsTechnical capability map.This website · 02
Browse this website posts across architecture, delivery, product systems, and the public writing footprint connected to this site.
Zero-downtime deploys on a cheap VPS
Field notes
485 published articles. Essays written here open in place; older tutorials take you back to the site where they first appeared.
Master the interview process for full-stack AI roles. Learn what hiring managers actually test, from agent architecture to production failure modes.
CareerNot on code, and not evenly across the team. A manager's attention is a scarce resource allocated the way any scarce resource is — under pressure, unevenly, and usually toward whatever is currently the loudest failure rather than the quietest risk.
CareerNot raw output, and not how hard the case-writer worked. One of the industry's most-copied engineering ladders names four things explicitly, and scope — evidence the work would have happened without you having to personally push it — carries more weight in that framework than any single technical achievement.
CareerPreparing for a PhD doesn't mean leaving engineering. Here's how I'm building the foundation while staying in industry—and why this path might be worth considering.
CareerThe technical argument for killing it is usually settled early. What isn't settled is that the system is also a team's justification for existing, a defense against being cut, and a source of the coordination cost that gave its owner an effective veto in the first place.
CareerAdvisor matching is the bottleneck. Here's how to signal research fit, write cold emails that actually get replies, and prove you can deliver despite a full-time job.
CareerGoogle spent two years and studied 180 teams trying to find what made some of them work. Individual technical talent wasn't the answer. Whether people felt safe saying what they actually thought was.
CareerProfessors need more than research ideas to ship real impact. What industry engineers actually bring to academic collaboration—and why it matters.
CareerIt's a real framework with a real mechanism, not a euphemism for being likeable. Allan Cohen and David Bradford's model treats influence as trade, and most engineers who have it are running the trade without knowing its name.
CareerPursuing independent research while holding a full-time engineering role is possible—but only if you're deliberate about time management, ruthless about scope, and honest about trade-offs.
CareerMaster the interview process for full-stack AI roles. Learn what hiring managers actually test, from agent architecture to production failure modes.
TutorialInternal tools powered by AI agents can automate repetitive work in days, not months. Learn the scoping, safety, and deployment patterns that work.
AI / MLThe fastest way to waste six months on AI is to scope the assistant too broadly on day one. Here's how to define the first workflow that's actually worth shipping.
AI / MLData quality, permissions, freshness, and lineage decide whether an AI assistant is trustworthy long before the first prompt gets written.
CareerThe strategy deck says one thing. Where the requisitions actually go says another, and the second one is the more reliable forecast — because headcount is the one commitment that's expensive enough to be honest.
CareerThree paths diverge for senior engineers. Only one aligns with your actual risk tolerance, cash needs, and ambitions. Here are the real tradeoffs.
CareerMost mentorship focuses on motivation. The kind that actually develops junior engineers targets judgment. Here's how.
CareerStartups don't need enterprise process. They need a few real standards, clear architecture calls, and leadership that speeds delivery up instead of gating it.
ArticleHow a Series A SaaS company automated lead qualification with intelligent agents, cutting response times by 95% and improving conversion consistency.
ArticleHow a D2C brand reduced customer acquisition cost by automating real-time ad reporting and enabling faster optimization cycles with an AI agent.
Professors don't need enthusiasm from industry collaborators. They need a scoped question, documented reasoning, and respect for the review cycle.
ArticleHow a mid-market B2B SaaS team automated deal-stage validation and activity logging in HubSpot, recovering 600+ hours per year of rep time.
Web DevPerformance problems in large content platforms are almost never one slow query — they're architectural. Here's what actually keeps a Next.js platform fast as pages and teams both grow.
CareerThe strongest interview prep isn't memorized answers. It's two or three projects you can walk through in detail, backed by public work that holds up.
Web DevHow a 60+ person engineering team unified a fragmented three-repository codebase in 18 months without halting feature delivery, using strangler-fig pattern and incremental codemods.
Cloud / DevOpsHow disciplined diagnosis and architectural optimization cut query latency by 12x on a 300M event/day analytics platform.
CareerThe best sign a consulting engagement worked isn't the deliverable. It's that the team doesn't need you back a month later for the same kind of problem.
AI / MLHow a mid-market SaaS company built and deployed an AI assistant that satisfied security requirements without sacrificing capability or user experience.
AI / MLMost AI systems don't fail on model quality — they fail on retrieval, permissions, and fallback logic nobody designed on purpose. Here's what actually holds up in production.
ArticleThree CRMs, conflicting customer records, overlapping deals. How one company unified fragmented data after a merger and restored clarity to sales operations.
Cloud / DevOpsA mid-stage SaaS company cut cloud costs by 42% without rewriting infrastructure—through auditing, rightsizing, and strategic purchasing.
A working notebook
“Some ideas belong here because they connect directly to projects and services.
Older tutorials still live on Medium, where people first found them. This page keeps the trail intact without pretending everything was published in one place.
How I choose a topic
I would rather publish one useful explanation from lived work than five summaries of things everyone already knows.
Step 01
A topic usually starts as the second or third time the same engineering, product, hiring, or research question lands on my desk.
Step 02
I look for a shipped system, a measured result, a failed approach, or a public artifact that keeps the argument honest.
Step 03
Most technical choices touch something else. The useful links are the ones that help a reader follow that chain without opening fifteen tabs.
Step 04
Some pieces belong on this site; others already have a life elsewhere. I keep the original destination and publishing history intact.
Topics covered
The recurring technical and strategic themes represented across this archive.
A quick orientation
The practical details behind this mixed archive.
Those pieces were published there first. I would rather send you to the original article—with its date, responses, and history—than create a duplicate here.
Thirty-five posts are enough to become noisy. The filters separate original essays from outside tutorials, and permanent page links make it easier to pick up where you left off.
Usually. The essays here tend to connect a technical decision to the project, service, or research context behind it. External posts are often narrower, practical guides.
Please do. Real questions are where the best pieces start. Send the context, what you have already tried, and the part that still feels unclear.
Next step
You do not need a polished brief. A bottleneck, an uncertain architecture decision, or a product idea that refuses to become concrete is enough to start.