> No one is ever going back and reading individual commits.
I violently disagree with this.
At a minimum, when I review PRs I look at the commit history to understand what's up. If the path that was taken to commit this is full of "oops" and "fix" messages, it's an immediate reject for me. The commits tell the story and it's a kindness to your human reviewers to not make them work harder to understand the point you're trying to get across.
Can't use the Twitter links if you don't have a Twitter account. Also, why make the user click away when they're trying to understand if your product does something interesting, and why do they need an account on an unrelated service when an image/gif embed would get the message across in 5 seconds?
This is one of those ideas that would really benefit from a short video demo, gif, or even a screenshot directly in the README. Otherwise, the title reads like a "Curtains for Zoosha?" meme. [0]
.gitignore doesn't have the same security implications.
If you fail to prevent a private key from being added to your repository, you can reverse this and purge it from the blobs and reflog as if it never happened.
If you fail to prevent OpenAI from ingesting a private key, you have created a security incident.
TIL about Windows Sandbox. Not a Windows user myself (it's the Year of Linux on the Desktop™!) but this sounds immensely useful for technical and nontechnical users -- sort of a super-disposable container with UI? https://learn.microsoft.com/en-us/windows/security/applicati...
> It was such a simple concept but it worked so well. Wouldn't be able to do something like that anymore due to all manner of sandboxing in action. Lost a tool, gained security.
This class of programs absolutely still exists (see: every debugger, scanmem, GameConqueror, etc.).
Sandboxing doesn't prevent processes from inspecting the memory of other processes, it just prevents the sandboxed process from doing things it shouldn't.
My understanding is that it's not that the _models_ are banned, but rather the _platform_ is banned. It is acceptable to host, say, `deepseek-r1-distill-qwen-7b` and run it yourself, for example. It is not acceptable (to the authors of these bans) to download the DeepSeek app and run it on your work device.
It's much harder to search using an AST tool for a human. It's certainly harder than grepping, for example. I use AST tools myself, but it takes a while to represent a complex structure in a big codebase when I need to look for that.
It's not always amenable to grepping. But this is a great use case for AST searches, and is part of the reason that LSP tools should really be better integrated with agents.
I think Cloud Run has many nice features that Heroku's apps don't. However, Heroku's services ecosystem and the easy bindings don't have a direct Cloud Run equivalent, imo, and are inferior in the GCP world.
We've been writing with our hands for thousands of years. I suspect that on balance a Butlerian Jihad against AI slop would be perfectly fine for our hands.
I violently disagree with this.
At a minimum, when I review PRs I look at the commit history to understand what's up. If the path that was taken to commit this is full of "oops" and "fix" messages, it's an immediate reject for me. The commits tell the story and it's a kindness to your human reviewers to not make them work harder to understand the point you're trying to get across.