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...
When you write a piece of code, you inevitably need to use memory. To keep track of the data you care about. This data can be list of customers, contents of a file, input from the user or anything. Unfortunately, the amount of available memory is not unlimited. So when you program is running, you can't keep everything forever there. So how should we solve this problem? There are two ways:
The second approach, needs a Garbage Collector to do the job. This GC is a piece of code which is already provided by the language and handles all the memory management for you, so you can focus on the code you write and not managing computer memory.
The problem is, GC needs to do a lot of processing. It needs to keep track of all memory allocations, and the references to those allocations in your code. Note that there can be N references to a single block of allocated memory. GC needs to take care of all N references and it can only return the memory to OS when all those references are no longer valid in the code. As a result, GC will need to stop your application (for a few milliseconds) and do the job (check memory allocations, check references, mark those allocations which can be returned, return those marked allocations). These few milliseconds can be really expensive in some cases (for example for low latency applications or real-time processing).
Java has introduced a new type of GC which tries to use concurrent techniques to make keep this overhead minimum. It is a new experimental GC algorithm and you can check here for more information.