> It does not control for commit complexity, security intensity, or bug severity. It does not distinguish between a one-line typo fix and a CVE patch. It is a blunt instrument. But the critics' accusation is also blunt: "Claude is making things worse." A blunt instrument is the fairest response.
If by fairest you mean to say that this analysis and response is sufficient, then I'm sorry but I have to disagree. We really need to understand if the nature of the bugs are worse from a user's perspective. Even if the rate stayed unchanged, if the result is the perceived quality of the software declined then I would personally consider that worse, especially if I were a project maintainer.
That's not meant to be wholly dismissive either. But in general, I don't think quantitative analysis alone is enough to fully answer this type of question.
But it is fair. Up to this point I have yet to see anyone say they did an analysis of the code and found X regressions of Y severity. All they say is "there are more bugs because LLM". This analysis, which you can verify yourself if you wish, says "the bugs [number of] are pretty average even with LLM", which is a direct response to that. If you'd like a more nuanced analysis you're welcome to do one and share the result, if you're so inclined.
That which is asserted without evidence can be dismissed without evidence. This is more evidence, and of greater rigor, than was used to make the assertions. That's good enough for me. If someone wants to actually do the work to support the original claims with better evidence, great. I'd love to see it. Until then, I'm going to not worry about this issue.
If you have an internal CRM and are maintaining a Zendesk integration to create support tickets within your product, you've likely already done half the work needed to instead create those tickets in your own internal CRM tool yourself. This makes a lot of sense.
As someone who's had to maintain a Zendesk integration such as this for a large app it's hard to understate the benefit of having all that support info so close to the rest of your user's data. I have seen a huge amount of effort go into trying to get just the right balance of data in and out of ZD. Also helps alleviate concerns with sharing too much customer data with a third party.
This definitely isn't the right call for everyone, but there's a lot of upside if it can work for your organization.
Agreed, this got me thinking maybe I should try something similar with my own old macbook pro. They did mention that this was the first time they had soldered anything, so it's great that they went for it and it worked! So now it's just a matter of improving technique.
Long term, that may need to be redone. Really want less exposed wire in the final product, tin the tips of the wire first so they don't suck up the solder and trim to the appropriate length(only a bit bigger than the size of the pads at most). This is a good example on tinning: https://www.youtube.com/watch?v=pRPF4wpXX9Q And if you need to expose a lot of wire then just use some heatshrink so it's not exposed once you're done.
In a perfect world, you'd want to remove all the existing solder and then re-solder everything. But de-soldering can be its own skill and isn't always strictly necessary. Just something more to work toward.
No it's not strange. As someone who enjoys playing music I have heard a lot of music that doesn't suite my particular tastes, but appreciated the artistic talent of the people creating it because I truly believe they are talented. If you dig below the surface level you can find plenty to appreciate about how something is created, even if the product isn't for you.
You can find something to like about a lot of things. I also enjoy watching videos about wristwatch repairs and seeing the construction of them. However, I do not want one and would never wear one.
“Venezuela is completely surrounded by the largest Armada ever assembled in the History of South America. It will only get bigger, and the shock to them will be like nothing they have ever seen before — Until such time as they return to the United States of America all of the Oil, Land, and other Assets that they previously stole from us.”
This along with other direct quotes from officials is what led me to the conclusion that, yes, oil is a large factor.
The problem is that you can't cherry-pick quotes from this administration and use them as a source of truth like you could with previous administrations.
Especially from Mr. Trump, who says something and then an hour later states the opposite. (See his record on solar, electric vehicles, various personnel and congressmen.) Keeping people guessing is part of this administration's strategy, and is inherited from how he did business.
It wasn't just him making such quotes, as I indicated before, and I made no attempt to make an exhaustive account of such statements which can be easily found elsewhere. It's very reasonable to conclude that that is an issue at play here. That is all I attempted to convey.
I think these are valid concerns for a project maintainer to think through for managing a chosen solution but I don't think there is a single correct solution. The "correct", or likely least bad, solution depends on the specific project and tools available.
For bug reports, always using issues for everything also requires you to evaluate how long an issue should exist before it is closed out if it can't be reproduced(if trying to keep a clean issue list). That could lead to discussion fragmentation if now new reports start coming in that need to be reported, but not just anyone can manage issue states, so a new one is created.
From a practical standpoint, they have 40 pages of open discussion in the project and 6 pages of open issues, so I get where they're coming from. The GH issue tracker is less than stellar.
Absolutely. What sound pretty cool, and different, here is CalPrivacy would be required to build a request mechanism that's one request sent to every data broker.
They open themselves up to a lot of risk, but more likely they only comply when CA residents are concerned or stop collecting for CA residents. Good question about outside the USA. Makes me wonder if there may end up being some sort of data broker safe havens setup, like we've seen with banking.
California will take them to court and/or block them from doing business in the state, have various ways to penalize them, etc. California is big enough that many will want to play game with them and having a state as powerful as California on board will get other states to jump on board and pass their own legislation and take up the same tactics with non-complying companies. Once it gets enough traction at the state level, the fed will step in because this will affect interstate commerce and that is federal jurisdiction. This is how state sovereignty works, it is not that states can do as they please, they can only do it up until the point it affects other states or crosses the line with federal law.
The GDPR lets someone request deletion of their data and there are legal teeth to force a business to comply, but that's 1:1. Maybe I need to dig deeper, but this specifically applies to data brokers it seems. That's great and it being a one to many request is fantastic, but sounds like it may not apply to just anyone who has data on you like the GDPR...
The gist of the GDPR in that respect is it allows someone to request a record of what data a particular business has gathered about them as well as request deletion of that data. It also introduced a lot of restrictions around what can be done with a particular subject's data, like sharing with third parties.
The BQ dataset is only ~17GB and the free tier of BQ lets you query 1TB per month. If you're not doing select * on every query you should be able to do a lot with that.
If by fairest you mean to say that this analysis and response is sufficient, then I'm sorry but I have to disagree. We really need to understand if the nature of the bugs are worse from a user's perspective. Even if the rate stayed unchanged, if the result is the perceived quality of the software declined then I would personally consider that worse, especially if I were a project maintainer.
That's not meant to be wholly dismissive either. But in general, I don't think quantitative analysis alone is enough to fully answer this type of question.