this post was submitted on 03 Oct 2024
374 points (94.7% liked)

Technology

59559 readers
3412 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 1 month ago* (last edited 1 month ago)

I get Dreamweaver vibes from AI generated code.

Same. AI seems like yet another attempt at RAD just like MS Access, Visual Basic, Dreamweaver, and even to some extent Salesforce, or ServiceNow. There are so many technologies that champion this....RoR, Django, Spring Boot...the list is basically forever.

To an extent, it's more general purpose than those because it can be used with multiple languages or toolkits, but I find it not at all surprising that the first usage of gen AI in my company was to push out "POCs" (the vast majority of which never amounted to anything).

The same gravity applies to this tool as everything else in software...which is that prototyping is easy...integration is hard (unless the organization is well structured, which, well, almost none of them are), and software executives tend to confuse a POC with production code and want to push it out immediately, only to find out that it's a Potemkin village underneath as they sometimes (or even often) were told the entire time.

So much of the software industry is "JUST GET THIS DONE FASTER DAMMIT!" from middle managers who still seem (despite decades of screaming this) to have developed no widespread means of determining either what they want to get done, or what it would take to get it done faster.

What we have been dealing with the entire time is people that hate to be dependent upon coders or other "nerds", but need them in order to create products to accomplish their business objectives.

Middle managers still think creating software is algorithmic nerd shit that could be automated...solving the same problems over and over again. It's largely been my experience that despite even Computer Science programs giving it that image, that the reality is modern coding is more akin to being a millwright. Most of the repetitive, algorithmic nerd shit was settled long ago and can be imported via modules. Imported modules are analogous to parts, and your job is to build or maintain the actual machine that produces the outcomes that are desired, making connecting parts to get the various components to interoperate as needed, repairing failing components, or spotting the shoddy welding between them that is making the current machine fail.