Apples and oranges. They presumably already have some sort of evidence in order to get a warrant and are under criminal investigation.
According to the article the agents said it was just a normal part of screening.
476 karma · joined January 4, 2024
Apples and oranges. They presumably already have some sort of evidence in order to get a warrant and are under criminal investigation.
According to the article the agents said it was just a normal part of screening.
Now, if it's something minor, I'll ask Claude about it, and get the gist of what I need to do, and just do it myself.
That's definitely a downside of a minimal MD and I could def be wasting tokens. I've tried to scope the tasks such that it won't feel the need to scan unnecessary files, but it's not bulletproof.
I don't need to tell the agent my tech stack, what DB access library I'm using, the way in which I write my tests, etc. Why? Because it's all very clearly spelled out within the code itself. I've gone great lengths to make sure that my fairly complex domain can be understood by a person with little domain knowledge, which means it should certainly be understood by a tool that has a wealth of it.
These tools work pretty well out-of-the-box. I'm sure I could squeeze out better token usage or streamline some tool calls, but it's not something I really want to focus on. Just like I don't want to endlessly configure my IDE, I don't really have patience with spending time on anything besides actually building something.
> Now this rule will either be never applied or when it's applied it will be an arbitrary decision made with mostly inconclusive "evidence".
Or people just lie. Which is the whole problem with not having a strong way to determine code's origin. And it's also a tad ridiculous because if done correctly, the seams between my thoughts and those of the agent shouldn't be apparent. If it's utilizing existing patterns in my codebase that I've written by hand, then you wouldn't even know.
My point is that the idiom has now come to mean "I disagree with your tech choices".
Every answer is met with "But did you think about X", or "One more thing to consider" and it almost starts to feel manic as you dig down that hole.
Multiple times I've had to literally say "Stop with the follow-ups and suggestions. Just answer the questions clearly".
How does this support your argument? The tech didn't even exist in the 80s or 90s.
Saying "They wouldn't have made the same choices 40 years" is meaningless in this context. There's a lot of things they wouldn't have done back then that we do today. And this is a field that has been changing by the week recently, which makes even less appropriate.
This idiom now apparently means "I disagree with your tech choices" or in your case, "Someone 40 years ago would disagree with your tech choices".
"I'm using technology I know that will get us there" is not the same as treating every problem as a nail. It's making a practical choice that probably also had time constraints and other factors we don't know.
Not if you're in enterprise dev. You have 2 types of accounts: Microsoft and Google. Not because you want to, but because that's reality and it's practical.
What I'm saying is if you're an enterprise dev and you don't have a Microsoft account of some type that's a failure on your part. It's part of the job.
But regardless, what alternative would you propose? Did it contain any sensitive information? Does the alternative integrate with your current system? Do people need to create accounts for it like Dropbox? Do I have to teach all of the employees how do use this new service instead of just right-clicking and sharing the file?
SFTP is a no-go for obvious reasons. I can't even get people to stop clicking birthday initiation links from Australia (we're in the US) let alone teach them how to use FTP.
Dropbox would require a dropbox account. 100% not going to push another piece of softare on them when our current software already does.
Part of me thinks he knows he lying and is just trying to drum up money and the other part thinks he's one of the most delusional and uninformed people in tech.
One of the challenges for their team I'm assuming is making sure the release notes also get copied to the actual documentation. This was one case where I thought the same thing and only until reading the release notes realized it was already a feature.
Also, Claude refuses political stuff in general, not just your specific beliefs.
EF Core is provider-specific and also exposes provider-specific functionality.
> 4. You end up not wanting to use the objects directly anyways, so you end up with object-object-relation, needing a mapping layer from your database-object to your business-objects, which also defeats most of the benefits from change-tracking
This just isn't true for EF Core. https://learn.microsoft.com/en-us/ef/core/performance/effici...
> 5. The generated SQL is periodically utterly nuts, so you have to review every generated query anyways
Not universally true either. You only have to review complex queries. If you're making claims about a specific ORM it would be good to mention it as it's not universal.
> 6. You probably dont want to actually use any of the OOP mapping features like inheritance in your DB
Then don't? Since when is inheritance required for ORM-usage?
I have found a lot of the anti-ORM critiques come from either using a crappy ORM or having not used a good one in the last 5 years.
Entity Framework in particular has come a long way in this regard. Particularly owned & complex entities, value converters, etc.
https://learn.microsoft.com/en-us/ef/core/modeling/
> Worst case it creates a weird database-contaminated domain model that's hellish to maintain.
CQRS is good for this because it forces you into using a different write and read model. My write models are domain objects and my read models are DTOs that feed the UI and via projection I can shape them without issue.
It's wild having to argue with people who say demonstrably untrue things and then refuse to admit that what they said was wrong.
But this is exactly the point I'm making. If the code is carefully reviewed, targeted, and tested, then why make people have to lie in order to submit PRs?
Why not just say "Irresponsible use or agentic-based PR's will be auto-rejected"?
And that's not even mentioning that tools like Github Copilot can just act like fancy autocomplete. There are dozens (if not hundreds) of different ways to use these tools.
I guess I'm just really not sure how you can unequivocally forbid these insanely powerful tools when they are almost certainly going to be a large part of developer's workflows going forward?
AI can be trained. Also, AI can create code that improves the community. It's replies like this that leave me even more confused.
Says who? How can you say I'm categorically wrong when your entire point rests upon an opinion?