[–] 63 points 11 months ago (5 children)

"Me want burger" directed at the microwave while it spins your frozen mid-tier burger.

It spits out a weirdly hot but cold "burger" after a minute. The bread is mush and the patty is frozen in the center, but it's a burger none the less.

"Wow and just think, in a decade everyone could be a 5star chef like me"

I like my microwave as much as the next person, and it has its usecase like any tool, but lets not start building microwaves into cars and fridges and washing machines.

  • source
  • Using AI on libraries you know inside and out (you know all the attributes of the classes you're working with and you know what the arguments are for every function) feels great. Using AI on libraries you're not familiar with will simply cause you to lose time because AI will give you code that returns different object types than the library is expecting. Then, instead of understanding why you're asking it to fix it, it will try variations of similar code and make up an excuse as to why now it's fixed, despite it having no clue what the problem was. Even if the code "runs" you'll have to refactor it anyways because code is not one size fits all.

    It can be useful to sparking creativity but if you're not reading documentation you're just looking busy while not accomplishing much

  • source
  • parent
  • context
  • [–] 5 points 1 year ago (1 child)

    Dude, writing code is the fun part, reviewing code written by others is time-consuming, difficult and boring. Why would you automate the fun out of coding and force yourself to review even more shit?

  • source
  • view more: ‹ prev next ›