Making Products Successful
Speedy Development, Smarter QA- How GreyB Keeps It Simple
It's autonomouse QA!
Hanisha Arora
Making Products Successful
Building DX - Developer Experience
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
Lean Approach
Band-Aid Product or Scalable Product: Using Testing as Fuel
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 have a
Making Products Successful
How Process Debt Slows Down a 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&
Making Products Successful
The Efficiency Trap - Building Fast vs Building Right
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
Making Products Successful
How can a user design your feature?
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
Lesson Learnt from Bugs
Is complex password safe?
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
Lean Approach
How long does it take to find the root cause of a failure in your system?
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
Making Products Successful
How did you make your feature deadline?
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.
Lesson Learnt from Bugs
Why do many websites ask for work emails instead of personal emails while registering?
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,
Lean Approach
Quality != Test cases Count
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
Making Products Successful
A Problem vs The Problem
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: