Muteen K

Lets talk about Composition in the OOP paradigm. Not sure if you heard about this one rule: COMPOSITION OVER INHERITENCE Now that i understand it deeply enough, i can't help but agree with this rule. Its one of the most underrated rules in software design. Inheritance tells you what an object IS. and, Composition tells you what an object DOES. But first things first, why should you stop abusing my boy "Inheritence" - You want a banana (one feature). Instead, inheritance forces you to pull in the gorilla and the entire jungle (bloated parent states). - Real-world requirements change fast. If you build a rigid parent-child tree, a single product pivot can shatter your entire codebase. - Change one line in a master class? Congrats, you just broke 14 subclasses downstream. So, how to fix this sh*t: Stop thinking in rigid structures. Start thinking in plugins. Build small, independent, swappable components and inject them. Basically, Design your code like LEGO, not a concrete sculpture. With composition, instead of defining what an object is (e.g., class Dog extends Animal), you define what an object does by assembling independent building blocks. Check examples: 1) Inheritance approach 2) Composition approach

@avrldotdev How bout a state machine, which works like a checklist. I've built something similar before, where we keep checking llm states and if we reach any state where the llm is not moving forward or moving in the wrong direction, we end the state machine and kill the llm along with it

Had to reject a candidate coz they couldn't answer this: I asked: our research agent completes some requests in 30s while some take 8-10min. Looking at the logs, it's stuck in a loop wasting 1000s of tokens. How'd u fix this? explain ur process. They replied: I'd add MAX_ITERATIONS & TIMEOUTS. I countered: That prevents an infinite loop but the agent still wastes 100s of tool calls before hitting the limit. How'd u eval that the agent isn't making any progress much before timeouts? What'll you answer in their place to not get rejected?

History has been made people 🙌🏻

Its a really big moment for indian space & tech. sector which was pretty much limited to ISRO for so long. Kudos to @SkyrootA 👏🏻

@kayleecodez Please enlighten me with some articles too 🫩🙏🏻

@mk0x0FF your suggestion is also good but ngl structured concurrency is more clean rn. im exploring more about it thesedays.

revisiting structured concurrency after reading through some of the async roadmap. one thing that stood out: in sync rust, calling a function gives you a pretty strong guarantee. when it returns, the work it owns is done and its resources have been cleaned up. detached tasks quietly weaken that guarantee. a function can return while work it started is still running somewhere else. that means the function boundary no longer tells the whole story. you now have to understand task ownership, cancellation, shutdown and failure propagation outside the function itself. that's why i think structured concurrency is much more than task trees or cancellation. it makes function boundaries meaningful again. the code that starts the work is also responsible for waiting on it, handling failures and cleaning it up. looking at the current async roadmap, this also explains why so much of the effort is around scoped tasks, reliable cancellation and guaranteed destructors. it feels less like adding async features and more like making async preserve the same reasoning model that already makes sync rust easy to follow

@kayleecodez Yes + a few working professionals actually i'm working as a freelance mentor with Geeksforgeeks

@mk0x0FF you taught college kids?

Just had a 3 hour session of teaching java functional programming 🫩 It was fun but tiring as hell at the same time. No energy left I really want to work on my projects, lets see in the evening now

Another one of my old sketches

@archiexzzz @SarvamAI Congratulations man 👏🏻

update: researcher at @SarvamAI 🫡

@zadoyngx @archiexzzz Well can't disagree 🫠

@mk0x0FF @archiexzzz more streetshitters

You don't want to miss this. Register for Sarvam Epoch fast, India's Frontier AI conference!

@kunalbuilds_x 🤯🤯🤯🤯 logic = 100

@mk0x0FF Okay 🤣!! btw I thought chhore with a padgi whould be odd, like Haryanvis don't wear those pagdis.

Find the odd one out (2 Marks)

@kunalbuilds_x nah, its either sonpapdi or sondaas

@mk0x0FF chhore one

@emii_iime @TrisH0x2A This one's also a great book but its way too detailed to prepare for interviews, it takes time to digest this book

@mk0x0FF @TrisH0x2A

OS in 1,000 Lines teaches you how to build a Unix-like operating system in just 1,000 lines of C despite its size it includes process switching virtual memory with paging a shell a filesystem and a disk driver every feature is built step by step with real code you can run and experiment with for comparison Linux was around 10,000 lines when Linus Torvalds first released it in 1991 one of the best resources for understanding how an operating system comes together from scratch

@anurag__kochar 🤣🤣

hypocrisy of women

@YashJRathod @IAmManware Yeh gender wala angle toh maine socha hi nhi, "he" mera default hai 🤣 i meant "he/she"

@mk0x0FF @IAmManware i don't think ke koi ladka itta efforts dalega notes mein

college notes of a gold medalist

@narayandwi30232 @coughkaa Yeah sure, it was funny 😹

@mk0x0FF @coughkaa opinion matters

@triorDeep woh toh birth right hai 🫩🙏🏻

@mk0x0FF illiteracy and bakchodi krne ki adat☝🏻

Lmao listen to this guys😭🤣 So there's an uncle in our colony (from RSS) who told me to join his open gym instead of the gym I currently go to. I asked, "Hmm okay... but why?" He goes: "In closed gyms like yours, when people exercise, the place gets hot. Because of the heat, O2 (oxygen) breaks down and turns into 03 (ozone gas). Breathing ozone is bad for your body, so you'll face a lot of health problems later." Brooooo😭😭😭🤣, you are also a tution teacher, really?