In Java, when an object is no longer referenced, it becomes eligible for garbage collection, and the JVM eventually frees the memory automatically.
In C++, many people believe there is no automatic memory management because developers traditionally use new and delete to manually allocate and free memory.
However, C++ provides something called Smart Pointers.
A smart pointer is a special type of pointer that manages heap memory automatically. It holds ownership of a dynamically allocated object and ensures that the memory is freed automatically when the pointer goes out of scope.
This helps prevent common issues like memory leaks and incorrect manual delete operations.
If you’re genuinely interested in understanding how smart pointers work and why they are so useful, give this blog a read. It’s one of the best explanations of smart pointers in C++.
Blog: https://t.co/6XejaqslUH
The final nail in the coffin of CS fundamentals.
Most devs have been writing SQL their entire career.
They can query. But they can't explain why it's slow.
That's the gap nobody talks about.
"CMU 15-445 – Database Systems by Andy Pavlo" fixes exactly that. 25 lectures. Free on YouTube.
It covers everything happening beneath your queries:
• Query execution – what actually happens after you hit enter
• Buffer pool management – how databases pretend RAM is infinite
• B-Tree indexes – why your index gets ignored and your query dies
• Query optimizer – how the DB silently rewrites your SQL before running it
• Transaction isolation – why "just wrap it in a transaction" is never enough
This isn't another "write better SQL" tutorial.
This is databases "the way senior engineers actually understand them."
"Wish someone had shown me this earlier."
Save it. Complete the series.
Paid to attend a hackathon.
Travelled cities
Slept 2 hours on plastic chairs
Mentors said “add AI”
WiFi said “no”
Food said “survive”
Code said “segmentation fault”
Judges said “this is not even a problem” 🙃
Wallet said “never again”
Congrats me for funding my own bad luck 💀
Daily Log ✅
• Revised Flexbox properties 🎨
Spent time revisiting layout fundamentals today.
The basics always matter more than they seem.
2026 is going to be my year 🔥
#BuildInPublic
Daily Log ✅
• Solved 1 GeeksforGeeks problem 🧠
Solving just one question took a lot of time today.
Feels uncomfortable — which probably means real learning is happening.
2026 is going to be my year 🔥
#buildinpublic
Daily Log ✅
DSA:
• Solved 2 LeetCode problems 🧠
DEV:
• Revised CSS basics 🎨
• Built a simple landing page for practice🧩
2026 is going to be my year 🔥
#buildinpublic