About 75,000 Deloitte staff have been given access to a generative artificial intelligence chatbot to create PowerPoint presentations and write emails and code in an attempt to boost productivity
ft.com
About 75,000 Deloitte staff have been given access to a generative artificial intelligence chatbot to create PowerPoint presentations and write emails and code in an attempt to boost productivity::About 75,000 staff to be given access to ‘PairD’ tool with advice to validate ‘accuracy and completeness’
You are viewing a single comment
I really hope this goes through, because the pile of dogshit they sold my municipal government can’t fairly be called code.
It’s astonishing. I will never ever deal with that company if I have the opportunity in the future because of how utterly incompetent they were creating a “microservices architecture” for us which is in effect a series of AWS Lambdas running random Python that do not coordinate, suffer from race conditions, and in many places do not do the thing in the first place.
It’s the second worst code I’ve ever seen. The first was home grown at another public sector job.
The cost for this shit that could have been replaced by a simple Flask app? Or even a well structured, in-lined Python script? $1.5 million. Ongoing costs in the hundreds of thousands per year.
This should be a $20-50/month EC2 instance.
Absolute garbage.
No, I am not underestimating the complexity requirements nor the communication overhead/competing stakeholder interests and all other manner of externalities.
Deloitte belongs in the dust heap.
BUT THEY CHECKED ALL THE BUZZWORDS
Serverless. Lambda. Cloud. Python. Microservices. Blahblah.
The number of companies I've contracted for that just try to hit all the buzzwords and don't actually architect for their need, nor simplicity and maintenance is ridiculous.
Example for one place I'm consulting for right now...the average simple change like enabling/disabling a button based on a required field in a form typically takes touching 10-14 different files.
Why? Because checkboxes need to be wrapped library components with their own NPM repo. They must also be super dynamic and flexible, so tons of inputs and outputs. They must also be themeable. Anywhere that uses them must be an isolated reusable form. Consumers of that form have logic to decide whether or not that form displays a certain way for the context. That component must also bubble up it's state and the form state to its parent. It's parent is a micro frontend (fuck micro frontends). That must communicate it's state to a composable parent. That parent must rely on stupid NgRx/Redux to dictate button state.
I hate it all. I feel like engineers these days are convoluted just to be convoluted.
I know you're right, because you're either at one of the top 20 tech companies, and thus know what you're talking about, or you're not, and thus all your stuff could run on a good desktop computer.