

someone went through the leak and opened a proper pull request to open source it
https://github.com/anthropics/claude-code/pull/41518
the file tree looks less messy than in that screenshot, but damn, I didn’t think it would be 514k lines


someone went through the leak and opened a proper pull request to open source it
https://github.com/anthropics/claude-code/pull/41518
the file tree looks less messy than in that screenshot, but damn, I didn’t think it would be 514k lines




Share Tech Mono


I thought it was a given that, if it’s a phone app, you’re likely to want to carry it with you, not leave it on a desk with your computer.


that would still require the OS or user to spoof a location to actually prevent tracking. I hope they’d do that, but I wouldn’t expect them to.


HEL


that assumes
Possible? Sure. It’s also possible that I drink half a bottle of vodka on a Friday night and mess up with production.


fitting translation for “meta”

I’ve never worked on a codebase where using ORMs wasn’t better than rolling your own queries. What are people writing that they actually need the marginal performance gains? And even if that’s worth it, why not just use raw queries in your critical paths?
Every time I have to write or modify raw SQL it feels like I’m throwing away all my static checking features and increasing the chance of bugs, because I have no idea of the query matches my schema or if it’ll blow up at runtime.
I’ve done it quietly 4y ago, only told some closer relatives. It was kind of funny when relatives I wasn’t talking to told my closer ones that we were keeping in touch on WhatsApp, not even aware I wasn’t in the platform for over 6 months at that point.
Now after years and leaving 2 family groups, politics, and a whole lot of drama behind, I feel it was a great decision, and the only regret was not doing it earlier.
in order to crack down on
AIunprofitable bots
I’m sure they’ll have no issues allowing bots that align with their interests


you can’t compare it to the islands, because the GPS trace is in an area within that green circle, with a different scale. You can only look at the 300m scale in the bottom right, which looks in the ballpark of an aircraft carrier to me


The way I see it, for any code review there are going to be different levels of recommendation regarding the comments. When I review, I try to make it clear what’s optional (/ nitpick) and what I’d really like to see fixed before I can approve it.
So even making some assumptions, I can’t choose between 4 and 5 because optional and “less optional” changes are often in a same PR.
The only one I haven’t done much of is #3. That one looks better if one has questions about code that was already reviewed, merged, and it’s likely in production.


As with a lot of things in life, it depends.
I use 1-5 depending on the repo, who made the change, what the change is about, and how involved I am in the project.
Though the “time-frame” idea of #4 is usually replaced by conversations if it’s a coworker, as it’s more effective.
Q: about #3, do you mean on code that is already merged / committed to the default branch?


The problem is that you didn’t bring much, and it sounds like you’re trying to spread FUD yourself:


why are you making a post instead of replying to a comment?


so… some really basic shit that should have been expected in a pre-2010 update + AI
Well done, guys. I guess you gotta start somewhere.
actual open source option, fwiw
https://github.com/anomalyco/opencode