SI Developer Story
#9. After joining the SI project - The start of full-fledged development

After joining the project and going through an adaptation period, you will be fully involved in development. Development is carried out in accordance with the schedule of WBS based on the functions listed in the RFP (Request for Proposal). In SI, it is assumed that functions can be changed at any time, so the degree of coupling with other modules is kept as loose as possible.

This is because the client who commissioned the project knows their own work, but they cannot provide implementation guidelines such as what functions are needed and how the screen should be configured. Therefore, it is very common that additional requirements or changes are made after showing the developed screen.

Therefore, if the degree of coupling with other modules is high, it is necessary to modify other modules to modify one module, which can lead to unexpected side effects, resulting in messy code duplication.

The goal of SI is to make it work somehow, so clean code and efficiency are a low priority.

At first, you may be eager to make it well, but with a tight schedule and requests from the client who keeps giving you additional requirements, you will soon find yourself developing quickly.

Also, some clients just sit back and expect you to make it since they paid the money. This is a prelude to the hellgate that will open up at the end of the project, so if you don't know anything about your work, ask and organize it as much as possible.

Keep the following points in mind when developing in SI.

• The content can be changed at any time.
• The client doesn't know anything. Get frequent feedback by showing them one screen at a time.
• Don't say Yes to additional requests unless they are absolutely necessary.
• I am not Bill Gates. Customers prefer screens that are made quickly over well-written programs.