The bench deck, read aloud

Six rounds on the fan deck

Kunming Fanbi E-commerce Co., Ltd. offers six standing rounds of computer integrated systems design work. Each round has a written start rule, a written finish rule and a named bench lead, and each one can be booked alone or stitched into a full cycle that runs from the first blade to the last wire. The descriptions below are the same words the crew reads from every morning.

We work from a bench room at Unit 2, Room 705, Building 3, Zhicheng Homeland, Fengning Subdistrict, Wuhua District, Kunming - 650000, China (CN), and we keep the pace of the room deliberately slow because careful work cannot be hurried.

Blade Set Desk

The blade set desk is where every engagement begins. We take the client estate apart on paper, name each functional module, and give it a seat in the deck: a purpose, an owner, a data contract and a clear place in the flow of work. A module that cannot earn its seat is retired, and a module that belongs to another system is returned rather than quietly adopted into the deck. The desk produces the seated module list, a one-page map that every later round will reference when the crew needs to know what is inside the frame.

The desk is also where we agree on the scope of the first cycle. Clients often arrive with a long wish list and a short budget, and the honest answer is rarely to do everything at once. We cut the list into rounds, place the most fragile modules first, and agree on the finish rule for each round before any work is scheduled. The seated module list is signed by the client and the bench lead together, and it lives in the run ledger from that day forward. Nothing leaves the desk until the map is complete and every blade has a seat.

Ledger Fan Rounds

Ledger fan rounds are our scheduled walk through the entire stack, read from the oldest record to the newest, so that drift in one layer cannot hide behind a healthy reading in another. On each round the crew reads logs, metrics, change records and open tickets in order, and writes a short entry that names what moved, what stayed and who signed off. The round is deliberately unglamorous, and that is the point: it catches the small changes that no incident report will ever mention.

Rounds run on a cadence agreed with the client, usually weekly during a project and monthly after handover. Each entry goes into the ledger with a plain description of the system state, a note on any component due for another look, and a short list of questions for the client. We do not soften findings. If a module has drifted out of its band, the entry says so, and the next round begins by checking whether the reported fix actually held. Over a year the ledger becomes a reliable history of the system, which is worth more than any single dashboard.

Draft Band Weeks

A draft band week is a dedicated block for tuning the airflow of a system: cache behaviour, queue depth, message size, retry policy and the pace of background jobs. We measure the draft rather than the peak, because a system that moves its load comfortably on an ordinary day is the system that survives a hot afternoon. The crew sets target bands in advance, works through the parameters in the order that gives the largest gain with the least risk, and stops as soon as the bands are met rather than chasing the last few percent.

The week closes with a draft sheet that records the chosen operating bands, the reasoning behind each setting and the conditions under which the bands should be revisited. Clients receive the sheet alongside a short briefing, and we encourage their own engineers to sit in for the final day so the reasoning transfers rather than staying with the bench. Draft band weeks are often booked after a motor swap, when the new drive is seated and the airflow needs to be recalibrated around it.

Motor Swap Days

Motor swap days replace the drive behind a workload without stopping the desk that depends on it. A drive in our vocabulary is a platform, a database, a runtime engine or any component whose replacement affects the whole frame. The crew writes the swap sheet before the first component is unclipped: every step, every dependency, every checkpoint and the exact moment at which a rollback would be called. Clients can watch from the spare chair, and we recommend that at least one client engineer does.

The swap runs in stages, each with its own balance check, so that a problem is caught while the old drive is still warm and the rollback path is still short. We keep the old configuration documented until the new one has run clean for a full cycle, and we never retire documentation on the day of the swap. The day closes with a read-back of the swap sheet, a fresh fan sheet for the new configuration, and a note in the ledger that records what changed and why. There is no big bang cutover on our bench.

Balance Run Sessions

Balance run sessions test a system the way it will actually be used, with the ratio between read and write, burst and lull, and morning and evening set from real telemetry rather than a vendor chart. The crew builds the scenario, runs it against a copy that matches production closely enough to be honest, and reports vibration the way a technician reports vibration in a fan frame: small numbers, plainly stated, with no drama and no smoothing.

Each session produces a short report that lists the bands tested, the readings observed and any component that fell outside its expected range. Where a reading looks surprising, the crew repeats the run before writing it down, because a single odd number is more often a measurement artefact than a real fault. Sessions are booked before a swap, after a draft band week and whenever a client plans a change in workload. We treat a clean balance run as the licence to move to the next round, and we will not skip it to save time.

Wiring Check Evenings

Wiring check evenings are quiet after-hours reviews of the joins between services: interfaces, credentials, certificates, network paths and the small connections nobody notices until one of them loosens. The crew works through the seated module list from the blade set desk and checks each join against its documented contract, then updates the diagram wherever reality has drifted from the drawing. The evening is intentionally unhurried, and the room is quiet enough that a loose join has room to show itself.

Every check ends with a diagram revision and a list of joins due for another inspection in the coming quarter. We photograph nothing and we record everything in text, because a diagram that can be read in ten years is worth more than a picture that only makes sense to the person who took it. Wiring check evenings are the last round of a full cycle and the most popular one for clients to attend, since they show the system as a whole rather than as a list of separate components.

How the rounds fit together

A full cycle runs through all six rounds in a fixed order, though clients can book a single round when that is what the estate needs. The order matters because each round relies on the record left by the one before it, and skipping a round leaves a gap that shows up later as a mystery in a balance run.

Round one

Blade Set Desk

Map the estate, name each module and agree the scope. The cycle starts with a signed seated module list.

Round two

Ledger Fan Rounds

Walk the stack in order and write the first ledger entries so later changes have a baseline.

Round three

Draft Band Weeks

Tune airflow against real load and record the operating bands in a draft sheet.

Round four

Motor Swap Days

Replace the drive components in stages with a rollback seat held open throughout.

Round five

Balance Run Sessions

Verify the new configuration against realistic scenarios and report the readings plainly.

Round six

Wiring Check Evenings

Close the cycle with a review of joins, a diagram revision and a handover note.

Book a round on the bench

Send a short note about your estate and the bench lead will reply with the next open slot and a plain estimate of what the round will take. We answer every enquiry within two working days.

Contact the bench