Workplace reviews and discussion: 整技科技股份有限公司

1. There are daily stand-up meetings as well as weekly meetings, so issues can be reported immediately.

2. Outsourcing is used for coding. Engineers only need to write the system documentation -> outsource the work -> wait for testing.

3. There is afternoon tea every other Friday.

4. There is a snack cabinet that you can rummage through when you get cravings.

1. The product is actually a modified copy of a project developed in the past, repurposed as a product. It is highly coupled, and adding just one field can cause the entire function to

stop working. I once raised this with the RD department, but they only replied, "Create another table without changing the Table Schema at all."

This also means the outsourced team has to spend a lot of time studying it.

2. The underlying layer is controlled by RD, but in fact, only one self-taught engineer with insufficient skills is responsible for maintaining it. In addition, RD does not maintain some product components at all. If there is a problem with an underlying component, you can only fend for yourself.

3. The project schedule is extremely tight; more than thirty functions are expected to be completed within two weeks.

4. Because no deposit was paid when signing the contract with the outsourced team, and there was no early-completion bonus, the outsourced team's willingness to work is low. The coding quality is left to fate. In the worst-case scenario, the entire team at the outsourcing company may resign collectively, requiring us to renegotiate the project schedule with the new engineers hired by the outsourcing company.