Behind the build
How Testers Can Help Build Scalable Products: A Shift-Left Approach
A sudden surge in users is like a workout for your product
Behind the build
Building a product isn't about just coding. Creation looks cool until it creates experiences. It's lots of things outside coding that lead to a useful product.
Behind the build
Speedy Development, Smarter QA- How GreyB Keeps It Simple
It's autonomouse QA!
Behind the build
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
Behind the build
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&
Behind the build
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
Behind the build
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
Behind the build
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.
Behind the build
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: