When I was a kid I built a little cabin on an old wagon in our yard. Eventually my father said i was time to take it down and give the neighbours a break. I took it down, then decided to rebuild it even better. The new wood cabin was a huge improvement, but it lasted exactly one day before being taken down. It didn't matter that I had built it better and faster; it was just the wrong thing at the wrong time. Today, now that I don't have a 'job', I've been working hard on my personal learning environment (PLE) application, CList. But is it the right thing for the right time any more? I wrestle with that question, which is why this article appealed to me, even though you can stop reading after maybe the first third (again, it's an AI article that goes on and on and on and on....). The point is good: "A team can release three AI-powered features in a single sprint. If none of them improves conversion, retention, or satisfaction, the speed was wasted. The features were built efficiently. They just were not worth building." (p.s. don't get me wrong - working with code like this is the most fun I've had in a long time and while it would be nice if it was widely adopted, it's not really necessary). (p.p.s I really need a better name than CList - I'm open to ideas).
Today: Total: [Direct link] [Share]
