Workplace reviews and discussion: 庫果有限公司

The boss is a tobacco and alcohol wholesaler himself and says he has been programming for a long time.

Yet there are countless problems, and he arrogantly tells engineers how to do things, but everything he says is wrong. When asked to do code reviews, he cannot explain anything coherently. He even teaches engineers how to write error handling, but what he says does not conform to design patterns at all. He still acts smug. The tobacco-and-alcohol guy is laughable.

I was the only iOS engineer in that company. With the project all on my shoulders, I spent three months building the basic shopping-center architecture. There were three Android engineers, while I wrote everything alone. After I finished, they said there were bugs and complained about this and that—what the hell, you’re operations staff, and you didn’t even open dev or QA. What exactly were you testing the bugs with?

Later, Ms. S—the subject of this extramarital affair—said that the original iOS allocation was supposed to be completed by one person in three months, and that they had already found someone to help me. Yet after three months, the chat room still wasn’t finished. That person was one of the three Android engineers. When he first started writing Swift, he could only build screens; I still had to refactor everything he completed. You said you found someone to help, but it still couldn’t be done in three months? Stop saying “LOL, Lao Liao”—it only makes your own incompetence obvious. If you disagree, come argue. Writing all the error handling as hard-coded logic is exhausting. It’s as if the frontend could predict every error message coming from the backend. What an idiot. Use your brains, you two in the Lao Fu–Liao extramarital-affair duo. Don’t just keep saying that the gods said this or that. With this level of intelligence, even the gods can’t save you.

The boss is a tobacco and alcohol wholesaler himself and says he has been programming for a long time.

Yet there are countless problems, and he arrogantly tells engineers how to do things, but everything he says is wrong. When asked to do code reviews, he cannot explain anything coherently. He even teaches engineers how to write error handling, but what he says does not conform to design patterns at all. He still acts smug. The tobacco-and-alcohol guy is laughable.

I was the only iOS engineer in that company. With the project all on my shoulders, I spent three months building the basic shopping-center architecture. Don’t keep saying “LOL, Lao Liao” about supposed bugs—it only makes your own incompetence obvious. If you disagree, come argue. Writing all the error handling as hard-coded logic is exhausting. It’s as if the frontend could predict every error message coming from the backend. What an idiot.