meh that’s a different support package

OWASP Top 10 is pretty much a list of suggestions for vibe-coders.

If Claude understand code, Claude ship code just fine. If Claude understand but you don't, you no ship code, let Claude do!

Got pulled into a meeting where a web dev contractor we hired stated, “I can’t promise these changes, it depends on how we can get CoPilot to do them”. I don’t think my bosses care because they want their bosses to know that they are, “working with AI”.

Sounds like what a lot of beginner programmers do as well.

I had to tell the ai to reduce the comments it made. Since it was bunch of not important information.

Yea the comments are awful. More useless than dog shit.

Agreed it's why if I'm asking for llm assistance I will generally start with a design for a component and ask it to follow that and comment accordingly usually leads to much better results than blanket asking it to do something for you

You can add instructions to not comment, you can also have it explain what it does at every step, not everyone just doesn't care about learning. It can be a very effective teaching tool if you use it that way. 🤷

Out of the box yes this is true, but:

1. Custom instructions go a long way
2. Review the code yourself, tell it what to fix, and it will fix it. For me it often takes like 5 rounds of this before the code is fully polished to the point I'm proud of it. And you know what? It's still MULTIPLE times faster than typing code by hand. And at least for me, the quality is higher, because I have 12 different agents that review the work too and they catch additional issues that even I missed.

If you or others ship shitty code don't blame the LLM, the issue is entirely the engineer using it wrong

So... indistinguishable from the statistical mean of human generated comments.

Nightmarish. Can you make the AI write up new documentation every time you want to push a change, so it looks like you're using it frequently but you still get to write the code yourself?

I would love letting LLM deal with documentation. It's the bane of my existence.

So it's enshittification, but they've doused the whole shebang with rocket fuel and set it ablaze.

If the company also trains AI, I'm guessing they're also forcing use to gather training data. I.e. tracking feedback, corrections, etc.

He better not have his spine poked by anything sharp :)

(in cade I failed at it: reference to Midra)

You make the billionaires proud, such a good lil capitalist

"...enabled me to deliver value in a fraction of the time I expected."

I don't wanna flame you for it.

This is kinda where I see vibe coding taking off the most: The same phenomenon as using LLMs to summarize and reply to pithy business emails.

Business gets so unbearably businessy, people are using machines to bypass the inherently un-human "professionalism performance" for them.

It might not be work anybody can claim to be proud of, but right now success for the professional-managerial class runs on looking busy and circling back to synergizing the workflow with best practices for optimal returns regarding key performance metrics 🤢 or whatnot.

I don't blame people for it, in a work context. Looking impressive with AI tools is now a survival tactic when working under normies holding the purse strings and investing stupid amounts of money into the bubble. They've forced people to be part of a circular, self-reinforcing imaginary reality they're profiting from.

So, I don't wanna flame you. I just hope you're doing something fundamentally human to keep your soul alive on the side, at least. Something you as a unique human being on this earth can be proud of. <3

Sometimes documentation doesn't help. My workplace used to be waterfall and we still have systems analysts producing documentation

One piece of work came to my team as "this calculation fails in this case and we can't tell why"

Looking at it there were two updates in the documentation showing updates ten years ago the first fixing that corner case with the second fixing a side effect of the fix

Why didn't it work? It was never built, or perhaps built but never merged

On the good side we have an excellent plan for how to fix that corner case, on the bad side we aren't funded to do that amount of work so we have to half arse a solution

I once heard someone describe legacy systems as systems without test coverage. I think it's not the best description, but it's certainly an interesting perspective.

It's part of why it bothers me when folks say they use LLMs to make unit tests. If anything, you should be writing tests by hands to get a solid specification then let the AI make the code. Of course this is a false dichotomy, but I'm just saying if you have to choose between those two options in some weird hypothetical bizarro world.

Now that's a good vibe coder

Yes. It's the same thing, except when I joined the market knowing fuck all about computers, while coding with my cute little BASIC commands; there wasn't some tech bro asshole telling all the C programmers that their skills would no longer be required. Or at least he (implicated in Epstein files billionaire, Bill Gates) wasn't saying it quite so loudly (as accused rapist billionaire Sam Altman).

Incidentally, I still work with that same C programmer, I'm still learning from them, but have since taught them a trick or two; and we both now charge sinful amounts of money for our time.

But he isn't the Microsoft ceo anymore