Is he actually that good?

The commit history is public and the debugging notes are checked into the repo. Draw your own conclusions.

What's the tech stack?

Next.js 15, React 19, TypeScript strict, Tailwind + DaisyUI, Zustand, Hasura GraphQL, better-auth, PostgreSQL, ClickHouse, Playwright, Vitest and Cloudflare Workers. Plus whatever the incident requires.

Why is he saluting in the photo?

The build passed on the first try. It happens roughly once a quarter and it deserves a salute.

Can I get him to review my PR?

Yes. Bring the reproduction steps, the actual error and what you already tried. He will find the other thing that's broken too.

Engineering · VPN Super

Cristina 2ships it to production

Full-stack engineer. Next.js, Hasura, Cloudflare Workers, Recurly webhooks and the occasional 2am production mystery. Peer-reviewed as "annoyingly thorough".

Finds the root cause, not the symptom
Writes the regression test before closing the ticket
Documents the gotcha so nobody re-debugs it in six months

See the track record Read the FAQ

Why you want him on the ticket

Six things that keep showing up in the commit history.

Root-cause discipline
A mobile subscription silently replaced by a web one looked like a root-device bug. It wasn't. It was a Recurly handler linking the wrong customer three steps earlier.
Knows the difference between ?? and ||
An empty string beat the fallback chain and wiped a customer link. One operator changed, one class of bug gone.
Cross-platform paranoia
Caught a git pathspec that silently matched nothing on Windows because cmd.exe doesn't strip single quotes. The tool reported success the whole time.
Reads the whole file
When a ticket named one broken i18n namespace, he grepped for the other three in the same route and fixed those too.
Writes it down
Every non-obvious debugging win ends up as a documented symptom, root cause, fix and gotcha. Future-you says thanks.
Never pushes without asking
Commits freely. Stops at the remote. Authorization does not carry across tasks — a rare and underrated virtue.

Bogdan vs. a regular Tuesday

Entirely objective. No conflicts of interest whatsoever.

The situation	A regular developer	Bogdan
Flaky test in CI	Re-runs the job	Finds the race condition
"Works on my machine"	Ships it	Boots a Windows VM out of spite
Webhook fires twice	Adds a dedupe table	Deletes the duplicate client-side call
Weird production log	Marks it as noise	Traces it to a locale folder name
Ticket says one bug	Fixes one bug	Fixes one bug, flags six more
Friday 17:55	git push --force	Asks first. Always asks first.

Cristina 2ships it to production

Why you want him on the ticket

Root-cause discipline

Knows the difference between ?? and ||

Cross-platform paranoia

Reads the whole file

Writes it down

Never pushes without asking

Bogdan vs. a regular Tuesday

Frequently asked questions

Got a bug nobody can reproduce?