Earlier quoted context omitted.
I find that a C suite member talking about AI without a specific goal in mind (“we will use AI to automate X, which will help us do Y better”) is a huge red flag.
It also seems to be a main selling point of a lot of logistics and supply chain star-ups these days. I guess it sounds way sexier than "give us millions to build a new forwarder and our own tech because we don't want to use off-the-shelf software and we want to be acquired by DHL one day".
How many of you know that the team is working on something that no-one wants?
251–260 of 428 posts
Re: How many of you know that the team is working on something that no-one wants?
#252Obviously using a throwaway here. Our board members got it into their heads that successful companies must have an AI "play", so they instructed the CEO to invest about 10% of our development budget on AI. We are doing absolutely inane projects that have no hope of succeeding. We serve a niche industry where certified professionals have to do certain tasks personally, instead of being able to delegate to secretaries.…
Re: How many of you know that the team is working on something that no-one wants?
#253We might get the details wrong, but somebody is going to make a killing with this in the next few years.
Re: How many of you know that the team is working on something that no-one wants?
#254Earlier quoted context omitted.
I remember just before my first web project. I worked on a Oracle client server project (SMDS management tool) and to install the client, you installed about 4 products via 14 floppy disks one after the other on the client PC. Took two days for two of us to install it on five or six client PC's
So you can probably imagine what it was like when we had several dozens of client pc’s across several customer companies across several cities across the continent.
I recall discussing this with the engineering centre manager about how in 5 -10 years the web could replace fat clients on PC's
Re: How many of you know that the team is working on something that no-one wants?
#255Earlier quoted context omitted.
> we all know the project will fail unless someone develops well-perfoming, human-level AGI before Q4/2020 This is hilarious, and makes me wonder how many similar corporate AI initiatives are under way in the world right now.
I have had a couple conversations where a business guy starts off with a decent idea then he says something like "the cognitive AI module will fill out your expense report after watching you do it for a couple weeks". What the fuck? If I had the ability to code a cognitive AI module which could do that I would not be building it for you, I would solve self driving and license the software for billions.
I've been kicked off a project because I couldn't stop talking about training data (they already had) and machine learning algorithms (NLP, text classification) that we could implement right now to start automating a couple of internal processes that are currently pointlessly manual. Think moving incoming e-mail to appropriate downstream support channels.
Not enough magical AI / AGI in there.
The countless PowerPoint presentations built after my departure described processes along the lines of "the AI will detect when you're about to miss your connecting flight and book you into your favourite hotel with your favourite dinner pre-ordered".
Surprisingly, the project survived and now they collect training data and use machine learning for text classification.
Re: How many of you know that the team is working on something that no-one wants?
#256Earlier quoted context omitted.
I had a boss not so long ago who kept selling our customers our "Conversational AI Bot". What we gave them was a fairly dumb keyword search of a library of questions the customer would type in along with answers - wrapped in some html widgets displaying cartoon robot heads. It still astounds me that not only did none of those customers sue us for blatant misrepresentation, but most of them were delighted with what th…
There are a couple of lessons in that anecdote.
I had a similar cognitive dissonance when doing "R&D Grant applications" a long time back. I kept on thinking "Research" was the sort of rigorous academic work you do to earn a PhD. In the government/business world, it seems pretty much spending time or money to learn how to do anything not 100% required for your business previously counts. Including things like "selling our widgets, only via the internet" being valid and acceptable thing to get government rebates for "R&D". I still feel dirty everytime I draft one of those grant applications... :shrug:
Re: How many of you know that the team is working on something that no-one wants?
#257Re: How many of you know that the team is working on something that no-one wants?
#258Earlier quoted context omitted.
What always drives me crazy about instances like this, is that managers and the c-level seem to be much more willing to listen to some "random" guy or blog over their own people. People they hired, people that have a much better understanding of the issue, the processes and so on. This effect is by no means limited to tech. And engineers, regardless of type, are by no means immune to that as soon as they reach higher…
They're just seeking some outside the box solutions. If you don't course correct, how do you know/show that you're driving?
Re: How many of you know that the team is working on something that no-one wants?
#259Earlier quoted context omitted.
Financier Martin Armstrong claims to have exactly such a system but it doesn't predict the market, it only makes quite accurate market forecasts.
I have heard about this guy's forecasts but have been unable to find a list of predicted vs actual. Do you know of such a list?
Re: How many of you know that the team is working on something that no-one wants?
#260Obviously using a throwaway here. Our board members got it into their heads that successful companies must have an AI "play", so they instructed the CEO to invest about 10% of our development budget on AI. We are doing absolutely inane projects that have no hope of succeeding. We serve a niche industry where certified professionals have to do certain tasks personally, instead of being able to delegate to secretaries.…
Long story short: after a year or so, our boss decided to scrap our half-baked system and gave up on the idea of creating some internal product entirely.