There is a strange point in every product journey where things are going exactly right and that's when you can start having a problem. I ran into this recently while working on something I thought was really cool(at least it appeared that way to me :P). If
You have probably been asked about your hobbies at some point. I never had a good answer to that question. Tbh, I still don't. A few years ago, while reading Designing Your Life, I realised something slightly uncomfortable. I did very little just for joy. Most things I
Some time back, I shipped something that made me conscious. I was building a pipeline that generates intelligence reports with AI. Not drafts, not suggestions for a human to polish. A finished report going out at scale with no human in the loop. The whole point of the system was
Japan had been on my bucketlist for a very long time. Naturally, I had expected what people usually talk about - cleanliness, introversion, transport, food, vending machines and many more things. What I did not expect was this strange feeling of calmness during the trip. It wasn't silence, Tokyo
Last week my vehicle started making a sound when I accelerated. Nothing was broken enough to stop using it, but it was clearly not normal. So I went to the service center. The mechanic asked what the problem was. I said there’s some sound. He asked “What kind of
What happened when I tried to write what I know
Monday: “Let’s align on priorities.” Tuesday: “We’re blocked on X changes.” Wednesday: “Let’s push this to next week.” Thursday: “Would it be done by Monday? By Monday morning? At 11 am?” Friday: “Can someone summarize this in the tracker?” By the time the week ends, alignment is
Inside doubts keep it alive. Outside belief makes it matter
Sometimes Product Teams Trip Somewhere in the Middle
The Art of Fixing the Wrong Thing the Right Way
A sudden surge in users is like a workout for your product
Ask before it goes "out of order"
Quality
It's autonomouse QA!
Build
Testing is often perceived as the gatekeeper of products, causing deployment delays. This common misconception overlooks the significant role testing plays beyond merely testing and managing bugs. They are instrumental in shaping a product that users will love. And smoother developer experience. You may be wondering how? Thinking like a
Product
If opening this article would have taken more than 2-3 seconds, you'd probably be annoyed. This is the expectation we have now from anything we use. Whether it’s internet speed, instant Google searches, Netflix streaming, or 10-minute delivery, we demand speed and efficiency. First movers
Product
Imagine taking shortcuts during construction to finish a building faster. While it might be tempting at first, neglecting proper procedures can lead to problems down the line like this: In the product language, these problems are called Technical Debt. For those who don't know what this is. It&
Product
Every customer's question: What Kind Of Product Are You Building?. But in the early stages, focusing solely on the vision can be a recipe for disaster. How can someone understand your GRAND vision if the product itself is still taking shape? Building for the Wrong Reasons If you
Product
General opinion: There's a hyped term - go into the user's shoes and you'll make what they would like. Then, you can run campaigns to verify certain hypotheses, take surveys, have interviews, etc. Or see from analytics what could have happened. Or the best - Once
Build
Which of the following is a safer password? 1. wG1eqe#4D 2. therearemanyunpopularopinions General opinion: 1 is safer because it has capital, small letters, numbers, special characters, etc. It’s harder to break. Probably it will take many months to break it. It is impossible for a person to guess
Quality
General opinion: Five mins? Five days? (Dare I say it) I have no idea, we sit until it’s found out. This must have happened when your production would have gone under crisis. The whole team would have come up forming a crew to fix up. Alternate opinion: If your
Product
General opinion: That’s the feature - planned. It will take me X no of days to implement the feature - implementation. For fixing the mess-ups a day more added - buffer. Deadline: X+1 days. Alternate opinion: If my colleagues at GreyB would be your QA. Bye-bye, your deadline. Your
Build
General opinion: Being in an industry that works with organizations and not with individuals, it is considered to be useful to have their work emails to create a relationship of retention. There’s no whose account is it? disputes and easier handoff organizations. Alternate opinion: In addition to the above,
Quality
Choose one - 60 test case or 10 for one function? General Opinion: More the test cases, better the code. So, 50. Alternate Opinion: If you choose 50, It’s better don’t spend time on writing test cases, just do the development rather - it would be less waste of resources.
Product
Situation: I can access this after being even when my access is revoked. Problem: You missed a check in a function. General opinion: Add the missing condition in that function and push it to production. Time took to fix: A few mins - Quick approach Impact level of the fix: Low