607 karma · joined August 19, 2016
Everyone and their cat can look at open source projects, which can and will result in being called out publicly. This can also have legal ramifications on the project itself.
It isn't a problem for me, more amusing than anything else (I run in Low Power mode 90% of the time) but worth knowing for anyone thats thinking about pushing the hardware to its limit 24/7.
The solution Valve came up with is quite brilliant.
Ecomm orders want to drop to the distribution center as soon as possible, which means you can't wait until you have a whole bunch of them just so you can analyze which addresses are on multiple orders. You would either need to 1) detect this in the warehouse systems (I spent my career working on these, so I can say with high certainty that is almost definitely Not going to happen, especially if they go through a 3PL) OR 2) you have to cancel orders after they have already dropped to the warehouse (which means wasted labor in the best-case scenario).
None of that is worth the effort to a company who is fundamentally still getting paid the same for the product regardless of if the purchaser is a scalper or not.
A skill wouldn't be a bad option though, and I highly recommend creating one yourself! The ability to customize our workflows and tools to a high degree is one of the largest strengths of agentic coding.
Ive had great success with it, and it rapidly speeds up development time at fairly minimal cost.
he AI is there to do the easy part; scan a giant spaghetti bowl and label each noodle. The humans job is to attach descriptions to those noodles.
Sometimes I forget that people on this site simply assume the worst in any given situation.
see, i actually read and monitor the outputs. i check them against my own internal knowledge. i trial the results with real trouble shooting and real bug fixes/feature requests.
when its wrong, i fix it. when its right, great we now have documentation where none existed before.
dogfood the documentation and you'll know if its worth using or not.
If there is an action you don't want them to ever take, dont provide them with the ability to do so.
What I give Claude is an API key that allows it to talk to the mcp server. Everything else is hidden behind that.
This is what I do, and I am 100% confident that Claude cannot drop my database or truncate a table, or read from sensitive tables. I know this because the tool it uses to interface with the database doesn't have those capabilities, thus Claude doesn't have that capability.
It won't save you from Claude maliciously ex-filtrating data it has access to via DNS or some other side channel, but it will protect from worst-case scenarios.