this post was submitted on 03 Nov 2026
259 points (94.5% liked)

Technology

89443 readers
3762 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 news or articles.
  3. Be excellent to each other!
  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, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] fonix232@fedia.io 0 points 15 hours ago (1 children)

As a senior dev... AI actually improved the code we wrote in my last job. Mind you the codebase was in a shite position (tons of technical debt, plague-like avoidance of inline comments because "all of that knowledge is on Jira/Notion" except it wasn't; lots of legacy code, undocumented weird behaviours, everyone was doing their own coding style without regards to the rest of the codebase and so on).

With controlled AI contributions, we've managed to:

  • refactor large chunks of code where the overall high level logic didn't need to change, but the underlying tooling did (e.g. lots of UI layers got rewritten from a very early attempt at a standardised MVVM approach to a well defined MVI one, we've also managed to eliminate the remaining RxJava/RxKotlin legacy flows to replace them with Coroutines)
  • UI layers got refactored in no time because the AI agent was able to convert them appropriately (and even fixed a handful of UI bugs)
  • a handful of core monoliths (yes I know... I hated working with them as well, but we never had the chance to properly refactor) got split up into more manageable, vertical-specific domain controllers without breaking
  • the elimination of a legacy overarching component that was estimated at 6 months, got reduced to 6 weeks
  • unit test coverage skyrocketed because even if the code was hand-written, an agent would provide coverage, based not just on implementation but on intention (and adoption of TDD/BDD finally started spreading).

Meanwhile code quality improved because we've had well established patterns and styles defined in the agent instructions, and even the anti-documentation "pragmatists" got shut up when they finally understood that the AI works better if there's fucking comments to explain what's going on

[–] FiniteBanjo@feddit.online 2 points 12 hours ago (3 children)

What you've done is allowed an unethical and incompetent machine create an unmaintainable technical debt which will destroy the future of the codebase or the company, because you were all lazy.

[–] Ledivin@lemmy.world 2 points 4 hours ago (2 children)

It sounds more like you didn't even read his comment and are just rabidly spewing anti-AI talking points instead of participating in the discussion.

[–] FiniteBanjo@feddit.online 1 points 1 hour ago

He let AI refactor his entire codebase because the team didn't understand each other's techniques/approach and nobody had any time or knowledge to do the work themselves. They literally did not understand how it worked so they asked the chatbot to redo it and now they still don't understand it but it appears to them as if it was improved.

What did you read?

[–] fonix232@fedia.io 0 points 2 hours ago

As they usually do.

[–] robert@piefed.ca 1 points 5 hours ago

Chill out dude

[–] fonix232@fedia.io 0 points 5 hours ago (1 children)

Please shut the fuck up if you have no inkling about what you're talking about.

[–] FiniteBanjo@feddit.online 1 points 1 hour ago

Eat my ass slopper