Solutions are not delivered all at once. We lay the foundation months before, but changing how the team works. We identify what we need to research and how to solve the problem. We integrate new libraries and frameworks and develop patterns of implementation. And then we build and release dependent components and features ahead of time making sure they all come to together and function together. We build the risky first. And then when that…
I never got up at 5 am to go stand in line for Boxing Day. Too many crowds, all immediate purchases, not enough browse time. I remember the first year you could buy “online” for Boxing Day – I bought a phone online before we sat down for dinner on XMAS – no lines, no early mornings, just a cup of tea and the internet. And that’s the day Boxing Day just became another day…
No one is watching to see how often you post, when your last update was, or what the space in between is. They are waiting to see when you are coming back. Gaps aren’t from a lack of discipline or consistency; they emerge when we are overloaded. But they don’t rule us; they just wait for them to take them back.
Eventually, it will all break. Yes, all of it, everything will break. Someone will trip over a cord, a surge of power, a misplaced “.”, a bad line of code, whatever – it will all break. Or maybe it will simply be wear and tear and longevity. After 18 years, don’t you want a break from working 24 x 7, never stopping, never going on vacation, doing the job every day, that needs to be…
I love this definition of an AI agent today – “Brilliant, but lacks expertise.” This is 100% how I see AI agents today. I found this video interesting, if only because it gave a non-hyped version of agents. https://www.youtube.com/watch?v=CEvIs9y1uog You wouldn’t hire a developer to manage your network, and that’s the same way you should approach the development of your agents – one size does not fit all.