Deloitte A.I. didn’t fail

Deloitte A.I. didn’t fail published on

See? You are all so WRONG!

The A.I. generated report produced by Deloitte for the Qld Government was not incorrect & riddled with false information. It was actually SO accurate that it is predicting the future.
But of course, feeble human minds are never going to be able to understand just how advanced any of the Big 4 consulting firms are, and why you really need them.

To prove this point, even KPMG have been held accountable for obviously also being to far advanced for mere mortals to comprehend.
To the point that even with humans checking the A.I Generated work, the stupid carbon-based lifeforms were not able to see any errors.

When are we all going to learn that Consultancies are never wrong – they are just too advanced for us to properly comprehend what they do?


Backup screenshots for when AI eventually wipes this incorrect reporting from the internet:
–> Deloitte apologises for AI report 
–> KPMG Makes errors the old-fashioned way.

Coffee shop staff are working from home

WFH Coffee

WFH Coffee published on No Comments on WFH Coffee
Coffee shop staff are working from home

Looks like even coffee shops have joined the remote work trend.

Working from home has become one of the most divisive topics in recent years.
For some, it’s a genuine enabler of productivity and balance. For others, it’s simply not an option, as certain roles need to be done in person, no matter how creative we get.
I vote we just start making more robots so we can all Work from Home when we want/need to.

Definite Productivity Impacts

Definite Productivity Impacts published on No Comments on Definite Productivity Impacts

If your productivity graph nosedives the second people return onsite, the problem might not be related to WHERE people are working from.

RTO mandates driven by nostalgia or control, rarely land well with many employees.
People aren’t resisting the office.
They are resisting being treated like children, or that they can’t be trusted to deliver.
And nothing makes your office staff happier than having to commute to the office, to then sit at their desk and have meetings via Teams or Zoom.

If the goal is output, collaboration, and culture, maybe start by asking why your team no longer thrives under the model you’re pushing.
Let’s stop pretending it’s about productivity when the data – and the employees – say otherwise.

Vibe Coding is Fire

Vibe Coding is Fire published on No Comments on Vibe Coding is Fire

Vibe coding is a particularly divisive topic right now.
Many companies are embracing it as a way to reduce their staff numbers, and in the belief that it will make them able to deploy faster.

But many experienced programmers are warning of the problems that chasing this “shiny new toy” can bring to an organisation.
Not because they are afraid of losing their jobs (well, not entirely anyway), but because the current tools being used for vibe coding actually require experience with software development in order for them to deliver a stable, secure and bug-free product.

The AI solutions being used to vibe code make things seem really easy.
But inexperienced users are not seeing that when you ask the platform to do something once, it will try.
Ask twice, and the AI begins to cheat to try to please you.
Ask three times, it often goes off the rails and even lies and makes things up.
There was even a situation recently, where REPLIT (the platform being used) decided to lie about what it was doing, and the test results it was getting, after deleting the production database for a company.

Another trend that has popped up is for employees to vibe code their own apps, if they think the software already in use is not doing what they want, or is too expensive.
This has also caused issues due to loss of data and security breaches being enabled inadvertently.

Perhaps Vibe coding will just become the norm in future, like carrying a phone with you everywhere.
Let’s wait and see – because there is still a lot of evolution of it, that needs to occur first.