Month: April 2025

Looking at India from an American’s point of view, there’s a lot to admire: the booming tech space, vibrant culture, and brilliant minds shaping the future of AI, space to explore, and entrepreneurship. But when you look closely into the homes and mindsets of people, there is this shockingly outdated system that still exists: Caste based marriages.

Yes, even in 2025, it’s a thing.

For me and the rest of the world, it’s a concept of the past, but in india, it’s the present and might even be the future. I’m sure many of you are so unfamiliar with the term that the caste system is a centuries-old social hierarchy in India that was supposed to be abolished legally. However, it still has a huge impact on how people live and whom they marry. And this isn’t just about aunties with traditional preferences in india. There are literally entire matrimonial sites designed to help you find somebody who is from your own caste. We’re talking Tinder, where you swipe right only if they match your caste, no vibes, no compatibility checks or filters. That’s what has been happening.

Here’s what caste-based matrimony looks like today:

• IyerMatrimony.com – For Tamil Brahmins looking for a partner who can quote Sanskrit shlokas and write Python.
• RajputMatrimony.com – Where your royal bloodline matters more than your degree.
• NadarKannalam.com – A hyper-specific matchmaking site for a very specific Tamil caste.
• YadavMatrimony.com – Cows, caste, and compatibility.
• AgarwalMatrimony.com – Where commerce, caste, and community collide.

It’s really crazy to see a country that prides itself on for being a global tech superpower building the backend for Silicon valley, yet, clinging to a medieval social system it comes to marriage and love.

And before you say that “Its just culture or beliefs”, no. Culture evolves and adapts; this is something on a whole new level. Saying “I want my kid to marry someone without our caste” in 2025 is like saying I want my child to marry the person who has the same wifi provider, it’s not a tradition, it’s bias but with a new user interface.

What is even more confusing is how normalised all of it is. Caste filtering isn’t being done behind the curtains; it’s very openly advertised, like a feature rather than what it is, a big red flag. It’s basically discrimination disguised as a family rule.

Come on, India. You’re better than this.

You’re so advanced to send rockets to the moon, but can’t cross the line of caste for marriage? You can run huge global companies, but won’t let your daughters marry somebody they want to? Something isn’t working right here.

If India truly wants to lead the world, this is not just a social issue; it’s about credibility. The great Indian innovation should not be about AI for caste-based matchmaking. It should be about unlearning the caste system altogether.

Because real progress isn’t just about code — it’s about courage.

Let me start with a small disclaimer; I love engineers, i respect what they do and i really think without them nothing could really work in this world. They run the show of different ideas being turned into reality, they build houses, write the code and make all thre magic happen.

But, they shouldn’t design.

I’ll tell you why, and it’s completely justified. Design isn’t about perfecting things; it’s a mindset switch that allows creativity to flow. And honestly, many engineers dont have that in them, some of them do, but that’s fine if they dont.

Design is a lot about emotions, storytelling, empathy, and intuition rather than logic. It’s about seeing the world from another point of view, not just the eyes of the system. It’s about asking why before jumping into how. And Engineers are mostly always obsessed with the how

See, when an engineer is presented with a problem, they will solve it meticulously, with beautiful and minimal lunes of code. But they oftent tend to solve the wrong problem, or they solve in a way which makes sense only to them, not the person who will use it. Have you ever used a feature that has worked technically but always felt like a design that is not human enough. That’s what happens to engineers’ designs.

There’s a lot of difference even in the values of a designer and an engineer; engineers value structures, predictability and technicality. On the other hand, designers live in ambiguity, exploring the messy parts of their product, taking feedback, and chasing half-felt hunches. While designers seek to open up, engineers seek to narrow down. Engineers try to reduce the complexities, and designers are in love with them.

And let’s not even get to the aesthetics part of it. I’ve seen so many UI designs from engineers that look like they were built for the early 2000s, using very minimal colours which nobody could like. Pixel alignment? Not a concern. Font hierarchy? “What’s that?” Icon spacing? “Bro, it works, right?”

To be fair now, there are unicorns here as well, people who are brilliant at both design and engineering , but its really rare. Like, Bigfoot-on-a-unicorn rare. Most engineers aren’t wired to think like designers. And they shouldn’t have to be.

When designers and engineers get together, great products are created. But if they try to do the others job, then its a complete failure. The best engineers push fpr performances, scalability and functionality. They understand what is essential and make it seen. Both the professions are utmost important and require deep focus for great outcomes.

But please — let designers design. Let engineers build.

And let’s stop pretending those are interchangeable skills.

