Well that is a very good point!
comments
I would never trust anything a tech blog's opinion piece says blindly
Knowing how to code is now "syntax heavy"
god I hate this world
That's the beauty of it, just ask chatgpt or copilot how to do it, then learn by fixing all their mistakes. Until my company decided to become "AI first" I barely ever touched Python, I still barely know Python, but I now know to spot indentation errors and hallucinated function calls.
I will sign up! I have no fucking idea how vibe coding works, which makes me perfect!
Say it. Say the words.
The words are all still stupid because it's a new thing, but there is one specific space that I find it just impossible to deny the way that there are already tools on the market that change the way the job is done:
Claude can turn plain english statements about what data I want from what different parts of the Microsoft 365 administration ecosphere into scripts that take all that data, transform it the way I want it transformed, and turn it into spreadsheets, pivot tables, data manipulation macros, and everything else I need to answer questions which are really hard to answer from the MS web interface. I can ask things like "Which systems have any of these three known vulnerable apps?" or "What software is common to everyone working in this division of the company?"
It's boring stuff, but it makes a world of difference in terms of what I can look at to base my decisions on. I spent less time building repeatable reports for each type of object I need to think about (device, application, user) than I did building even one report for one assessment in years past without automation. And it's not constantly asking the LLM to do things for me, it's building a couple of tools with a much faster iterative process for feature tweaks or debugging than could take place as an interaction between two people. I was making changes to scripts
I'm using it only for specific work areas where I already know the APIs I just don't have the time to stumble through the gather and collate of the various data. Based on the level of complexity of the tools I've been able to build I would say that anybody who knows how to describe the data they work with most could use a tool like this to make that process a lot more automatic. We're not ready for the tool to do the work without human oversight, but we're ready for anybody who works with stacks of data to build their own automation instead of having it built for them.
And even this improvement wasn't universally appreciated: some people found error messages they couldn't ignore more annoying than wrong results, and, when judging the relative merits of programming languages, some still seem to equate "the ease of programming" with the ease of making undetected mistakes.
This guy was writing in the year x86 was first introduced, and I still feel like I see this attitude around.
(He manages to shoehorn in a "kids these days" paragraph too, though)
Yes, but quality takes actual skill to measure, instead of just a diff.
(Although I guess lines are still better than time in office)
Hmm, was the boss hoping to turn that into a "why do I even pay you" moment?
You could have that, would just have to be experience writing code for AI, rather than vice versa...
So I ran into my first genAI coding junk yesterday when I was on a call with my boss and as a solution to a problem we were talking he said, "hold on let me ask Gemini."
I felt my soul die a little bit at that point.
But the fun part is that Gemini first didn't provide a good answer.
And then on the second go it also didn't provide a good answer.
And then on the third attempt we decided to table the issue for the moment because prompt coding on a call was taking longer than I think he expected.
I really disliked that experience.
Yeah, you're a 747 pilot. You're the exception, not the mode
Why not, If it resonates
You know the "vibes" of different models - when to use
Would that be a vibe-rater?
Usually not. At least from where I sit
Well that's fairly privileged for you.
You still haven't said anything about what ways your business encourages safe use of the thing. Tradesmen have a long history of training new workers on how to work safely.
The cherry picker was invented because ladders are bad, and they are much safer than ladders. Businesses started using them because it's a better and safer tool for the job.
Your "reasonable businesses" are still playing. They are asking their employees to produce more and understand less.
There are safety courses for dangerous machinery
https://www.ihsa.ca/Training/Courses/Chainsaw-Operation-and-Maintenance-(2024).aspx
AI safety is not being considered by businesses.
Vibe salary
10x the speed, sweet. So 10x the salary too right?
The guy who wrote this is an idiot, but he became so in a world where "LoC" is a metric -- one that Goodhart would love, but alas.
This is honestly the road to hell and the ~good intentions in one.