• ColdFenix@discuss.tchncs.de
    link
    fedilink
    arrow-up
    0
    ·
    11 months ago

    The trick is to split the code into smaller parts.

    This is how I code using ChatGPT:

    1. Have it analyze how to structure the program and then give me the code for the outline with not yet implemented methods and functions.
    2. Have it implement the methods and functions one by one with tests for each one.
    3. I copy the code and test for each method and function before moving on to the next one So that I always have working code.
    4. Despair because my code is working and I have no idea how it works and I have become a machine that just copies code without an original thought of my own.

    This works pretty well for me as long as I don’t work with obscure frameworks or in large codebases.

    • ch00f@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      11 months ago

      So my job (electrical engineering) has been pretty stagnant recently (just launched a product, no V2 on the horizon yet), so I’ve taken my free time to brush up on my skills.

      I asked my friend (an EE at Apple) what are some skills that I should acquire to stay relevant. He suggested three things: FPGAs, machine learning, and cloud computing. So far, I’ve made some inroads on FPGAs.

      But I keep hearing about people unironically using chatGPT in professional/productive environments. In your opinion, is it a fun tool for the lazy, or a tool that will be necessary in the future? Will employers in the future be expecting fluency with it?