This page collects workplace experiences, questions and discussions submitted by users. Dates shown are submission dates, not periods of employment. Individual reports do not describe the entire company.
Read the community guidelinesNone
It was work experience in the MIS department, developing an ERP system for a hospital.
The manager would ask a question, and if you couldn’t answer it, you had to resign. The problem was that the colleague assigned to guide me was very incompetent; the two managers hadn’t even explained the answer clearly to him in the first place.
The manager wanted me to explain the advantages of opening multiple connections. They were nothing more than these four points:
1. Improve performance and increase bandwidth
2. Connect to different databases or servers
3. Prevent an error in a single connection from causing an interruption
4. Prevent data leakage caused by an information security issue in a single connection
That colleague would only keep saying “No.” When I asked him what the answer was, he couldn’t answer either.
When I showed that colleague code containing “Begin Transaction, Commit Transaction, Rollback Transaction,” he said I couldn’t call it a “transaction.” When I asked what term I should use instead, he told me to figure it out myself.
When I first found the code, I asked him whether it was database-related. He said it was related to programming, similar to a background process that sends emails while updating the database. Two days later, he said it wasn’t—that it was related to the database, involving starting and ending transactions. Two days after that, he said it wasn’t that either, but something simpler. He then said that I had misled him both times before. I was very puzzled about what exactly the manager had told him to make him keep changing his answer. It made me extremely frustrated; I felt that he and the two managers were all playing games with me.
In the end, I gave him a filtered answer to show the manager, but the manager was still dissatisfied and fired me.