During my computer science studies, our introduction to artificial intelligence didn’t begin with neural networks or robotics, but with a parade of definitions:
As a teenager, I was all ideas and no follow-through. Every week brought a new concept, a new scheme, a new startup in my head. I wore my imagination like a badge. But over time, I had to confront something uncomfortable: ideas weren't rare. They were a ten a penny, a kind of noise that kept me from actually doing the hard work.
In a recent piece, I made the case that we should stop trying to build "perfect" AI. That imperfection is not a failure mode — it's intrinsic to how these systems work. Here, I want to go one step further: not just to excuse AI's flaws, but to explore how we can use them. How we can design with imperfection in mind.
We seem to have stumbled into a strange contradiction: we demand perfection from our machines, while tolerating imperfection from ourselves. The same people who chuckle at human error in the workplace will denounce AI systems for the slightest misstep. "It hallucinated a fact!" Yes. And you never have?
A useful way to understand the successes—and the stagnation—of big tech is through the lens of organisational advantage. Not just what a company did, but how it was set up to win.
The 20th century belonged to specialists. Experts carved out narrow domains and dug deep. The system rewarded it — the best knee surgeon, the best COBOL programmer, the best ad copywriter. Depth was the differentiator. But AI tilts the game board.
Have you ever tried to create a language from scratch? I began creating one for fun a while ago, and I've been trying to teach it to ChatGPT,. Langaf is a fictional language that is similar to English and uses a base twelve counting system.
Application Programming Interfaces, or APIs, are an essential component of modern software development. APIs allow different software systems to interact with each other, facilitating the exchange of data and functionality between them. However, while APIs have become ubiquitous in modern software development, their documentation often leaves much to be desired.
As a product manager, making decisions is a big part of the job. While we all want to make the right decision every time, sometimes things don't go as planned. It can be tempting to try to stick with a decision, even when it's not working, but I've learned that it's better to be able to reverse course and make a new decision.