Implement Stack using Queues – exact question asked at @HashedIn by @Deloitte Single-queue C solution: • push: O(1) – just add to back • pop: O(n) – rotate all but the top element to maintain LIFO • top / size / empty: O(1) Beats 100% runtime on LeetCode. Full code: github.com/ArthKulkarni93/LL… Problem: leetcode.com/problems/implem… What’s your preferred approach — one queue or two queues for amortized O(1)? #CPlusPlus #DataStructures #InterviewPrep

Custom Vector from scratch in C 🔥 Memory allocation, copy ctor, assignment, resizing with doubling, operator[], push_back/pop_back — the full thing. If anyone's bored, roast this code or point out stupid mistakes pls. What should I try next — String? List? Something else? #CPlusPlus #LowLevelDesign #DSA

Memory-efficient doubly linked list using XOR of pointers (advanced, tricky).

Just finished @striver_79's Builder Pattern lecture. Core takeaway: The Builder pattern really shines when you have classes (like Pizza) with a few mandatory fields (e.g., type and veg/non-veg), but also plenty of optional features (like cheese, extra toppings, size). Instead of stuffing everything into one huge constructor or setting default values everywhere, you break the object creation into clear, stepwise parts. You must specify what’s truly necessary and you pick optionals only if you need them. Benefits: - Makes object construction clear and manageable - Helps code stay readable, especially as more options get added When to use: - Complex objects with required and many optional fields When not to use: - Very simple objects with only a couple of attributes In summary: Builder pattern is best when you want strict control over required fields and flexible configuration for optional ones

Just finished @striver_79's Builder Pattern lecture. Core takeaway: The Builder pattern really shines when you have classes (like Pizza) with a few mandatory fields (e.g., type and veg/non-veg), but also plenty of optional features (like cheese, extra toppings, size). Instead of stuffing everything into one huge constructor or setting default values everywhere, you break the object creation into clear, stepwise parts. You must specify what’s truly necessary and you pick optionals only if you need them. Benefits: - Makes object construction clear and manageable - Helps code stay readable, especially as more options get added When to use: - Complex objects with required and many optional fields When not to use: - Very simple objects with only a couple of attributes In summary: Builder pattern is best when you want strict control over required fields and flexible configuration for optional ones