Search for a command to run...
Hands-on technology leader with 10+ years building scalable, mission-critical systems at Goldman Sachs, Brevan Howard and fast-growing fintechs. Expert in cloud-native architectures, distributed data pipelines and high-throughput systems; experienced in migrating legacy platforms and designing AI-enabled services. Proven track record delivering reliable platforms that process millions of transactions daily.
No comments yet. Be the first to comment.
It’s an Exoskeleton, and That Changes Everything Most people are thinking about AI the wrong way. They imagine it as a coworker:Something you assign tasks to… wait for… and hope it delivers. Sounds re
I didn’t wake up one day and decide, “AI will change everything.”My journey into AI was slower, messier, and honestly… a bit reluctant at first. If you’re a builder, engineer, or curious technologist,
Imagine a programming language designed not just for humans but also for AI.Not adapted for AI. Not retrofitted. Built from scratch so AI can read and write it easily. That’s exactly what NanoLang is. It’s a tiny, experimental language created by vet...
Most PostgreSQL optimization guides feel like laundry lists of settings and indexes. But real performance gains often come from clever ideas, not just the usual tricks. Let’s unpack a few of those ideas in ways that actually make sense for you. These...
Remember when we defeated pop-up ads? Yeah, they're back. And this time, nobody's fighting them. The Good Old Days (Of Terrible Ads) Back around 2000, the internet was a warzone. Visit any website and BAM!!! random windows would explode onto your scr...
One of the important topics in programming courses is error handling. Usually, they talk about what is an error and explain stuff like try/catch/finally and in the case of more advanced courses they explain about resource cleanup. But after learning these techniques that your programming language gives you, as a Software Engineer you have a responsibility to decide "what to do" in case of error. I have seen many cases where they just "throw" the exception and that is the easiest thing you can do. But is it always the best thing?
There are four ways you can handle an error that happens during program execution and you need to consider all the factors and make an informed decision in each scenario as to what is the best way to handle the error.
One common part in all of the above cases is logging which usually happens with any error handling scenario. Errors are important and you should log them so that by inspecting the operational environment you can understand how the application is running and what kind of errors are regularly happening. This information can help you improve your code and/or the operational environment.
Note that you sometimes need to mix multiple approaches. For example, you may retry in case of error, if it fails again try to fix it and if it still doesn't work, terminate the process.
The point is, in each case you have to consciously consider the context and determine what is the best way to handle the error.