5 ms·

I think the article nails it, on multiple counts. From personal experience, the cognitive overload is sneaky, but real. You do end up taking on more than you ca

I think the article nails it, on multiple counts. From personal experience, the cognitive overload is sneaky, but real. You do end up taking on more than you can handle, just because your mob of agents can do the minutia of the tasks, doesn't free you from comprehending, evaluating and managing the work. It's intense.

varispeed 8mo ago
"Explain to me like I am five what you just did" Then "Make a detailed list of changes and reasoning behind it." Then feed that to another AI and ask: "Does it make sense and why?"
- coldtea 8mo ago
  Then get rid of. They can keep 1/10 the humans, and have them run such agents.
- salawat 8mo ago
  Garbage In, Garbage Out. If you're working under the illusion any tool relieves you from the burden of understanding wtf it is you're doing, you aren't using it safely, and you will offload the burden of your lack of care on someone else down the line. Don't. Ever. Do. That.
wnolens 8mo ago
This has been my experience too. I feel freed up from the "manual labor" slice of software development and can focus on more interesting design problems and product alignment, which feels like a bit of a drug right now that i'm actually working harder and more hours.
Tade0 8mo ago
Started referring to it as "speed of accountability". A responsible developer will only produce code as fast as they can sign it off. An irresponsible one will just shit all over the codebase.
Molitor5901 8mo ago
I'm not sure I would agree in totem. Freeing the minutia allows for a higher cognitive load on the bigger picture. I use AI primarily for research gathering, and refining of what I have, which has freed up a lot of time to focus on the bigger issues, and specifically in my case, zeroing in on the diamond in the rough.
- btbuildem 8mo ago
  > Freeing the minutia allows for a higher cognitive load on the bigger picture I think we do agree -- the higher "big picture" cognitive load feels more expensive than the minutia cognitive load
maccard 8mo ago
For a very small number of people the hard part is writing the code. For most of us, it’s writing the correct code. AI generates lots of code but for 90% of my career writing more code hasn’t helped. > you do end up taking on more than you can handle, just because your mob of agents can do the minutia of the tasks, doesn’t free you from comprehending, evaluating and managing the work I’m currently in an EM role and this is my life but with programmers instead of AI agents.
- snovv_crash 8mo ago
  Also EM and it feels like now I have a team of juniors on my personal projects, except they need constant micromanaging in a way I never would for real people.
