You can use a well known template like ARC42 and insist on the maintenance of suitable indexes for agent access and review for coherence on a regular basis.
Ultimately any useful documentation needs active curation.
Getting devs to do this well is hard. Agents can be driven to do a fair job through suitable prompt frameworks and repetition eg as PR reviewers.
I’ve had reasonable success with a combination of space dimensions structured requirements and component based indexes and time dimensions of decision records and commits.
Also a strong design model to give common structure - hex arch with ports and adapters and pure business logic.
You can absolutely build robust products using agile. Apart from some of the human benefits of any kind of incremental/iterative development, the big win with Agile is a realistic way to elicit requirements from normal people.
This was definitely something I picked up from science education. Basically a technical journal.
These days I split between technical notes a write and store on the project git so others and the AI tools can read - eg architecture decision records, bug reports etc and then a separate personal linear time journal of what I’m doing / thinking/ task lists meeting notes etc, often with links to the project specific docs. Great for searching. What I miss from paper is ability to quickly sketch diagrams.
Sigh. Urban expectations. Come live in the sticks where I do and pay £35/m for about 15Mb. Actually had to go Starlink to be able to work from home properly. Swish fibre came round a few years ago and dug up all our roads and put fibre to all the phone poles but then vanished and nothing has happened since.
The US is so far out of line with the rest of the mostly civilised west it astonishes me. We know how this will go. Officer claims felt life was in danger (it wasn’t, and well over by the time he shot), investigation will drag to drop from popular consciousness, DA will say nothing to answer, civil prosecution, private settlement, nothing changes.
I think if you want the benefits of living in a country then you should be willing to defend it. This attitude of entitlement without responsibility is exactly what gives migrants a bad name.
Fun signal processing project and all the sampling problems sound typical. Unless this is just for your bike, given that some of the pokey fours run up to 15k rpm ~ 250Hz primary, I think it would be a lot easier to use a significantly higher sample rate and then treat in the digital domain. If you can recognise the engine speed and signal as a reliable pattern (use a digital PLL?) you might be able to subtract it and get more of the chassis signal left. As another poster pointed out, if you could do a motorway run with a high sample rate you have a good dataset to experiment with, including seeing how far you could downsample and still get appropriate sensitivity and selectivity.
Ultimately any useful documentation needs active curation.
Getting devs to do this well is hard. Agents can be driven to do a fair job through suitable prompt frameworks and repetition eg as PR reviewers.
I’ve had reasonable success with a combination of space dimensions structured requirements and component based indexes and time dimensions of decision records and commits.
Also a strong design model to give common structure - hex arch with ports and adapters and pure business logic.
YMMV