A Lighthearted Guide to Starting a Coding Project for Fresh Graduates

Everyone may have read too many martial arts novels.

Today a curious reader asked: "Hello, how should I start writing code when I receive a new requirement?"

I replied with a chuckle.

The typical process for a fresh graduate looks like this:

Change clothes, maybe put on a cosplayer outfit.

Do the technical selection and write a technical proposal first.

Find someone to review the proposal.

Start drawing diagrams and designing core interfaces and architecture.

Develop according to the flowchart.

After development, find someone to review the code.

Write test cases.

Finish everything in one go, then submit for testing and go live.

Now you ask me again.

I basically just sit down, start typing wildly to get a feel for the keyboard.

After about a short period I’m in the zone, push the code to a pre‑release environment, run it on live data, and check the results.

Test cases are often forgotten.

Then I go downstairs for a milk tea, wander the supermarket, and maybe have a meal.

Because I know plans never keep up with change, the backend part is okay. In the data development stage you never know what strange problems you’ll encounter.

Technical proposals? They’re only useful when making a PPT.

Need to join a big‑data technical group? Add me on WeChat: whispererrr, the group has senior members with better practices.

Below are some recommended big‑data resources:

Eight Thousand Miles of Cloud and Moon | From Zero to Big Data Expert Learning Path Guide

What Are We Actually Learning When Studying Flink?

193 Articles Smashing Flink – A Collection You Should Follow

Flink Production Environment Top Challenges and Optimizations – Alibaba’s Classics

Flink CDC – My Take on It and the Online Issues