I am a Software Engineer & Tech Consultant with Financial Expertise, specializing in building scalable and secure systems while leveraging deep financial knowledge to drive business success. My experience includes developing robust IT architectures, designing blockchain-based solutions, and providing strategic technology consulting that optimizes systems for performance and cost efficiency.
My strong background in finance, supported by certifications like CFA and FRM, enables me to deliver data-driven insights that optimize operational efficiency. I bring a unique blend of technical innovation and financial acumen, ensuring that my solutions are both technically sound and strategically aligned with business objectives.
Here's what I've been working on and thinking about
When integrating multiple external systems, treat each integration as an independent strategy and use a factory to select the implementation at runtime. Differences stay isolated in their own implementations; the main flow only cares about ‘who to call’ and ‘how to orchestrate’.
These three mechanisms solve different problems at different layers: distributed locks protect business execution, row locks protect data mutation, and transactions define lock scope and atomicity.
Treat recent search history as ephemeral user behavior, not core business data. Redis Sorted Sets provide a natural fit: O(log N) writes, automatic ordering, de-duplication, and bounded size—all without turning a lightweight behavior signal into a database concern.
A clean, layered, and cloud-native foundation for managing infrastructure both locally and in the cloud. Separates provisioning, orchestration, persistence, and automation into modular layers.
Node.js runs one event loop per process—only one CPU core is used. To scale, use Cluster for multi-process or Worker Threads for multi-thread. Both enable parallelism, but in different ways.
async/await doesn’t make code run in parallel. It’s syntactic sugar over Promises that makes asynchronous logic read like synchronous flow, working by pausing and resuming execution through the event loop.
When integrating multiple external systems, treat each integration as an independent strategy and use a factory to select the implementation at runtime. Differences stay isolated in their own implementations; the main flow only cares about ‘who to call’ and ‘how to orchestrate’.
These three mechanisms solve different problems at different layers: distributed locks protect business execution, row locks protect data mutation, and transactions define lock scope and atomicity.
Treat recent search history as ephemeral user behavior, not core business data. Redis Sorted Sets provide a natural fit: O(log N) writes, automatic ordering, de-duplication, and bounded size—all without turning a lightweight behavior signal into a database concern.
A clean, layered, and cloud-native foundation for managing infrastructure both locally and in the cloud. Separates provisioning, orchestration, persistence, and automation into modular layers.
Node.js runs one event loop per process—only one CPU core is used. To scale, use Cluster for multi-process or Worker Threads for multi-thread. Both enable parallelism, but in different ways.
async/await doesn’t make code run in parallel. It’s syntactic sugar over Promises that makes asynchronous logic read like synchronous flow, working by pausing and resuming execution through the event loop.