βDo. Or do not. There is no try.β β unless weβre in a spike branch, then trying is encouraged.
Iβm interested in building systems that scale like the Death Star (minus the exhaust-port vulnerability) and stay online longer than a phaser on stun.
Observability should feel like a lightsaber β elegant, not clumsy or random. I boldly ship what no deploy has shipped before, with resilience as Prime Directive #1. I chase LeviOsa-level precision in APIs so production never goes full Dark Arts. One does not simply walk into prod without tests, rollback, and a fellowship of code review.
Senior Software Developer at BEES / AB InBev β I help keep the digital tap flowing: same discipline whether the payload is bytes or barley (and yes, the backlog pairs well with hops).
I'm Graduated in Computer Science and have a Software Architecture specialization β basically leveling up from hobbit to wizard tier, one pattern at a time.
Reach me out on LinkedIn for more information.

