It's doing context management in the same way, but adds a learning loop based on code reviews. Currently works with Gitlab, Forgejo and Gitea but happy to accept a PR for Github support or co-write it.
> In the space of a single hour, Muneeb deleted around 96 databases with US government information. He downloaded 1,805 files belonging to the EEOC and stashed them on a USB drive, then grabbed federal tax information for at least 450 people.
Maybe whoever runs infosec at that place should also be fired?
No idea. The people that have no need to run real software and want a high end device probably have an iPad with a keyboard case. Those that want a low end device have a chromebook.
Same here, working with a team that knows Java, so I'm letting Claude write Java.
If I compare the results to another team that uses Python with Claude I see slightly better results on the Java side. Not because Claude knows that better, but because the tools are more rigid by default which creates more of a self correcting loop for Claude. The Python side has Pydantic, but it's a bit of an afterthought, while in Java you can't skip the type checking.
In the end you can do the same things on both sides, it's 95% a team/engineering culture difference. So pick the language that the team knows best.
Undeclaring someone dead is one way to fix it, but you could also issue a new birth certificate, SSN etc and have minted an entirely new citizen :-) free of debt and ownership, uneducated and unemployed on paper but somehow quite experienced.
These people mostly contribute via transaction fees, for Amex for example more than half of revenue is from transaction fees instead of interest. Unfortunately for the credit card companies, an economic downturn also reduces spending by the financially stable people. So transaction fees are also affected.
And localhost being the exception is often quite painful - I've stuck into several projects that worked just fine on localhost, and then were a pain in the neck to convert to run in secure contexts
reply