Published on (UTC)
This post was submitted by a user and reflects their personal experience or opinion. The publication date is not an employment or interview date.
None
I do not recommend joining the Systems Department. I used to work there. The first-level supervisor had a very short temper and extremely low EQ. When he lost his temper, he would yell and curse at employees, but after investigating, at least four out of five incidents were usually caused by problems in his own code. Before writing code, he never drew flowcharts or architecture diagrams, nor did he write any comments. The most laughable thing was that this “technical” supervisor, despite having more than ten years of experience, wrote code with SQL injection vulnerabilities. He did not properly close database connections either, causing several of 104’s internal servers to require periodic restarts. He hard-coded all parameters into the program instead of reading them from configuration files. Not knowing how to use frameworks or understanding MVC architecture would have been bad enough, but he also forced you to write programs his problematic way. He constantly played both sides: in front of others, he would say that he imposed no restrictions on what technology you used and would let you use anything, but as soon as he turned around, he would yell at you: “Didn’t I tell you not to write programs this way!!!” When he sensed that your technical abilities surpassed his, he would deliberately make trouble, intentionally curse and yell at you in front of the second-level supervisor, and create the false impression that you had caused him problems. When he was in a bad mood, he treated subordinates as punching bags, verbally abusing them and even making personal attacks. During my employment, I completed two projects. I handled everything, including backend programs, scheduled jobs, monitoring programs, the system administrator platform, all UML documentation, cross-department communication, and contacting vendors. Then one day, his persecutory delusions flared up. He spent the entire afternoon repeatedly pressuring me, asking, “Are you planning to take the projects I’m in charge of?” No matter how I explained, he kept repeating the same question until the end of the workday. I thought it was over, but the next morning, when he saw me at the office, he called me into a meeting room, closed the door, and continued questioning me. Unable to endure his pressure any longer, I resigned on the spot. As soon as he heard I was leaving, he flew into a rage, accusing me of being ungrateful and saying that he had once helped increase my salary by NT$2,000, yet I did not know how to repay his kindness. He then began threatening me, saying that I owed him a personal favor and forcing me to repay it. Afterward, he went to complain tearfully to the second-level supervisor who backed him. After hearing him out, the second-level supervisor felt that he had been wronged, so he called me into a meeting room……and suppressed me a second time…… The final conflict occurred shortly before I left, when there was one last deployment request. The deployment time was later changed, but the first-level supervisor did not notify me. On the afternoon after the deployment, the company’s QC team came to me and said, “Give me the code. I want to see whether you put any programs in it that could endanger the company’s systems……” Then the Planning Department also called to complain, asking why I had deployed something without authorization! And that first-level supervisor yelled at me as well: “What the hell are you doing again!”…… It was not worth it. All I can say is that working at 104 was truly not worth it. You do everything, yet the people above deliberately frame you and make you take the blame. After the project is completed, he gets the credit. In the end, my contributions to both projects were taken, the first-level supervisor who threatened me was promoted, and he and his backer jointly forced me to resign. When I left, I was still carrying a pile of accusations against me……