*QA chick tries to run software
*software doesn't start / throws an exception
*she does chmod 777 *
*still doesn't work
*blames developer

SHE DOES A FUCKING CHMOD 777 ON EVERY FUCKING FILE AND FOLDER LIKE THIS IS SOME BLACK MAGIC FUCK

@Alice when u ls the whole server glows green omfg

Yeah I used to do that..(black magic)

Personally when things stop working my favorite black magic is the classic rm -rf /, isn't it such a lifesaver?

“rm -rf /“ is not enough, you should use “rm -rf /*” or “rm -rf / —no-preserve-root” instead ;)

@falkebo You're right! I must be behind the times 😛

@falkebo hope she is not on devrant and dosen't see this. otherwise we are doomed.. thank you guys.. :D

In her mind: CHMOD == poof...

I mean, as QA your supposed to blame the developer, and chmod 777 maybe worked for her in the past (for her specific setup it might even be necessary to give correct file permission, 777 is easy and fast and insecure... Which for a closed off QA testing isn't a problem)

At least she can use `chmod` and somehow tries to handle the problem...

@Ignisor there a fine line between trying and making it worse.

Perhaps they should try to figure out what the problem is before doing anything....

@incognito she is supposed to be able to configure and start the software. most of these errors came from a configurational cause which has nothing to do with the developer. every configurational error was logged nicely, she did this everytime without opening a logfile and looking for the actual problem.

chmod -R 777
the fix for everything.

@falkebo dd if=/dev/zero of=/dev/sda bs=4M status=progress

@vortexman100 thats the way to go :D