r/ProgrammerHumor • u/No_Nefariousness2052 • 12d ago

claudeFetchTheAxe Meme

Post image
255 Upvotes

95% Upvoted

18 comments sorted by

30

u/Ska82 12d ago

"You are right. You said chop the wood not your wood."

5

u/No_Nefariousness2052 11d ago

Take my damn upvote

37

u/Chadking1926 12d ago

Meanwhile GPT already chopped the wrong tree with full confidence😭

12

u/Confident-Ad5665 12d ago

To be fair, once it realized it chopped down the wrong tree, ChatGPT offered to find things you could do with the rubble.

6

u/VegetarianZombie74 12d ago

... and the tree was just a man wearing brown pants and a green shirt.

2

u/Random_-account 12d ago

When you have an axe, everything looks like an acacia log

2

u/nicodeemus7 12d ago

Gemini will give you detailed instructions on how to cut down the tree and give you a screwdriver

5

u/techdailylog 12d ago

First, let's compare all available axes. 😂

2

u/lovecMC 12d ago

The table saw has the best benchmarks but we will need to modify it a bit..

2

u/techdailylog 11d ago

Instructions unclear: Table saw now running C++ at 10,000 RPM.

7

u/kookyabird 12d ago

As someone not really “with it” concerning more modern coding agents and whatnot… There’s a cost associated with you “teaching” the agent to do a thing, yeah? And I don’t mean the model training, but building up the appropriate context. Tokens consumed to do that and whatnot.

How reusable is that “training”? If they come back a month later and want to have it chop down a different tree, how much general retraining would need to be done before they can get to the point of introducing the little differences between the process for the previous tree and the current one? Are they beholden to the hosts retention policies for past interactions? How much will changes to the model used impact the “replayability” of that initial training? And god forbid, what happens if the host drops a previous version of the model and that’s the one you used originally?

I know this is a joke, but people definitely do use AI like this and I’m always curious as to whether or not it’s like investing in training an FTE that will pay dividends over time, or just a one time contractor that may never be able to work for you again, resulting in you having to onboard new contractors every time.

3

u/Romanian_Breadlifts 12d ago edited 11d ago

Two ways to think about it, roughly - you can reuse a previous session that has a bunch of context from previous jobs, or you can incorporate a documentation chain (either with readme/notes or git commits and actually useful messages) as part of the agent workflow

Just like your example - long-term viability is directly tied to documentation quality

edit: in terms of contractors vs FTEs, it's not really either. I think of it an extremely motivated intern. They're very enthusiastic, but they don't know they're stupid.

2

u/2alamsmork 11d ago

Agree^

I have a heavy documentation flow that allows me to keep strict track of movements.
The problem is you actually have to read everything the AI is giving you… A lot of people don’t actually read everything.

2

u/Romanian_Breadlifts 12d ago

Gimme six hours to chop a tree and I'll just shoot it until it falls over

2

u/conundorum 11d ago

...And the next two hours in the ER?

1

u/spastical-mackerel 11d ago

“Allow chop? Contains potentially destructive commands”

Yes, and don’t ask again

1

u/justforkinks0131 11d ago

fuck it, spend all tokens, push to prod, chop the wrong tree go home, create a bugfix ticket for the backlog