This doesn’t come from a hate towards design, nor that I dont value empathy, solving problems, or a strategic approach. However, design thinking has gone from being used as a human-centred approach to understanding issues and coming up with solutions to an overhyped and corporate buzzword that only promises innovation and delivers one-fourth of it.

Ive seen many meetings where somebody stands up saying “let us appy design thinking to this” and then we are all standing in front of two big white boards, drawing sad sticky figures of the users and figuring out their emotions, like we are making a Pizar movie. Then spend hours brainstorming wild creative ideas and giving ourselves a cheer on the back for putting “if we can or how we might” infront of every sentence.

It feels good. It feels collaborative. It feels like we’re solving world hunger.

But 90% of the time, nothing actually gets built.

Design thinking pretends to be a process; in reality, it’s about performance. It’s simply a justified way to look busy, sound more creative, and avoid doing anything risky. But authentic designs are messier, uncomfortable, and challenging. Nobody actually seems to be thinking about the users; just to look busy, we are willing to pretend to think about designs. It puts creativity in a box with five stages and assumes that brilliance is bound to emerge if you follow the proper steps. Sorry to break it to you, but it won’t.

Empathising? That is great, unless, like most teams today, they are printing out some random fake personas and guessing what they want and like, rather than talking to them.

Define? It usually becomes a mission statement with just buzzwords rather than clearly articulated problem statements.

Ideate? Reduced to a one-and-a-half-hour session filled with post-its that dont solve anyone’s problems.

Prototype? A Figma file that no one ever opens to have a second look at.
Test?? At what time? By the end of Friday, we’re all ready to order pizzas and check Netflix shows to binge-watch.

What gets on my nerves the most is how design thinking gives people the illusion of progress. It’s so comfortable, controlled which is why it feels so easy to do and often neglected. But its so completely divorced form the realit of product building, the risk taking parts, making mistakes and stumbling into ideas by learning from mistakes, not just diagramming the hell out of a prototype.

Give me a scrappy builder who talks to users and iterates fast over a “Design Thinker” with a

Sharpie and a Post-it any day.

Designs aren’t just a five-step process; it’s a craft. It’s about your intuition, failures, feedback, and relentless interaction. The sooner we build, test, and learn, the better for us, rather than hiding behind design thinking sessions that aren’t taking us anywhere.

Rant over.

Let’s talk about affordance, the mythical UX principle that says, “You should’ve just known how to use this.”

Affordance is a design that can get you to do something without needing instructions or a set of rules on how to do it. Like a handle on the door that suggests pulling or a button that allows clicking. A touch screen that invites you to swipe, double tap, rotate, etc.

In simple theory, an affordance is the design that speaks for your actions.

In practice, it’s the design that mocks you.

The Norman Door: Your Daily Humiliation

I’m sure we have all been through that awkward moment where we “pushed” a door that says “pull” and laugh it off. That’s totally not on you; that is afforance or, rather, a lack thereof. Designers have a term for it, “Norman door”, after Don Norman, a man who wrote an entire book about everything from light switches to teapots, is gaslighting us. So, if you have ever yanked a “push” door like you’re trying to rescue a child from a burning building, congratulations, you are NORMANIZED.

Digital Affordance: Where Buttons Go to Hide

I remember the time when buttons were like actual button? raised , shadowed, outlined and gentle “click on me” vibe? Now it feels like buttons are texts, floating in the air or on a blank canvas. Makes you wonder is this clickable or is it just decorative.

You hover over it, nothing happens, you click and yet nothing happens. Makes you feel like you want to cry out to the world. God forbid if you are alone trying to figure it out, youll be stuck figuring out how to use it rather making the best use of it.

Modern UI designers say, “Let’s make it minimalist.” What they mean is, “Let’s make it impossible.”

Common Affordance Crimes

• Flat buttons: Are they clickable? Are they labels? Are they ghost energy? W
• Hamburger menus: Somehow theyre always hidden.  Sometimes they’re in the top left. Sometimes they’re in the bottom right next to your credit card info. Always ambiguous.
• Microwave touchscreens: Want to reheat pizza? Good luck navigating the “Choose Your Heating Style” maze. There’s a “Power Level button”, and no one knows what it does.
• Gestures: Swipe, pinch, tap, drag with two fingers while whispering ancient Greek—UX in 2025.

These modern interfaces require a secret ritual before we start using them.

Affordance: Where “User Intuition” Means “Guess Again”

Designers always say “we believe in user intuition”, but what they really mean is that “we didnt label anything , its your fault you’re lost” Affordance has basically become the design version of “You should’ve read my mind.” If it works, the designer is a genius. If it doesn’t? You clearly just don’t get it.

