Disclaimer

It's a space where I share stuff I found when partnering with testers to understand why they think developers are nuts and with developers to find out why they curse testing.

Both of these entities can work together when they advocate the product instead of developer/tester biases. Hence, they can use testing in their journey of making ROI faster for the product.

The practice ground

Anywhere that can help in proving,
Work done == Building features
Efficient work done === Creating product

What's special?

I share my alternate opinions with the opinions that exist in the developer's tech world. It could be finding ways to use a feature in a not-so-right way, test strategies, and road maps to certain ways in testing. I don't listen to you until you built X with care.

Who this is not for?

If you have any of the following traits, press the close button on the tab or press Ctrl + W.

• You're good with things working on your system but not others
• If you have a command button on your keyboard (because this is only vim friendly)
• You think everyone can test
• Keeping the same password - a hard one - everywhere it's called THE security for you
• You will always test in production
• You think you know testing
• You think your website is safe
• Your code is working as your expected code
• You're coding for bots
• You love your code. (believe me don't let my content give you a mid-life crisis)