3 ms·

How to avoid skill atrophy? Easy. Limit your use of LLMs. Intentionally practice. It's what I do. You're losing if you're handing your brain over to LLMs right

How to avoid skill atrophy? Easy. Limit your use of LLMs. Intentionally practice. It's what I do. You're losing if you're handing your brain over to LLMs right now, because companies would prefer to hire someone with more up-to-date coding skills, even if they then force them to use LLMs. So the winning move is to resist using LLMs for as long as possible. Stop fanboying the industry's attempted commodification of your work, and get back to the basics.

dfgg2 8mo ago
Man its really sad to see that this place seems to embrace LLMs with open arms and seems to have no care for the implicit costs and side costs of it. I have no interest in SWE - I focus on other fields. But, LLMs are a complete disaster of a product, as the more you use them the less you are engaging your own brain to tap into the knowledge you have to get shit done and move fast. LLMs are a mirage and the fatal flaw of a human is laziness. This lack of brain engagement is deadly. People dont realise how tough it is to get back once you've started to lose it. Its akin to the gym and muscles.
raw_anon_1111 8mo ago
If your only “skill” is “I codez real gud and turn well defined requirements into code”, you were commoditized a decade ago.
- devilsdata 8mo ago
  Huh? When did I say that was my only skill? Did you reply to the wrong comment?
  - raw_anon_1111 8mo ago
    Well an LLM only helps you code, coding is not a competitive skill in 2026. If your “work” can be commoditized by a next word predictor, it was going to be commoditized by someone willing to work for less than you make anyway
- py4 8mo ago
  1. No, implementing well defined requirements were not commoditized a decade ago. You still have to come up with the design and proper (efficient,correct,...) solution that respects the requirements. it was and still is the skill set of a L4/L5 SWE. 2. If you think LLMs cannot help with navigating ambiguity and requirements, you are wrong. it might not be able to 100% crack it (due to not having all the necessary context), but still help a lot.
  - raw_anon_1111 8mo ago
    You realize you are arguing my point? We are in complete agreement about #1. As far as #2, I came into a large project at my new at the time company last year one week before having to fly out to a customer site. I threw everything I could find about the project into NotebookLM and started asking it questions like I would ask the customer. Tools like Gong are pretty good to at summarizing calls. I agree with you on #2. I am at a point now where I am the first technical person after sales closes a deal and I lead (larger) projects and do smaller projects myself. But I realize remotely, my coworkers from Latin America are just as good as I am now and cheaper. I’m working on moving to a sales role when I see the time coming. It’s high touch and the last thing that can’t be taken over. I would never have trusted any L4 or L5 SWE I met at AWS anywhere near one of my customers (ProServe). But they also wouldn’t let me put code into a repo that ran an AWS service. Fair is fair If I remember correctly, the leveling guidelines were (oversimplifying). An L4 should be able to handle a well defined story An L5 should be able to handle a well defined Epic where the what is known bit not how An L6 should be able to lead a more ambiguous longer term project made of multiple Epics.
    - py4 8mo ago
      I was saying it was not commoditized a decade ago, but i feel it's getting commoditized *now*. So you seem to be basically saying SWE is over and it's time to move on to something that is primarily based on human-human interaction?
      - raw_anon_1111 8mo ago

dfgg2 8mo ago

Man its really sad to see that this place seems to embrace LLMs with open arms and seems to have no care for the implicit costs and side costs of it. I have no interest in SWE - I focus on other fields. But, LLMs are a complete disaster of a product, as the more you use them the less you are engaging your own brain to tap into the knowledge you have to get shit done and move fast. LLMs are a mirage and the fatal flaw of a human is laziness. This lack of brain engagement is deadly. People dont realise how tough it is to get back once you've started to lose it. Its akin to the gym and muscles.

raw_anon_1111 8mo ago

If your only “skill” is “I codez real gud and turn well defined requirements into code”, you were commoditized a decade ago.

devilsdata 8mo ago
Huh? When did I say that was my only skill? Did you reply to the wrong comment?
- raw_anon_1111 8mo ago
  Well an LLM only helps you code, coding is not a competitive skill in 2026. If your “work” can be commoditized by a next word predictor, it was going to be commoditized by someone willing to work for less than you make anyway
py4 8mo ago
1. No, implementing well defined requirements were not commoditized a decade ago. You still have to come up with the design and proper (efficient,correct,...) solution that respects the requirements. it was and still is the skill set of a L4/L5 SWE. 2. If you think LLMs cannot help with navigating ambiguity and requirements, you are wrong. it might not be able to 100% crack it (due to not having all the necessary context), but still help a lot.
- raw_anon_1111 8mo ago
  You realize you are arguing my point? We are in complete agreement about #1. As far as #2, I came into a large project at my new at the time company last year one week before having to fly out to a customer site. I threw everything I could find about the project into NotebookLM and started asking it questions like I would ask the customer. Tools like Gong are pretty good to at summarizing calls. I agree with you on #2. I am at a point now where I am the first technical person after sales closes a deal and I lead (larger) projects and do smaller projects myself. But I realize remotely, my coworkers from Latin America are just as good as I am now and cheaper. I’m working on moving to a sales role when I see the time coming. It’s high touch and the last thing that can’t be taken over. I would never have trusted any L4 or L5 SWE I met at AWS anywhere near one of my customers (ProServe). But they also wouldn’t let me put code into a repo that ran an AWS service. Fair is fair If I remember correctly, the leveling guidelines were (oversimplifying). An L4 should be able to handle a well defined story An L5 should be able to handle a well defined Epic where the what is known bit not how An L6 should be able to lead a more ambiguous longer term project made of multiple Epics.
  - py4 8mo ago
    I was saying it was not commoditized a decade ago, but i feel it's getting commoditized *now*. So you seem to be basically saying SWE is over and it's time to move on to something that is primarily based on human-human interaction?
    - raw_anon_1111 8mo ago