Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)MG
Posts
0
Comments
420
Joined
2 yr. ago

  • But he’s not wrong. Every awesome opportunity I’ve had was the unknown on the opposite side of fear and self-doubt.

    Push into the darkness, friends.

    Hello darkness, my old friend.

  • I don’t disagree. Solutions finding problems is not the optimal path—but it is a path that pushes the envelope of tech forward, and a lot of these shiny techs do eventually find homes and good problems to solve and become part of a quiver.

    But I will always advocate to start with the customer and work backwards from there to arrive at the simplest engineered solution. Sometimes that’s a ML model. Sometimes a ln expert system. Sometimes a simpler heuristics/rules based system. That all falls under the ‘AI’ umbrella, by the way. :D

  • I’m an AI Engineer, been doing this for a long time. I’ve seen plenty of projects that stagnate, wither and get abandoned. I agree with the top 5 in this article, but I might change the priority sequence.

    Five leading root causes of the failure of AI projects were identified

    • First, industry stakeholders often misunderstand — or miscommunicate — what problem needs to be solved using AI.
    • Second, many AI projects fail because the organization lacks the necessary data to adequately train an effective AI model.
    • Third, in some cases, AI projects fail because the organization focuses more on using the latest and greatest technology than on solving real problems for their intended users.
    • Fourth, organizations might not have adequate infrastructure to manage their data and deploy completed AI models, which increases the likelihood of project failure.
    • Finally, in some cases, AI projects fail because the technology is applied to problems that are too difficult for AI to solve.

    4 & 2 —>1. IF they even have enough data to train an effective model, most organizations have no clue how to handle the sheer variety, volume, velocity, and veracity of the big data that AI needs. It’s a specialized engineering discipline to handle that (data engineer). Let alone how to deploy and manage the infra that models need—also a specialized discipline has emerged to handle that aspect (ML engineer). Often they sit at the same desk.

    1 & 5 —> 2: stakeholders seem to want AI to be a boil-the-ocean solution. They want it to do everything and be awesome at it. What they often don’t realize is that AI can be a really awesome specialist tool, that really sucks on testing scenarios that it hasn’t been trained on. Transfer learning is a thing but that requires fine tuning and additional training. Huge models like LLMs are starting to bridge this somewhat, but at the expense of the really sharp specialization. So without a really clear understanding of what can be done with AI really well, and perhaps more importantly, what problems are a poor fit for AI solutions, of course they’ll be destined to fail.

    3 —> 3: This isn’t a problem with just AI. It’s all shiny new tech. Standard Gardner hype cycle stuff. Remember how they were saying we’d have crypto-refrigerators back in 2016?

  • lol I’m an idiot. I just finished a rewatch of Mr. Robot in which a taxidermist that stuffs formerly living animals plays a prominent role. That show kinda fucks with my head and messed up my perception of reality for a while.

  • lol I’m an idiot. I just finished a rewatch of Mr. Robot in which a taxidermist that stuffs formerly living animals plays a prominent role. That show kinda fucks with my head and messed up my perception of reality for a while.