Notes on building
software that lasts.
A publishing surface for Pripsus product notes. The structure is in place and ready for content; nothing is published yet, so nothing here pretends to be.
How structural decisions early in a project determine how expensive change is later.
Turning a business requirement into a scoped, buildable, testable product increment.
Where automating a process pays off, and where it only hides an unclear process.
Versioning, releases and maintenance as part of the product, not an afterthought.
Designing interfaces for people who use the same screen several hours per day.
Modelling data so reporting and integration do not require a rewrite.
Topic areas only. No articles are published yet — this page is prepared for content management rather than filled with placeholder writing.
No notes published yet.
When notes are published, each one becomes its own page with its own metadata. Until then this section stays intentionally empty rather than carrying invented expertise.