6.5 · Field feedback

Level 6 · In practice

6.5Field feedback

Goal: remember the principles repeated by practitioners, and dismiss the misconceptions.
Estimated time: 9 min · If you only have 5 min: read “The essentials in 30s” + the diagram.

The essentials in 30 seconds

  • Understand: joins and grain explain 90% of wrong totals — push the work to the source.
  • Prove: a wrong report is worse than none — cross-check, parameterise, test under real conditions.
  • Doubt: preview OK does not mean report OK — check the PDF and the real volume, no myths.

Farès thread — what the quarter taught him

After one quarter, Farès sums up his practice in Algiers in five sentences: understand his data model, push the work to the source, never distribute without cross-checking, parameterise everything that varies, test under real conditions. And four myths shelved: the preview is enough, more colours is better, performance is tuned at the end, do everything in Crystal.

Keep one principle and dismiss one myth: that is how experience settles in.

What practitioners keep repeating

Beyond features, a few principles keep coming back among those who produce statements every day.

✓ Do

  • “Understand your data model”: joins and grain explain 90% of wrong totals.
  • “Push the work to the source”: filtering and aggregating server-side changes everything on large volumes.
  • “A wrong report is worse than none”: always cross-check before distributing.
  • “Parameterise everything that varies”: one generic model beats ten copied reports.
  • “Test under real conditions”: what runs fast on 100 rows can collapse on one million.

✗ Avoid

  • “If the preview is fine, the report is fine” — no: check the PDF and a real volume.
  • “The more colours and charts, the better” — clarity comes first.
  • “Performance is tuned at the end” — it is designed from the connection and joins on.
  • “Do everything in Crystal” — sometimes an upstream SQL view/command is far more robust.
Common misinterpretation: “this feedback is quotes”. No. This is an anonymous summary of widespread good practices, not attributed words: for nominative opinions, rely on real, sourced references.
Text version of the diagram (SEO / screen readers / translation): Experience cap: 1) Understand — data model, joins and grain first. 2) Push — server-side filter and aggregation, upstream SQL view or command if needed. 3) Prove — generic parameters, systematic cross-check, real-condition test and PDF check. 4) Dismiss — preview confused with proof, excess colours, performance postponed to the end, systematic all-Crystal. Lesson: a wrong report is worse than none — experience means cross-checking and testing.

Ready-to-say script — talking like a practitioner (30 s)

“My data model: [tables and grain understood]. My filter: [pushed to the server, SQL checked]. My statement: [generic through parameters, cross-checked, tested on a real volume with PDF checked].”

Copy-paste template — practitioner routine (5 lines)

practitioner_routine = {
  "data_model": "joins + grain understood",
  "source_work": "filter + aggregation server-side",
  "generic": "parameters {?Mois} / {?Region}",
  "proof": "cross-check + real-volume test + PDF",
  "dismissed_myth": "preview / colours / perf-at-the-end / all-Crystal: ..."
}

Small business / tight budget

One principle per quarter is enough: data model + cross-check first, the rest next.

Algeria SME

Adapt to local closes: cross-check against accounting and real-volume test every month.

Remote / hybrid

Prioritise written traces at a distance (verified SQL, cross-checked figure, checked PDF, dated).

Cross-cultural

Prioritise local transposition as soon as codes differ: question peers, compare practices.

Caution: Generic reminder: this feedback is an anonymous summary of good practices — not attributed quotes; for nominative opinions, rely on real, sourced references.

48h challenge — apply tomorrow

Apply 1 practitioner principle (data model, source work, cross-check, parameters, real test) to your current statement and dismiss 1 myth.

Section exit checklist
  • I know the 5 practitioner principles and the 4 myths to dismiss.
  • My practitioner routine (model, server, proof) is started.
  • I have done the 48h challenge or scheduled its date.
Self-assessment 1-5: clarity of my principles?myths dismissed?
Check your understanding

Farès wants to progress like the practitioners. What does the field say?

💡

Experience cannot be bought: it is built by cross-checking and testing, statement after statement.