It’s Not You. It’s the Button That’s Disguised As Air

Affordance was supposed to make things easier. Instead, it’s become the perfect excuse for bad design. “Oh, you didn’t know you had to double-tap with two knuckles while standing on one foot? Weird. It’s so intuitive.”

If your fridge, app, or smart toilet requires a tutorial, the only thing it’s affording is chaos.

But hey — maybe that’s just the user journey.

I’ll just say it — I hate data-driven design.

I’ll be honest: data is everywhere today, and piles of numbers are taking over the essence of design and vision. This isn’t coming because of hate towards data or because I dont believe in listening to the users. However, even the parts of design that should be guided by taste, instinct, and vision are somehow taken over by data.

Nowadays, every design decision seems to need a justification in the form of an A/B test, a heatmap, a conversion rate chart, or some “insight” from a dashboard. It’s no longer enough for a designer to say, “This just feels right.” That’s treated like heresy in modern product teams. If the numbers don’t agree, your taste doesn’t matter.

And that’s a problem.

Many of the best designs in the world did not come from testing 40 shades of blue or measuring CTR; it came from people with a powerful and willing point of view. People who valued aesthetics and understood its real worth. People who made some courageous decisions, not because data told them, but because they believed they were creating something worth believing in.

Data-driven design kills exactly that, it trains designers to aim for whether or not this will perform, rather than if it will inspire. It encourages safe choices, not bold ones; it rewards familiarity and not originality. You usually end up at the interface that is optimised and soulless. It struggles to incorporate the necessary feedback and human elements. Every button is placed where the heatmap says it should be. Every colour is chosen because it converted 0.2% better in a test. And everything starts to look the same.

I think great designs arent just about efficiency, they are all the emotions, contexts, storytelling anf even a little bit of drama. Some random surprise elements, delight and beauty is all it take to create these moments. But whrn it needs to be justified with metrics or charts, there is no room for that . Data measures everything very crucially and theres no reward here for nuances, it flattens out everything into what gets more clicks.

What gets worse is that data-driven designs kill trust within the teams. Designers aren’t seen as creators but as UI mechanics waiting for instruction from analysts and PM’s. A vision slowly becomes something that we are told isnt scalable.

Of course, we can’t ignore data; look around everywhere, and you will only find data around you. However, what we need to stop doing is that the data is suitable for designs, but it’s not!!. Designs cannot be reduced to numbers, and sometimes the best design choices are the ones that dont win the A/B tests because it makes people feel something. Because it makes us think and has a soul.

And that should still matter. It should matter the most, as much as anything else.

Blog post which inspired me to write this post – link

I still rememebr the first time i played a Flash game on my school computer, it was so smooth, colourful and felt like magic in my computer. Adobe flash was everywhere back then, games, animations, websites and even on youtube videos. There came a point where the internet was unimaginable without Adobe Flash.

Flash actually began in the mid-90s as FutureSplash Animator, later acquired by Macromedia and renamed Flash. Adobe took over in 2005, and that’s when Flash really hit its stride. As a teenager exploring the internet, I was amazed by what it could do. You didn’t need to install heavy software, just load a webpage and boom, instant video or game.

Newgrounds and Miniclip became my daily destination websites, and I even tried out Flash for myself, animating stick figures and building simple games. It was an empowering experience; Flash gave people hope that they could do anything with the internet. It made regular people create content and share, making us feel interactive and alive.

Slowly, over time, the cracks started showing. Flash’s upgrades got more frequent and annoying. Computers started to become slow, websites were down constantly, and there was news about security concerns. Then came the game changer: Steve Jobs rejected Flash in 2010, citing its inefficiency and lack of security. Now, one of the biggest mobile companies, like Apple, rejecting Flash was a massive blow. I didn’t realise then, but it was the beginning of the end. The internet was going very high, the web was mobile, and Flash couldn’t keep up.

Slowly, developers shifted to HTML5, which did many of the same things, such as animations, videos, and interactive websites, but without plugins and problems. Everything for flash started disappearing and Adobe announced its end in 2017 and by the december 2020, it was no where in the face of the earth.

It was a heavy goodbye for me. On the one hand, the web has become faster and safer every minute, making it more accessible. On the other hand, a whole era of creativity and video games was gone.

Thankfully, projects like Ruffle are helping preserve old Flash content.

Flash may be dead, but its legacy is unforgettable to people like me who grew up with it. It was more than a plugin; it was a doorway to a more creative, expressive internet.