Ainsley Williams, mechatronics engineer in Johannesburg. Two decades spent where one discipline stops and another starts.
The Solar Monitor reads sites belonging to other people, each reporting through a different platform. Those platforms do not agree with one another about what they are measuring or how often. Reconciling that is half the work, and it is the half nobody finds interesting.
The other half is that nobody reads dashboards. Numbers and charts are placed in front of a person who has no time to interpret them, so the interpretation never happens. This platform observes each site on a schedule instead, writes up what changed and what is likely causing it, and answers questions about it in plain language. The charts still exist. They are not the point.
The monitor can be talked to. A site owner asks what happened yesterday and gets a sentence rather than a chart. The assistant on the contact page of this site is the same build answering a different subject. Neither one improvises: what each is allowed to see is settled before it is asked anything.
How it worksThe route runs from national infrastructure to a software platform. What the stops have in common is not a subject. Each one sat where two things met, and no single specialist owned the ground in between.
I started in a large consulting firm on national roadways, toll facilities, urban precincts, and the electrical systems that run underneath them. Electrical infrastructure does not sit beside civil infrastructure. It runs through it, and the drawings are produced by different people. The Johannesburg infrastructure upgrades for the 2010 FIFA World Cup were where I first saw what happens to a programme when the date cannot move.
I worked on the commissioning and acceptance testing of a private toll concession in West Africa, the first of its kind in the region. Commissioning is a seam by definition. It is the point where the thing that was designed meets the thing that was actually built, and the two are never identical. Doing it under an unfamiliar regulatory framework adds a second seam that appears on no drawing.
I moved into project and contract management, and eventually ran a division of a national contractor: several project managers, multiple active contracts, tendering strategy, subcontractor development. A technically correct decision that loses the contract is not a correct decision. Where exactly that line falls is not taught anywhere, and getting it wrong is expensive in both directions.
I led the operational side of establishing an agri-processing venture across multiple countries in Africa, with investment and offtake counterparties in Europe and the United States. Land, permitting, design, equipment and contractor selection, cross-border logistics and legal negotiation, and test cultivation on the ground. It taught me more about what a business actually needs from its engineering than a project that runs cleanly ever could.
Sinclair Dynamics is the practice I run now, and the monitoring platform came out of it. It is the same kind of edge as the others: a physical system on one side, software watching it on the other, and the decisions that matter all in between. The platform stands on established engineering, on mathematics settled since the 1940s, and on a capability that did not exist two years ago. None of those three is mine. Putting them together is.
Three items. Each stated the way the issuing body states it.
Previously held, all now lapsed: ORHVS Responsible Person for high voltage systems, ISO 9001 quality management awareness, and ACSA airside induction and access permit for works at OR Tambo International Airport, a National Key Point, requiring assessment, security vetting and police clearance. The authorisations have expired. The disciplines they enforced have not.
Most of the interesting problems in engineering and in business are not new ones. The constraints move. The failure modes tend not to. I write occasionally about settled ideas that turn out to explain something current, usually because I have just run into one. Occasional is meant literally.
A document is written once, read cold, and cannot be asked anything. Why no page can be written for every reader you have never met, and what changes when a reader can ask instead.
Read itA machine does exactly what it is given, and nothing more. Why judging what one produced always means judging what it was asked to do, and what Ada Lovelace already argued about it in 1843.
Read itWhy "you can always spot AI writing" tells you almost nothing about how much AI writing you have read, and what the instinct is actually detecting.
Read itThe contact page is where this goes next. There is an assistant on it as well, which will answer questions about any of the above and asks less of you than writing to me does.
Get In Touch