MoMo (M_Service)

Geeks for Geeks(GFG), 2025-26 I was someone who always used to think clubs are just time waste and returns nothing back in the initial phase But i was wrong, The day i joined GeeksforGeeks Student Chapter - Bennett University my career slope growth was exponential. All Thanks to Shubhi Singhal | Mrigank Bhatnagar | Saurabh Singh | Gyanendra Prakash | Akshej Gupta for giving me this wonderful team ❌ family ✅ for life. What i feel for GFG, i feel the same for no other club. Saurabh Kumar Tiwary | GeeksforGeeks Student Chapter - Bennett University | Shivam Rai | Ishant . | Satveek Gupta | Tanzil Gupta | Prabhavi Gupta | Sahil Goyal

Using AI more hasn't made me ask "where am I headed?" anymore — it's made me ask something sharper: what can I build right now that actually gets me there? My first job was Technical Support for Windows OS at Microsoft. The mindset of building a system and continuously improving it has quietly shaped how I work ever since. I don't have any standout edge. What I do have is the ability to see the big picture and describe in detail what's actually inside it, then execute with impact measurement. Organizations and projects have their own history and their own spirit — and almost none of that gets written down anywhere. Understanding context and where it comes from can get my AI prompt better, more or less 😉 So what I'm trying to build isn't speed or output volume with AI. It's clarity around the things that stay vague: 🔹 Are emails and meetings actually focused on the problem that needs solving — or just circling the surface? 🔹 If this doesn't move forward — what's the cost of delay, and which trade-offs are being quietly ignored? 🔹 What should the spirit of the product and the user experience actually feel like? The deeper into the details, the better. 🔹 Don't dismiss the "crazy idea" — with AI, things can be messier and bolder than before. 🔹 Run small, distinct experiments quickly to see the quality of output and how things actually respond. My current stance on AI: bet on it, use everything available, accept the calculated consequences. Not reckless decisions. Just trying something small every day, following it all the way through, and seeing where it leads.

How NOT to do digitalization. This morning I went to The Coffee House and they rolled out a new self-ordering process on a tablet. Self-service sounded like a good idea until it took an employee 3 mins just to help me find the item I asked for on the UI. And when the ordering app asked for my phone number “to verify the order” I decided I had enough despite feeling kind of bad for the employee. Ironically since The Coffee House changed owners a lot has changed for the better, but it goes to show how easy a good offline setup can be sunk by a half-baked digital experience.