- OK according to chatgpt we are compliant. please review this email that I'm writing ( bullshit, he let the AI write that) to the customer. See this is what you can do with AI and I'm not even an engineer.
Unfortunately we are seeing similar in the software industry. Its the fact that AI is hitting everywhere, at every level, all at once. New tools for everyone to work out how to use.
So this means we have to face all these different roles using AI. We have to listen to their opinions on how to use the tools. We even have them advise us on how to use the tools. Management... or HR... telling you how to 'work' and even 'how to think' in relation to AI.
On the engineering side it's actually worse. Before anyone got the month or two of "Just use it and learn it", engineering leads started speaking in two languages at the same time.
1. We are creating many megabytes of per-prompts, skills, plugins, to burn hundreds of dollars of tokens with, you can even run multilpe of them at the same time in different terminals. They will take the process from start to finish. These will tell you "how to think" and "how we work in company X".
2. We want you to pair programme with the AI, stay in the loop, treat it as you junior or peer. Learn to use it as a tool for you the engineer.
These are not compatible. They are mutually exclusive.
The former is the cart before the horse. Before actually learning what the tool is capable of "out of the box" they move straight to extending it and writing systems on top of it.
There are so many problems with this.
1. Money. Running these "do all" highly detailed dozen step 'one shot prompts' costs a fortune. People are literally laughing and startig a leaderboard on daily costs. People are proudly dumping screen grabs of "Single session, single prompt, costs" of close to $1000. In one such example the output was 400 lines of code at a cost of $650. Meaning it's more than $1 per line. Worse though. This was not the only "one shot" time they ran that process. They ran it multilpe times a day for weeks refining it. I personally see a VERY nasty shock coming for these people and the funny ha-ha memes will stop dead.
2. They seem to be asking engineers to encode themselves and their thinking processes into the LLM.... and a lot of engineers are saying, "Yes". I am personally frowning and saying.... that wasn't in my contract, was it? You hired me for my skills, you are asking me to 'transcribe' 40+ years of dev experience into a claude skill?... and you don't see how that offends me?
3. They are building on top of a moving muddy field. What claude is today is going to look nothing like claude in 1 years time. The chances that their 'skill and plugin' repos will still work or be required in 1 year ... doubtful.
4. Cross sell tools you don't own. Outside of the engineering (though some do partake too) where we enjoy the CLI and the IDE interfaces to LLMs, business and "front end designers" and HR all prefer to use things like BMad or Obsidian. They are investing time, money and effort into these tools without realising they are as ephemeral as a spilt bottle of ether. We have already seen AI startups die from nothing more than a new release of an LLM replacing it overnight. Will BMad and Obsidian survive the first bubble burst? Maybe, but there is very high risk they won't.
5. We must use AI for everything, throw everything at it! There is no reason for you to write any code at all anymore! It's headless chickens all running in different directions. People can produce so much more output with AI there isn't enough time to check if any of it is any good. People are now using claude to review peoples claude skills use to write claud skills.
Right now, I'm chilling, keeping my powder dry, using the LLM as I know how and closing tickets quietly. Waiting on things settling down, waiting on a few walls to be slammed into, waiting on the "Hey, experienced engineer.... we may have miss judged you" to come.