Anything substantially new will still require an engineer in the loop. Specifically, if a new design pattern, archtecture, etc is required. AI can only build on its training material - it can't yet have original thoughts.
Big management consulting firms real value prop is two-fold 1) (value to it's employees) networking for the corporate leadership class when young and 2) (value to outside companies) blame insurance, you can always blame them for why something didn't work
> It has always been overpriced and had huge margins.
This is the engineer’s take on things. I am entirely sympathetic to it.
I also think it missed a lot of what management values in consulting. At its best, you can offload a lot of things unrelated to your business to people who are experts. At its worst, you’ve offloaded the blame to a group of over-worked twenty-something’s with impressive degrees who have no idea what they’re doing, but who sound really fucking confident about it.
Can an internal team do it better? Probably. Will they be cheaper? Probably. Will they assuage management’s anxieties and deflect some/all of the blame? Nope, not at all.
I did some software consulting years ago. Were we overpriced? Probably. But I also saw why we were brought in:
- A TDD loop where the Indian QA team played the role of the tests. The engineers would yeet some broken code at the end of the day, the poor QA testers would click through all the broken interfaces, and then the engineers would fix it the next day.
- A release process that was so slow and hellish that everyone just went to the DBA to have him add a stored procedure to implement their feature. He could get it in for you the next day.
- A frontend framework discussed in hushed tones, being built by a mysterious monk-like engineer, which was going to be the client's big secret weapon. In reality it was a terrible version of React built on top of jQuery.
- A core in-group of backend devs (most of these guys had advanced degrees for some reason), who would stay late every Friday, going through heroics to do a release of the client's email-templating app. There would be then be lots of back-slapping and congratulations the next Monday for these geniuses who were keeping the business afloat.
- "when in doubt, set timeout". They didn't know about callbacks
Usually consultants are brought in when upper management can tell that there is something very wrong and they can't fix it within the chain of command of their full-time staff.
Ah yes, the old trope of "consultants are only there to take the blame". Sure.
Having done a stint in consulting, most internal software teams are useless, that's why these companies hire outsiders. They are sick of having to deal with stubborn teams who think they know everything, and refuse to change. You can see that mentality in these threads.
In the article, they explain the goal of vibe coding prototypes is not to rebuild software, but to test the defensibility of businesses based on their software so they can decide whether to acquire them or not
> AI is finding vulnerabilities in all kinds of software written by humans.
I'm aware — I've used LLMs to find vulnerabilities, myself. But it doesn't follow that because AI can find them that AI can find the optimal fix, because fixing vulnerabilities often involves tradeoffs.
Anything substantially new will still require an engineer in the loop. Specifically, if a new design pattern, archtecture, etc is required. AI can only build on its training material - it can't yet have original thoughts.