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.
CareerIn bright rooms, light mode was rated more comfortable; in dim rooms, dark mode was. But a controlled reading-performance study found no significant difference in reading speed or comprehension between the two. Comfort and performance turned out to be two separate questions with two different answers.
CareerA meta-analysis of 78 studies and 254,037 people, ages 6 to 39, found near work raised the odds of myopia by 21% in adults. But most of the underlying research is on children, myopia progression in adults was far slower than in kids, and the evidence is almost entirely observational — correlation, not a randomized test of cause.
CareerThe American Optometric Association recommends 20-28 inches for a computer screen. Research on viewing distance found closer viewing widens the eyes and increases evaporation, independent of anything else — but a study testing font size specifically found no significant difference between symptomatic and asymptomatic users. Distance and size don't carry equal evidence weight.
FinTechHow a boutique fund eliminated spreadsheet-based portfolio risk tracking, building a precomputed metrics pipeline to handle 50+ positions with sub-minute latency.
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.