It takes time, it takes me away from my actual job within my business, and frankly, the bread from the bakery is pretty good.
Customers will pay for something that's of benefit to them. That hasn't changed.
35 karma · joined June 4, 2026
It takes time, it takes me away from my actual job within my business, and frankly, the bread from the bakery is pretty good.
Customers will pay for something that's of benefit to them. That hasn't changed.
What's the mechanism, if not handing people cash and benefits if they support your cause?
But wow, how do you stand a chance in stopping anyone when your code is all there freely available in the browser
This leads to 'fixing' the amount of text areas it needs to fill, so it works to a constraint of having to fill a collection of text areas instead of outputting the message that would otherwise best suit.
My way to combat this is to start by refining the words/messages to be put on the canvas before letting the agent try designing something.
My initial thought was desktops generally run 24/7, with laptops running when in use. At least for the customer at the market intersection for this type of product.
Thank you for slogging through the slop to bring the human angle
I also use it to mark tickets as closed, and create new tickets from recordings of support calls.
None of this means the LLM does it while I'm off doing something else, or without me initiating it
I work with several small businesses, not a multi department large corporate.
In my company I use it to manage multiple Microsoft 365 clients. I control the server and keys for clients and manage azure roles, each of my technicians get permissions based on their azure role in my tenant.
In another company I work with, they use it to manage multiple tenants in a construction software platform.
Practical example: I can now ask Claude to grab the new user request that was emailed to me, and create the user and email the client back with details.
I think something people miss about "just using the API" is that managing keys and git repos is not something regular people do. The learning curve is too steep.
MCP SSO/OAuth and DCR means non-technical users can just paste in a URL and sign in, like they do with everything else.
There is some debate as to whether Homer was an individual or actually a title used by multiple authors.
I haven't looked at the code. How are you dealing with projects scattered across different environments, are you routing those notifications yourself back to a central imap store, or do you have several different stores?
It's like bringing two working sides in and finding the third side to bootstrap.