- eloisant 8mo ago
  So you're saying AI doesn't help, and having reports is just like using AI (which you said doesn't help). What's stopping you from becoming an IC and producing as much as your full team then? What's the point of having reports in this case?
- throwaw12 8mo ago
  > For most of us, it’s writing the correct code. I am not sure about this statement, aren't we always cutting the corners to make things ~95% correct at scale to meet deadlines with our staffing/constraints? Most of us, who doesnt work on Linux kernel, space shuttles, and near realtime OSes, we were writing good enough code to meet business requirements
  - maccard 8mo ago
    My point is that coming up with the business requirements was always the hard part (unless you’re writing a scheduler)
- jakubtomanik 8mo ago
  Does AI write 100% correct code? No, but under my watch it writes code that is more correct than anything that anyone else on the team contributed in past year or more. Even better when it is wrong I don’t have to spend literal hours arguing with it nor I have to be mindful how what I’m saying affects others feelings so I get to spend more time on actual work. All in all it’s a net positive
moomoo11 8mo ago
That is fun though. I hated the old world where some boomer-mentality "senior" dev(s) would take days or weeks to deliver ONE fucking thing, and it would still have bugs and issues. I like the new world where individuals can move fast and ship, and if there are bugs and issues they can be resolved quickly. The boomer-mentality and other mids get fired which is awesome, and orgs become way leaner. Just because there are excess of CS majors and programmers doesn't mean we need to make benches that they can keep warm.
- sumtechguy 8mo ago
  That has more to do with where you work than AI. Some places have military grade paperwork where mistakes are measured in millions of dollars per min. Others places are 'just push it in fix it later'. AI is not going to change that. That is a people problem. Not something you can automate away. But you can fire your way out of it.
  - moomoo11 8mo ago
    For sure. I was replying to people not in that, it seems from the commenters here that is where they (and me) have worked or are working now. Whether it is their own company or some other place. I've only ever worked at places that are at the bleeding edge and even there we had total slackers.
    - anukin 8mo ago
      That’s totally orthogonal to what the OP is responding to though. Military software can be bleeding edge as well as extremely susceptible to error prone code which means you need to test more. Similar are the cases with financial softwares which are usually written in ocaml etc. observing your ability to comprehend, the places where you work must be “bleeding” profusely.
- wiseowise 8mo ago
  > I hated the old world where some boomer-mentality "senior" dev(s) would take days or weeks to deliver ONE fucking thing, and it would still have bugs and issues. What does that even mean? Are you begrudged manager or enthusiastic youngster who is upset that “boomers” are not killing themselves by juggling thousands of tasks ADHD-style?
skeeter2020 8mo ago
do you think this is inherent in AI-related work, or largely due to the current state of the world, where it's changing rapidly and we're struggling to adapt our entire work systems to the shifting landscape, while under intense (and often false) pressures to "disrupt ourselves"? Put another way, if this was similarly true twenty years ago with the rise of Google, is it still true today?

varispeed 8mo ago

"Explain to me like I am five what you just did" Then "Make a detailed list of changes and reasoning behind it." Then feed that to another AI and ask: "Does it make sense and why?"

coldtea 8mo ago
Then get rid of. They can keep 1/10 the humans, and have them run such agents.
salawat 8mo ago
Garbage In, Garbage Out. If you're working under the illusion any tool relieves you from the burden of understanding wtf it is you're doing, you aren't using it safely, and you will offload the burden of your lack of care on someone else down the line. Don't. Ever. Do. That.

wnolens 8mo ago

This has been my experience too. I feel freed up from the "manual labor" slice of software development and can focus on more interesting design problems and product alignment, which feels like a bit of a drug right now that i'm actually working harder and more hours.

Tade0 8mo ago

Started referring to it as "speed of accountability". A responsible developer will only produce code as fast as they can sign it off. An irresponsible one will just shit all over the codebase.

Molitor5901 8mo ago

I'm not sure I would agree in totem. Freeing the minutia allows for a higher cognitive load on the bigger picture. I use AI primarily for research gathering, and refining of what I have, which has freed up a lot of time to focus on the bigger issues, and specifically in my case, zeroing in on the diamond in the rough.

btbuildem 8mo ago
> Freeing the minutia allows for a higher cognitive load on the bigger picture I think we do agree -- the higher "big picture" cognitive load feels more expensive than the minutia cognitive load

maccard 8mo ago

For a very small number of people the hard part is writing the code. For most of us, it’s writing the correct code. AI generates lots of code but for 90% of my career writing more code hasn’t helped. > you do end up taking on more than you can handle, just because your mob of agents can do the minutia of the tasks, doesn’t free you from comprehending, evaluating and managing the work I’m currently in an EM role and this is my life but with programmers instead of AI agents.

snovv_crash 8mo ago
Also EM and it feels like now I have a team of juniors on my personal projects, except they need constant micromanaging in a way I never would for real people.
eloisant 8mo ago
So you're saying AI doesn't help, and having reports is just like using AI (which you said doesn't help). What's stopping you from becoming an IC and producing as much as your full team then? What's the point of having reports in this case?
throwaw12 8mo ago
> For most of us, it’s writing the correct code. I am not sure about this statement, aren't we always cutting the corners to make things ~95% correct at scale to meet deadlines with our staffing/constraints? Most of us, who doesnt work on Linux kernel, space shuttles, and near realtime OSes, we were writing good enough code to meet business requirements
- maccard 8mo ago
  My point is that coming up with the business requirements was always the hard part (unless you’re writing a scheduler)
jakubtomanik 8mo ago
Does AI write 100% correct code? No, but under my watch it writes code that is more correct than anything that anyone else on the team contributed in past year or more. Even better when it is wrong I don’t have to spend literal hours arguing with it nor I have to be mindful how what I’m saying affects others feelings so I get to spend more time on actual work. All in all it’s a net positive

moomoo11 8mo ago

That is fun though. I hated the old world where some boomer-mentality "senior" dev(s) would take days or weeks to deliver ONE fucking thing, and it would still have bugs and issues. I like the new world where individuals can move fast and ship, and if there are bugs and issues they can be resolved quickly. The boomer-mentality and other mids get fired which is awesome, and orgs become way leaner. Just because there are excess of CS majors and programmers doesn't mean we need to make benches that they can keep warm.

sumtechguy 8mo ago
That has more to do with where you work than AI. Some places have military grade paperwork where mistakes are measured in millions of dollars per min. Others places are 'just push it in fix it later'. AI is not going to change that. That is a people problem. Not something you can automate away. But you can fire your way out of it.
- moomoo11 8mo ago
  For sure. I was replying to people not in that, it seems from the commenters here that is where they (and me) have worked or are working now. Whether it is their own company or some other place. I've only ever worked at places that are at the bleeding edge and even there we had total slackers.
  - anukin 8mo ago
    That’s totally orthogonal to what the OP is responding to though. Military software can be bleeding edge as well as extremely susceptible to error prone code which means you need to test more. Similar are the cases with financial softwares which are usually written in ocaml etc. observing your ability to comprehend, the places where you work must be “bleeding” profusely.
wiseowise 8mo ago
> I hated the old world where some boomer-mentality "senior" dev(s) would take days or weeks to deliver ONE fucking thing, and it would still have bugs and issues. What does that even mean? Are you begrudged manager or enthusiastic youngster who is upset that “boomers” are not killing themselves by juggling thousands of tasks ADHD-style?

skeeter2020 8mo ago

do you think this is inherent in AI-related work, or largely due to the current state of the world, where it's changing rapidly and we're struggling to adapt our entire work systems to the shifting landscape, while under intense (and often false) pressures to "disrupt ourselves"? Put another way, if this was similarly true twenty years ago with the rise of Google, is it still true today?