Added to this is the prevalence of people thinking that LLMs can allow them to do anything, whether or not they understand it
1971, Willy Wonka and the Chocolate Factory depicted a computer which could (but was refusing to for comedic effect) predict the location of the remaining golden tickets. There were, and probably still are, a shocking number of people who believe that was a realistic scene.
I have an operations manager thinking he can make pages for our Intranet - where does it store the data? How is access controlled? So many basic questions that an actual programmer would know to think of.
Option 1: hold his hand and educate him on what he lacks
Option 2: let him flounder and make fun of his mistakes (the making fun part should be done anonymously if you value your job)
Option 3: he’s bright enough to ask the important questions to you or the LLM and get reasonable answers
Option 3 has a very realistic chance of working, if 1) you have documentation for how you do these things today - even informal documentation, anything the LLM can read and extract the relevant patterns from, 2) the LLM must have access to that documentation, and 3) your manager needs the patience and perseverence to work the discovery process until it’s viable and sustainable.
Odds are, your operations manager is going to fall short on the patience and perseverence dimensions and offload the boring parts to you, after all why did he become a manager in the first place?
maybe better to just ask a pilot to do it.
Yeah, except you can’t make nightly backups of the plane’s passenger manifest. If you’re not making nightly backups, you’re already in catchup territory LLM or no.
it’s benefit to us (and the world) is nowhere near worth the monetary and environmental cost.
I suggest doing a little research into what exactly the monetary and environmental cost of YOUR usage is. People engaged in low-value usages (too many to even begin to imagine, Rule 34 needs expansion to start to cover them) are burning a lot of un-necessary tokens.
What I have read, consistently from various sources, is that my $20/month Claude code subscription burns $11 to 12 in electricity to serve my responses. My house burns over $13 in electricity per day in the summer, mostly for the air conditioning.
1971, Willy Wonka and the Chocolate Factory depicted a computer which could (but was refusing to for comedic effect) predict the location of the remaining golden tickets. There were, and probably still are, a shocking number of people who believe that was a realistic scene.
Option 1: hold his hand and educate him on what he lacks
Option 2: let him flounder and make fun of his mistakes (the making fun part should be done anonymously if you value your job)
Option 3: he’s bright enough to ask the important questions to you or the LLM and get reasonable answers
Option 3 has a very realistic chance of working, if 1) you have documentation for how you do these things today - even informal documentation, anything the LLM can read and extract the relevant patterns from, 2) the LLM must have access to that documentation, and 3) your manager needs the patience and perseverence to work the discovery process until it’s viable and sustainable.
Odds are, your operations manager is going to fall short on the patience and perseverence dimensions and offload the boring parts to you, after all why did he become a manager in the first place?
Yeah, except you can’t make nightly backups of the plane’s passenger manifest. If you’re not making nightly backups, you’re already in catchup territory LLM or no.
I suggest doing a little research into what exactly the monetary and environmental cost of YOUR usage is. People engaged in low-value usages (too many to even begin to imagine, Rule 34 needs expansion to start to cover them) are burning a lot of un-necessary tokens.
What I have read, consistently from various sources, is that my $20/month Claude code subscription burns $11 to 12 in electricity to serve my responses. My house burns over $13 in electricity per day in the summer, mostly for the air conditioning.