alt Hacker NewsTheir company does data projects. That plus context makes me think they’re talking about internal work process automation type of work, although it also seems like they’re talking about conversational interfaces (chatbots).
I completely buy the “emperor’s new clothes” argument for work process automation. I’m surprised they don’t address AI-assisted engineering, which seems to be going positively for a lot of folks (although I have doubts about its sustainability). I disagree about the success of chatbots, if the problem is narrowly-defined and chosen properly. My previous company built a conversational interface to a vector database and saw good results. (Although, arguably, the vector database was the real magic, and a traditional UI would have been faster and more accurate.)
In general, I think OP is more right than wrong, though, particularly about the AI mania and unrealistic expectations sweeping the C-suite.
Replies
> I disagree about the success of chatbots, if the problem is narrowly-defined and chosen properly.
If you can narrow the problem down, then you could design a much better interface for it than a text box and free form text (unless that's the better solution).
As for as AI assisted engineering goes, the thing is that after some time with a project, you already have much of the workflows and routines nailed down as scripts and other various combinations of tooling. And unless it's spaghetti code, you will have various snippets you can copy from for new code. The one thing I've observed about AI projects is that there's often little technical design coherence about them. It's always a kitchen sink of technologies and practices.
Do yo have links handy for AI-assisted engineering going positively? The case I have on my mind of it going negatively is this recent Ford case [1] It's not that I believe it couldn't go positively, of course.
[1] Ford rehires human engineers after AI fails to match quality checks
https://www.bbc.com/news/articles/cgrkd41n2v9o