Login
You're viewing the mstdn.social public feed.
  • Jun 17, 2026, 8:46 PM

    @johnnythan That's a good point. 🙂

    I don't know how, but they somehow managed it that it usually does not output shitty code.

    Maybe rule compliance is better in AI than in humans, like writing and using tests, documentation, etc.

    Also, it can just try or look at some stuff much faster than humans can.

    Sometimes it is also running a wrong direction though, like a junior developer.

    That's why someone experienced has to look at the code and the design.

    💬 2🔄 0⭐ 0

Replies

  • Jun 17, 2026, 8:54 PM

    @borgbackup Me personally, I like coding. I like writing line after line and see what happens.

    I don't like (never did) to debug someone else's code.

    So that is why I rather program myself, instead of thoroughly checking code outputs from a machine. That is just no fun (for me).

    And: Main part is not writing code. I think most of the times that's the easy and fun part. Having a good structure, a future-proof architecture, that is where the real thinking lies.

    For me.

    💬 0🔄 0⭐ 3
  • Jun 18, 2026, 7:16 AM

    @borgbackup @johnnythan A thought: if people cannot always successfully distinguish "bad" code from "good" code when writing it themselves, often while working with those codebases for multiple years, can it be possible for them to distinguish "bad" code from "good" code when an AI wrote it?

    💬 1🔄 0⭐ 5
  • Jun 18, 2026, 4:08 PM

    @daniel_bohrer sure it is the same problem.

    also, if some contributor contributes code in a PR, you can not necessarily know whether AI was used or not.

    but for code review, it does not matter, you have to review it anyway to ensure that code quality is ok.

    overlooking something in review happens of course. AI can be useful as a 2nd or 3rd reviewer here, sometimes it finds stuff human reviewers have overlooked.

    💬 0🔄 0⭐ 0