|
|
|
|
|
|
by novax81
4708 days ago
|
|
|
The amount of "Not knowing what people are doing" in large companies is rather alarming. I used to work at a company with about 700 employees just in the building I was in, and had turned in my two-weeks-notice due to the low amount of responsibility/work I was being given (bad management). During my last two weeks I of course had even less work, literally just one task to take care of and it would only take me about an hour. So I sortof just chilled and got my things in order for a few days, deciding to log into the server and take care of the job on Thursday. So, Thursday comes and I try to get on the server... no response. A little more testing and the server looks like a dead box. I ring up IT and ask them to look into it, getting an email a few minutes later stating that the machine had a crash on Sunday night (4 days ago) and just hadn't been properly rebooted. As I logged in to do what I had intended to, it dawned on me that the department right next to mine had literally no other tasks right then except to be testing software on this server. Yet I, who had been putting off doing the work for 4 days, was the first to find out the server hadn't been working all week. This sort of stuff is what makes small companies where your contributions matter feel even more rewarding. |
|
|
Testing is so easy to fluff over. I did a mobile banking project (Project A) for my current employer and the business area said they needed 3 weeks to test it. The person assigned to test it was also assigned to test another project simultaneously (Project B). She would tell me she didn't have time to test Project A because she was testing Project B, and she would tell the Project B people she didn't have time to test because she was testing Project A.
In the end, I looked at the usage logs on the test site... she logged in on the last day of the three week period, futzed around for 5 minutes and then signed off on the project as "fully tested - no issues".