Worth your
reading time.

A useful article should give you more than a reminder that technology is changing. It should help you understand a problem, weigh a decision or notice something you might otherwise have missed. That is what this blog aims to do.

A closer look at the work

We write about AI, automation, connected systems and the less glamorous decisions that make software dependable. The audience is anyone building a business with these tools, or trying to make sense of what they might change. You should not need a second browser tab just to decipher the first paragraph.

Each piece follows a particular question far enough to be useful: how something works, where it can fail, and when a different approach would make more sense. There is room for enthusiasm, doubt and a little dry humour. The explanation still has to earn its place.

Sources you can follow

References sit alongside the argument so you can check the evidence yourself. We favour original documentation, research, announcements and technical writing. A vendor’s claim is treated as a claim; an unresolved question stays unresolved. Links are checked during preparation, although documentation and products can change afterwards.

Examples with context

A worked example should make the reasoning easier to inspect. Invented scenarios are labelled, project notes explain what is available and what remains in development, and customer outcomes need evidence. Where an example has been run, we distinguish the observed result from a proposed experiment. A tidy diagram alone proves very little.

Room to read

Comfortable type, manageable line lengths and useful headings matter, especially on a phone. Figures should explain something particular to the article, with captions or text that carry the meaning too. Tables use proper headers, links are clear, and motion respects the reader’s settings.

Dates and corrections

Article cards, bylines and the RSS feed show each article’s publication date. When an explanation needs correcting, we keep that original date and improve the explanation.

If an explanation misses something or a source no longer supports a claim, please email hello@hamsasoftware.com. Corrections are part of looking after the writing.

See you on Thursday

New articles are planned for Thursdays. Follow the RSS feed to receive them in your feed reader.