Growth Notes from a Junior Client Developer

When starting a task, you should check with the person in charge first and keep verifying whether your understanding and implementation direction align. In particular, if you interpret the design intent differently, you may have to redo the work from scratch, so it's important to build the habit of asking about and recording any questions right away, from the design stage through completion and verification.

It's a good idea to keep videos or screenshots of intermediate results. Not only do they serve as material for sharing the implementation direction, but they also become a reference point for checking the original behavior later when refactoring or extending features. The same applies when modifying another developer's code — you should first understand why the code exists and in what context it was created.

For data modifications, it's safer to request them through the planner whenever possible. Game data such as quest content or stats is often interconnected, so even changing a single value requires considering the rules, translations, and management procedures involved.

The client should always be designed with the assumption of potential network failures. You need defensive logic tailored to the situation — whether to retry on request failure, whether to halt subsequent processing, or whether automatic re-entry is needed — and you should also prepare fallback measures, such as an emergency exit button or automatic re-requests upon reconnection, in case a failure traps the user from progressing in the game.

In live service, you need to handle resources with an understanding of the difference between builds and AssetBundles. Even if you remove a variable from the code, the live build or an AssetBundle prefab may still reference that variable, so unintended behavior can occur if you don't check the actual scope of deployment. Ultimately, the most important attitude is to share trial and error with the team rather than hide it, and to improve so it doesn't happen again.