DEVELOPMENT METHOD

From a change to a tested result

Define the goal, make a focused change and test it on the target hardware. Keep enough evidence for someone else to follow the work.

01 / RESPONSIBILITY

Who does what?

I choose the goals, hardware and preservation criteria. I make the project decisions and perform the final device testing.

ChatGPT assists with programming, calculations, debugging, automation and documentation.

02 / TESTING

Start from a known source revision and configuration. Keep changes small enough to inspect and compare.

A build check confirms that an executable was produced. Device tests check its controls, image, sound and behaviour.

Keep these results separate. A working build is the start of testing, not the end.

03 / CONTINUITY

Source control stores revisions. Test records identify the build and conditions. Handovers record decisions, open questions and the next step.

Keep private game data and signing keys separate from public source.

04 / AUTOMATION

Use scripts for dependency setup, builds, file checks and repeatable measurements. Test the scripts before relying on them.

Visual quality, sound and control feel still need hands-on evaluation. Preserve useful failed experiments so their lessons can be reused.

05 / KNOWLEDGE

Start with the question an article answers. Explain the decision and result before adding implementation detail.

Keep one main explanation for each topic. Link summaries to it and update them when the evidence changes.

Use short paragraphs and clear terms. Put important limits beside the result they qualify.

06 / SOURCES

Describe ordinary hardware facts directly. Add a product link where checking a specification is useful.

Credit upstream code and identifiable contributions by name. Link measured results to their test records.

Use formal references for quotations, research findings and distinctive borrowed ideas when needed.

07 / PROJECT GUIDES