DEV Community

Cover image for AI for everything besides coding

AI for everything besides coding

christine on October 28, 2026

I use Claude Code all day for my job. That part of my AI use is easy to describe: there's a repo, a ticket, a diff at the end. Chats are different...
Collapse
 
vrunda_chauhan_a52cc23b11 profile image
Vrunda Chauhan •

I like how you measured AI's value beyond just productivity. The most interesting examples are where AI helped uncover the real problem instead of simply answering the original question. The cat food smell and fragrance examples are perfect illustrations of that. Sometimes the biggest benefit isn't saving hours; it's making better decisions, avoiding unnecessary purchases, and discovering solutions you wouldn't have considered yourself. That's where AI becomes genuinely useful in everyday life.

Collapse
 
cseeman profile image
christine •

They were both truly helpful there! And I really do love my new fragrances, which is wild to think that it was AI that really helped me figure out I would like them.

Collapse
 
robertpaschal profile image
Odinaka Robert Nnamani •

The cat food cabinet bit is the best argument in here. A chat that points past the question to the source is doing real work.

Collapse
 
gaming_channels_04771f34d profile image
Cody Simons •

yeah that's right

Collapse
 
robertpaschal profile image
Odinaka Robert Nnamani •

That one stuck with me too. A pointer to the source beats a tidy answer that stops at the question.

Collapse
 
earlgreyhot1701d profile image
Earl Grey •

"The useful ones end somewhere else". It seems, to me, there's always something else to connect! 🤣 Start a chat here, finish the purchase or calendar update or booking there. Still not a seamless experience exactly but once we get there. Watch out!

Collapse
 
alexshev profile image
Alex Shev •

Reviewing actual chats instead of counting prompts is a useful way to evaluate the workflow. How did you distinguish time saved from cases where verification or correcting the answer consumed the apparent gain?

Collapse
 
cseeman profile image
christine •

I didn't really, It really was just me eyeballing it, thinking about about much time it takes me normally. Super not quantitative, but just an estimate of time. And you are right, in some cases it really didn't save time...and might have been a time suck in itself.

Collapse
 
alexshev profile image
Alex Shev •

A rough estimate is still a useful starting hypothesis. The next lightweight step is to sample a handful of tasks and record elapsed time, rework, and whether the output was usable without rescue. That separates "felt faster" from work merely moved into review.