Caveat it's AI coded

It's much more than I put in the title but the video does a better job of explaining it. It's also an ad for a 3D scanner

you are viewing a single comment's thread
view the rest of the comments
[–] 26 points 5 days ago (11 children)

All of the things I enjoy doing have been automated

Programming too

  • source
  • hideshow 11 child comments
  • [–] 2 points 5 days ago (9 children)

    Writing code is beung automated. Programming still works best when a human is in the loop. We just have more time for the other aspects of programming. Which are in my opinion the more creative aspects

  • source
  • parent
  • hideshow 9 child comments
  • [–] 9 points 5 days ago (6 children)

    I think you will find that not everyone enjoys the “creative aspects” of programming.

  • source
  • parent
  • hideshow 6 child comments
  • [–] -2 points 5 days ago (5 children)

    True, but the programmer type-monkeys will have to adapt to this change though...just like other production workers have through the times.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 9 points 5 days ago (4 children)

    You probably misunderstood the parent's message.

    From what I can see online, there are 2 kinds of expert programmers:

    • some care only about the problem being solved, and not how. They'll go out and about saying AI is amazing, because they can just prompt and get something mostly working out of it. If they'd have to solve a sudoku for work, they'd ask the sudoku-solving machine to solve it and be happy about it, because they solved the problem.
    • some care about how to solve the problem and not exactly the problem being solved. Architecture, code quality and process is the part that gives satisfaction. They see coding as solving a sudoku, and the joy is finding a smart solution, not having the sudoku solved at the end. If the code quality can't be kept, then they'd ask to change the problem being solved. AI is a disaster for them.

    I'm definitely part of the second camp btw. AI enables the first kind of people to go wild and generate slop code, while at the same time removing the joy they find in programming. Work is becoming horrible for me, because AI destroyed any satisfaction I have when coding

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 4 days ago

    I can add to this, I work in a space where cybersecurity compliance is mandated. I’m a software architect. Slop coded apps combined with AI literally brute forcing vulnerabilities leads to a shitty outcomes for everyone.

    Two carpenters can build a table. One has uneven legs, isn’t stained or sealed, and has a crack in the middle. The other is measured properly, the joints and seams are well sanded, and the table has been oiled and sealed. Both “solve the problem”. Only one of them is actually reliable and useable. (And no, the AI didn’t make the good one)

  • source
  • parent
  • [–] 2 points 3 days ago

    Disclaimer: I care a lot about the problems being solved than the nth degree of how.

    That said, although we make a ton of use of agentic development at work we're still making the system design and architecture choices by hand.

    There are certainly some team members who miss doing things like figuring out how to solve a puzzle, but we've had a ton more time to focus on system stability and performance.

    I would argue that there's a third class of engineering: the splashy YOLO. We have one of those. The boss's boss loves the output, but the implemetaions are dog shit. We now have a personal atlassian token committed to the repo and said grand boss isn't technical enough to see why that's an issue.

  • source
  • parent
  • [–] 2 points 5 days ago

    You described my comment better than I did. How to solve the problem is infinitely me interesting to me than typing the characters on the keyboard. Personally I am trying to adapt to using AI as a tool for exploring how to done problems, rather than just writing “Copilot fix this problem for me”

  • source
  • parent
  • [–] 0 points 5 days ago*

    I would argue that figuring how to solve a problem, especially a novel problem, is the creative part of programming and the part that requires the actual skill. Punching the keys to implement it is the non-creative part I.e. what the type-monkey does.

    Unless the person weighs in, we can only guess what they meant.

  • source
  • parent