Technology, explained.
A practical reading companion. Start with the concept, then follow the linked documentation when you need the detail.
Real-time computing
A deadline is part of the job.
In real-time computing, finishing within a defined deadline is part of the requirement. This is not the same as raw speed. Look for the timing conditions, not only a throughput figure.
QNX Software Development Platform 8.0 (opens in a new tab)Quantum annealing
Define the problem before judging the answer.
An annealing workflow starts by expressing a problem as an objective function, then sampling for low-energy solutions. D-Wave’s documentation distinguishes quantum, classical and hybrid samplers. The label “quantum” alone does not describe all the work performed by a complete application.
Basic workflow: formulation and sampling (opens in a new tab)Headless architecture
The interface and the service are separate.
A headless storefront uses APIs to connect a custom interface to commerce services. Shopify documents Hydrogen as one way to build that interface; using a different frontend stack is also possible. Separating the layers helps identify which part handles presentation, commerce data and deployment.
Build headless commerce (opens in a new tab)Reading model numbers
Size and coverage answer different questions.
Aya 23 is a useful example: its documentation identifies language coverage separately from parameter count. Treat those as different descriptors. As a reading method, record the exact release before comparing results, and check whether a reported evaluation matches the task and language you care about.
Aya 23: open-weights release (opens in a new tab)Serviceable design
Maintenance can shape the architecture.
Canadarm2 was designed with components that can be replaced in space. The Canadian Space Agency describes replacing individual joints and end effectors. This provides a concrete engineering example of planning for maintenance at the component level rather than replacing an entire system.
About Canadarm2 (opens in a new tab)Before you read
a technical claim.
Does a larger number always mean a better product?
Do not treat it as a complete answer. First identify what is being counted, which version is involved and which problem the measurement addresses. This is a reading principle, not a ranking of the products in our files.
Are these pages independent product tests?
No. These files explain material from official documentation and institutional sources. Maple Circuit has not conducted the experiments or hardware tests described by those organisations.
How do I check whether a detail has changed?
Each file identifies its reference and review date. Open the original source, confirm the product version or publication date, and send the relevant page to our editorial email when a correction is needed.