Tester Or Developer: Two Very Different Relationships

Content 6 MONTE Welcome to BeeSV.com Jazz up boring old CS files by replacing the commas with the entire Bee Movie script Paste CSV id,firstname, lastname, email, email2, profession 100, Berget,Schenck,Berget. Schenckyopi Converted BeeSV idaccordingtoallknownlawsofaviationthereisnowayabeest 100accordingtoallknownlawsofaviationthereisnowayabee 101accordingtoallknownlawsotaviationthereisnowayabee Paste BeeSV Converted CSV

Content AskReddit EI CM 14h What is just a placebo effect but most people don't realize? 53.2k 17035 comments L hibikikun 4479 8h Loading spinners on web pages. I once had a user complain to me a web app was too slow (and it was pretty fast). So I tested him by making the animation spinner spin much faster. He went to my boss to praise me how much faster the web app was. (spin.js is what i was using)

Content Hand-writing a set of both normal test cases and edge test cases Assuming the end-user won't do anything too crazy, and only writing normal test cases Creating a program that generates random test cases Hand-writing test cases for the program that randomly generates test cases Writing a program to generate test cases for the program that generates test cases Assuming your code is perfect to begin with, and not writing anv test cases at all

You know that developer who actually admits when something doesn't work instead of closing the bug ticket with "works on my machine"? Yeah, companies appreciate those mythical creatures about as much as they appreciate a pool without a swimming animation. The brutal truth: honesty in software development is like that pool—looks inviting, technically functional, but you're not allowed to use it because someone didn't budget for the proper implementation. Better just stand there and pretend everything's fine while QA drowns in production bugs. Management says they want transparency until you're transparent about technical debt, missing features, or why the deployment actually failed. Then suddenly it's all "can't you just make it work?" Sure, let me just swim in this pool real quick.

Your perfectly optimized codebase is just lying there, minding its own business, when some developer decides to implement "a new feature" that's about to wreak absolute havoc. The code was running fine for months until management decided users needed the ability to export data as interpretive dance GIFs. Now you get to watch your beautiful architecture get beaten to death with the stick of progress.

Content Debugging ticket from Testing Telling them cosmic ray flipped a bit inside NAND made with mematic