4 ms·

Aren’t you also paying internal staff for their time. Waisting their time is waisting your money.

simonw 8mo ago
I've been in these situations before. If there's a known bug in an internal tool that would take the development team a day to investigate and fix - aka $10,000s - it's often smarter to send around an email saying "don't click the Froople button more than once, and if you do tell Benjamin and he'll fix it in the database for you". Of course LLMs change that equation now because the fix might take a few minutes instead.
- dns_snek 8mo ago
  > development team a day to investigate and fix - aka $10,000s What about the non-fictional 99.999999999% of the world that doesn't make $1000/hour?
  - bubblewand 8mo ago
    Large companies are often very bad at organizing work, to the tune of increasing the cost of everything by a large multiple over what you'd think it should be. Most of that cost wouldn't be productive developer time.
  - simonw 8mo ago
    It costs them single digit thousands instead.
- zahlman 8mo ago
  > If there's a known bug in an internal tool that would take the development team a day to investigate and fix - aka $10,000s - it's often smarter to send around an email saying "don't click the Froople button more than once, and if you do tell Benjamin and he'll fix it in the database for you". How much will Benjamin's time responding to those calls cost in the long run?
  - simonw 8mo ago
    Hopefully none, because your staff will read the email and not click the button more than once. Or one of them will do it, Benjamin will glare at them and they'll learn not to do it again and warn their coworkers about it. Or... Benjamin will spend a ton of time on this and use that to successfully argue for the bug to get fixed. (Or your organization is dysfunctional and ends up wasting a ton of money on time that could have been saved if the development team had fixed the bug.)
jimbokun 8mo ago
The alternative is the staff having no software at all to help with their task which wastes even more of their time.

I've been in these situations before. If there's a known bug in an internal tool that would take the development team a day to investigate and fix - aka $10,000s - it's often smarter to send around an email saying "don't click the Froople button more than once, and if you do tell Benjamin and he'll fix it in the database for you". Of course LLMs change that equation now because the fix might take a few minutes instead.

dns_snek 8mo ago
> development team a day to investigate and fix - aka $10,000s What about the non-fictional 99.999999999% of the world that doesn't make $1000/hour?
- bubblewand 8mo ago
  Large companies are often very bad at organizing work, to the tune of increasing the cost of everything by a large multiple over what you'd think it should be. Most of that cost wouldn't be productive developer time.
- simonw 8mo ago
  It costs them single digit thousands instead.
zahlman 8mo ago
> If there's a known bug in an internal tool that would take the development team a day to investigate and fix - aka $10,000s - it's often smarter to send around an email saying "don't click the Froople button more than once, and if you do tell Benjamin and he'll fix it in the database for you". How much will Benjamin's time responding to those calls cost in the long run?
- simonw 8mo ago
  Hopefully none, because your staff will read the email and not click the button more than once. Or one of them will do it, Benjamin will glare at them and they'll learn not to do it again and warn their coworkers about it. Or... Benjamin will spend a ton of time on this and use that to successfully argue for the bug to get fixed. (Or your organization is dysfunctional and ends up wasting a ton of money on time that could have been saved if the development team had fixed the bug.)

jimbokun 8mo ago

The alternative is the staff having no software at all to help with their task which wastes even more of their time.