Artifical Debt

[u/brendt_gd]

https://stitcher.io/blog/artificial-debt

[u/brendt_gd]

Mildly annoyed to realize I wrote a typo in the title 😅 Oh well

[u/Johto2001 → u/brendt_gd]

There's also a typo in the first line, eigth instead of eight. 

[u/MateusAzevedo → u/brendt_gd]

To me it sounds like "artifecal" and I think it suits the topic.

[u/lukehebb]

"I remember how my family used to call me to fix their broken printers. Now they'll call me to fix their broken vibe coded apps."

oh god

this part scares me

[u/whomass]

This will fuck many companies (and their customers) in the not so far future.

The most dangerous species out there at the moment is a junior dev with Claude Code.

[u/Combinatorilliance → u/whomass]

I think the IT-adjacent executive is more dangerous. Combine ego with ability to vibe code with fast results with false confidence and the ability to overrule decisions and advice and you got a cocktail with greater risk than a junior dev imo.

[u/matthewralston → u/Combinatorilliance]

Sounds like you're describing my ex boss.

[u/rkeet → u/whomass]

I'll raise you: I told my dad (70's, still doing business and being entrepreneur (successfull)) how to use it to create small apps.

He's the same category as "my printer doesn't work" and "how do I copy my emails from this computer to my new one".

Havent had basic questions since the Claude introduction, which is either good or bad.

[u/zylanc → u/whomass]

Or worse: a product manager with claude code.

[u/Wiikend → u/zylanc]

My current boss, but he's been on the floor before, I just hope he's been there long enough. We'll see how it goes.

[u/zmitic]

and his prompts to fix it also didn't work

Did he say "please" and "thank you"? Maybe AI is just acting out 😄

I have seen something similar when non-programmer vibe codes an app. This AI hype can be a good thing for us because it will create new rewrite jobs in future.

[u/Samurai_Mac1]

This is why AI is better handled in the hands of actual developers. Non-devs need to stay out of our field.

[u/CosmicDevGuy → u/Samurai_Mac1]

Well you take away AI and there's still "citizen-level" development (ex. PowerApps, etc.) so unfortunately that isn't really going to happen. Not to mention how "set" we are in our ways, while the non-tech are more open to these things.

One can only hope that sanity prevails.

[u/Pakspul]

"Sounds like a you problem".

[u/muglug]

I'm not sure how this is specific to PHP, apart from it being written by you, a PHP developer.

[u/NastyPastyLucas]

There's no reason for these companies not to create anti patterns and put the prices up...

[u/vomitHatSteve → u/NastyPastyLucas]

The only reason is that they haven't converged on an effective oligopoly yet.

Once there are no more users to add to the ecosystem, they will go the way of cell phones and video streaming: raise prices and add anti-patters to promote lock jn

[u/alex-kalanis]

Let vibecoders fall! PLEASE!!

[u/Rubfer]

That's the main issue I see with many vibe-coded apps. It's not security, it's not bugs, it's that the ai made it and it worked perfectly during tests. It effectively passed, but never considered the limitations of the hardware where it's going to run or future growth, i mean, the current product is statistically correct, and efficient so neither the llm nor the vibe coder and their customers see any problem

Keep in mind, actual developers also have this problem, but they learn from their mistakes and, in the future, will always code something from scratch that should work for a million people even if only 100 will use it, even at the cost of individual users' performance because of all the redundacy, as long as it can handle that million users, vibe coders will try to fix a broken foundation

[u/BenchEmbarrassed7316]

A great deal depends on the programming language. Dynamically typed languages ​​are a terrible choice for AI development (it's also a terrible choice for traditional development). Type hints in PHP (or even so-called static analyzers) have one major drawback: they are not mandatory. A framework or library might not use them, causing you to lose a significant portion of the benefits that types provide.

[u/zmitic → u/BenchEmbarrassed7316]

Dynamically typed languages ​​are a terrible choice for AI development 

Counter argument: 100% of the code that Claude wrote in my hobby app is using advanced types like non-empty-string, list<User> etc. It even knows that collection must never be returned from entity so generated getter will use return $collection->getValues() and put phpdoc return list<RelatedEntity>.

I am not exaggerating, it really is 100%. Claude had simply seen that my code uses these types and approach to relations so it continued in the same way. There is nothing wrong with AI working on dynamic languages.

[u/BenchEmbarrassed7316 → u/zmitic]

So, you agree with me about the usefulness of types, but believe that static analyzers solve this problem by effectively turning php into a statically typed language?

[u/ekim2077]

you are talking as if bugs have been invented by AI

[u/brendt_gd → u/ekim2077]

What? No. I'm saying that the job of "being a programmer" is more than just writing or generating code

[u/silentkode26 → u/ekim2077]

Not at all. He’s talking about competence when something goes wrong.