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.
1. The schedule is often just wishful thinking.
They say 4 weeks, but in the end it always turns into having to finish it in 4 days.
2. When there are problems with cross-module integration, everyone pretends nothing is wrong. Newcomers don't know how to investigate, they can't get the source code, and the PM doesn't understand the architecture either. They tell you to figure it out yourself. They suggest using objdump or ADA to disassemble other people's binaries.
You have to save your own module yourself.
3. The computers are unbelievably terrible! The Trojan, however, is very powerful. Every time you open a new file, it starts a thread to service it, using up 25% of the CPU. In the end, it takes 10 seconds just to open a file.
When you're in a hurry, it really makes your blood boil.
4. They give you a huge pile of things to do, and if you make a mistake, they review your work and tear you apart. It's best not to agree to work casually; agreeing only brings trouble upon yourself.
5. Setting up the environment is extremely troublesome and often takes half a day. The strangest part is that when you find someone to help fix a bug, you also have to set up the environment for them. Why do I have to set it up myself too?
6. The managers are pretty nice, and my coworkers are also very capable, but there is just so much work and the schedule is so unreasonable… Even a god would have trouble saving this situation…