Blog
Long-form, code-heavy writing on software engineering, AI/LLM, payments and system design.
The four objects that carry a production service, annotated line by line: probes that don't lie, honest resource requests, zero-downtime rollouts, HPA caveats and the boring starter kit that ages well.
Both sides of the wire: HMAC signatures with timestamps and constant-time compares, the raw-body trap, dedupe-and-queue consumers, producer retry etiquette and the checklist that prevents 3 a.m. replays.
Notes on a peer-reviewed tour of ML, neural networks and deep learning in healthcare — FDA-cleared realities, the limitations section everyone should read, and the practices worth stealing for any high-stakes system.
The whole idea in twenty lines of PyTorch: neurons, layers, backprop as a feedback loop, the architecture zoo in one paragraph, and what it actually means for people who ship software.
e-Fatura vs e-Arşiv, SOAP clients that behave in modern .NET, UBL-TR mapping without tears, the status lifecycle, cancellation rules and a go-live checklist from real ERP integrations.
From the while-true-Task.Delay era to clustered schedulers: persistent job stores, misfire policies, timezone traps, idempotent job design and the observability layer everyone skips.
Why I keep coming back to Graylog for self-hosted log management: the GELF setup, structured logging from .NET and Laravel, streams that route and alert, and the retention math nobody does.
When cluster number two arrives, Rancher stops being a dashboard and starts being a hiring decision you skip: RBAC done once, Fleet GitOps, K3s at the edge, and the rules I learned the hard way.
A candid comparison from someone who has operated both: the philosophical split, the same pipeline in Jenkinsfile and .gitlab-ci.yml, where each tool still wins, and one rm -rf war story.
Adapty handles paywalls and receipt validation; your ASP.NET Core backend owns the truth. Idempotent webhook handlers, the server API for profiles and promo grants, and access levels as roles.
