you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 1 year ago (3 children)

You have to check it every single time, though, erasing any time savings. You're saving effort, maybe, but not time.

  • source
  • parent
  • hideshow 3 child comments
  • [–] [S] 1 point 1 year ago (2 children)

    You're absolutely saving time, checking that the code works is far less time consuming than writing it. Especially for stuff like UIs or service endpoints. I literally work with this stuff on daily basis, and I would never go back. There's also another aspect to it which is that I personally find it makes my workflow more enjoyable. It lets me focus on things I actually want to work on, while automating a lot of boilerplate that I had to write by hand previously. Even if it wasn't saving me much time, there's a quality of life improvement here.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 year ago (1 child)
  • [–] [S] 1 point 1 year ago

    Yes, I've seen this as well. First of all, 16 devs is a tiny sample, a far bigger study would be needed to get any meaningful results here. Second, it really depends on how experienced people are at using these tools. It took me a while to identify patterns that actually work repeatably and develop intuition for cases where the model is most likely to produce good results.

  • source
  • parent