5 ms·

I could write the same comment myself. Also >30 years of experience. I actually think more than I used to, because I only get the hardest problems to solve.

by jwr 7mo ago

I could write the same comment myself. Also >30 years of experience. I actually think *more* than I used to, because I only get the hardest problems to solve. I mostly work on architectural documents these days.

qsera 7mo ago
>I only get the hardest problems to solve. So do you review all that code your LLM generates for you?
- jwr 7mo ago
  Yes, very much so, in detail. Just as I would with programmers. Also, LLM doesn't just "generate code" for me, we work together on design documents first. See, I started saying "we", because I found it to be such a good partner.
  - qsera 7mo ago
    So can you please describe the kind of coding that you had success with by using LLMs.
    - jwr 7mo ago
      No, because I do not understand what "kinds of coding" there are. Also, given the tone of this discussion, I am not sure I want to invest my time into it.
Lucasoato 7mo ago
This is a consequence of introducing LLMs in software development. If you imagine it as a pyramid that starts from the bottom, the easiest tasks that happen more frequently, to the top, the hardest challenges that happen once in a while, LLMs can definitely help in automating the base of such pyramid, leaving the human with an harder job to do because now he statistically encounters harder tasks more often. If this is the price to pay to unlock this productivity boost, so be it but let’s keep in mind that: - we need to be more careful not to burnout since our job became de facto harder (if done at the maximum potential); - we always need to control and have a way to verify what LLMs are doing on the easiest tasks, because even if rarely, they can fail even there (...but we had to do this anyway with Junior devs, or didn’t you?)
- qsera 7mo ago
  >anyway with Junior devs.. A junior dev is accountable, but an LLM subscription is not.
  - yomismoaqui 7mo ago
    If your email is on the commit, you are responsible.
    - deleted 7mo ago
      [deleted]
    - palmotea 7mo ago
      > If your email is on the commit, you are responsible. Humans shouldn't exist as whipping-boys for machines. It's a cop-out for shitty technology. People weren't designed for continuous passive monitoring and do really poorly at that task.
      - qsera 7mo ago
        Yea, pseudo autonomous driving and all that..

I could write the same comment myself. Also >30 years of experience. I actually think *more* than I used to, because I only get the hardest problems to solve.

by jwr 7mo ago

qsera 7mo ago

>I only get the hardest problems to solve. So do you review all that code your LLM generates for you?

jwr 7mo ago
Yes, very much so, in detail. Just as I would with programmers. Also, LLM doesn't just "generate code" for me, we work together on design documents first. See, I started saying "we", because I found it to be such a good partner.
- qsera 7mo ago
  So can you please describe the kind of coding that you had success with by using LLMs.
  - jwr 7mo ago
    No, because I do not understand what "kinds of coding" there are. Also, given the tone of this discussion, I am not sure I want to invest my time into it.

Lucasoato 7mo ago

This is a consequence of introducing LLMs in software development. If you imagine it as a pyramid that starts from the bottom, the easiest tasks that happen more frequently, to the top, the hardest challenges that happen once in a while, LLMs can definitely help in automating the base of such pyramid, leaving the human with an harder job to do because now he statistically encounters harder tasks more often. If this is the price to pay to unlock this productivity boost, so be it but let’s keep in mind that: - we need to be more careful not to burnout since our job became de facto harder (if done at the maximum potential); - we always need to control and have a way to verify what LLMs are doing on the easiest tasks, because even if rarely, they can fail even there (...but we had to do this anyway with Junior devs, or didn’t you?)

qsera 7mo ago
>anyway with Junior devs.. A junior dev is accountable, but an LLM subscription is not.
- yomismoaqui 7mo ago
  If your email is on the commit, you are responsible.
  - deleted 7mo ago
    [deleted]
  - palmotea 7mo ago
    > If your email is on the commit, you are responsible. Humans shouldn't exist as whipping-boys for machines. It's a cop-out for shitty technology. People weren't designed for continuous passive monitoring and do really poorly at that task.
    - qsera 7mo ago
      Yea, pseudo autonomous driving and all that..