• EatATaco
    link
    fedilink
    English
    arrow-up
    5
    ·
    9 months ago

    Yeah, I was lucky that I snuck into my company’s pilot program for it.

    I’m impressed at how often it predicts what I’m about to do. The code almost always needs a slight bit of editing, but it almost always at least shaves a bit of time off of whatever task I was doing.

    I no longer go straight to stackoverflow, I always ask the copilot first. Sometimes even just phrasing the question in natural language, something I wouldn’t do it trying to find it via search or stackoverflow, is kind of like rubber duck debugging, and I’ll come up with the answer while writing it out.

    • Landless2029@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      9 months ago

      My fav thing is two things.

      1. It reuses MY OWN CODE STYLE. So if I ignore a suggestion and setup a try catch in my own quriky way it’ll actually reuse it later on when I’m scripting. This works best when you add comments for the sections you write FIRST. So you comment # create array for x data it’ll do that or try catch for query it’ll give you a suggestion for the next block right away.

      2. DEBUGGING. github copilot can see your terminal and script so it’ll give you a detailed breakdown and suggestions. Blew my mind the first time.