Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
monkeyboy490126dDon't worry about it. It's pointless and absurd to concern yourself about things that you don't think about. The whole point of a review and of QA is to acknowledge that one person probably can't think of every case.
groenkek174126dTake a break from the piece of code. 'Forgetting' (for a lack of better wording) the thing you're working on gives you a new perspective. Do you duck it?
Fast-Nop10765126dI guess I'm probably some sort of bastard half-brother of @Floydian because I've been off in testing for seven fucking years, which taught me to see my own code in new ways.
Basically, devs look at their code with "how it works" glasses. Testers and reviewers, however, instead think "ok, what do I have to do to make that code break?" That's the key.
sladuled6252109dTry to be an asshole to your app, helps a lot. Not all clients are assholes, but they often try out what they can do with it, especially if your user manual sux.. So just think about WWDD - what would deedee do?! Press the button, drag the button, open form, close it, open again, try to apply, change mind midwork, cancel action... You know, try clicking really fast to see the results..maybe they change?!
And yes, having another set of eyes helps, I always ask my coworker to try to break it before I even mark it as ready for testing..
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job