Sales Engineer

Bhasha - Duolingo for Indian Languages 🦚

Hey guys, working on my next app. Wanted some feedback on the app logo for Bhasha - Duolingo for India. Problem - Design a logo which can represent Indian languages in a more interesting and eye catching way so more people will be intrigued to explore and learn about it. Idea - Represent the diversity of the Indian cultures and all it's languages with different colours while the mascot is the Indian national bird, a peacock. What do you guys think? What improvements can I make? Where and how can I make it more user friendly so people will be interested in it? Should I even make it?

Actor Siddique Seeks Anticipatory Bail

- **Malayali Actor Siddique** has approached the **Kerala High Court** for anticipatory bail after an FIR was filed against him for **rape and criminal intimidation**. - The complainant alleged that Siddique called her to **Muscot Hotel in Trivandrum** under the guise of discussing a film and then raped and assaulted her. - The complaint was submitted to the **Special Investigation Team** probing sexual harassment in the Malayalam film industry. - A decision on the anticipatory bail plea of **actor-legislator M. Mukesh**, also accused in a rape case, will be made on **Tuesday, September 3, 2024**. - The **District and Sessions Court, Ernakulam** held in-camera proceedings and will reconsider the case on Tuesday, with the court previously preventing Mr. Mukesh's arrest until September 3.

How to Waste Six Months: The Absurdity of Our New AI Feature

I’m 31 working as a product designer I’ve been working on our core application for nearly 3 years. We launched our biggest update this Wednesday. Sounds like a major milestone? It’s not. The feature is a brutal wake-up call. It made it painfully clear how lost our leadership is. We added an AI-generated motivational avatar to a basic B2B data dashboard. I don’t know why we did it. Our users want faster load times. They want better data export. What did we give them? A virtual mascot that smiles when metrics go up. I spent six months working hard. Nights, weekends, you name it. But not smart. I said yes to every absurd requirement. I chased appreciation instead of pushing back. I stuck to the roadmap so hard that I now have a joke of a project in my portfolio. Two of those six months were spent arguing over the avatar's eye color. In the remaining four, I treated user feedback like a nuisance. I ignored upskilling. I chose the comfort zone over challenge. And I paid the price. When I finally saw the live user reactions today, I realized it wasn’t worth building. Not because I didn’t work. But because I didn’t work right. I worked for the ego of our directors, not for the users. This isn’t a sob story. I’m not fishing for sympathy. But here’s why I’m writing this. Let me be your cautionary tale. Don’t waste your potential on useless hype features. Don’t stay stuck in the comfort of “busy work.” Don’t avoid speaking up. Don't assume a trendy AI tag will carry your product forward. It won’t. It’s now just a bloated piece of code I can’t even put on my resume. If you want to grow, you have to get uncomfortable. You have to take risks. Otherwise, you’ll end up like me. Realizing too late that you’ve spent months building nothing for yourself. I am the architect of my own wasted time. I built this failure with my own hands.