Engineering notes
Practical thinking for long-lived technical systems.
Articles about the decisions behind dependable embedded software, device integration, verification and modernisation.
Seven questions to answer before rewriting an embedded system
Security, user needs and investment should guide the choice between targeted fixes, component replacement and a new architecture.
Read the articleDiagnostics are part of product design
Useful logs explain the failure and its context. Meaningful severity and documented retry policies guide recovery or intervention.
Read the articleTesting failure and recovery in embedded systems
Link measurable requirements to unit tests, automated simulation and device evidence, with explicit failure handling and release criteria.
Read the articleWhy publish
Technical judgement should be inspectable.
A technology list says what somebody has touched. Clear technical writing shows how they reason about constraints, risk and operation. These notes make Scorpex’s engineering approach easier to evaluate before a project begins.
Suggest a technical question