This absolutely has been the case for me for the last few months. But what’s disheartening is that this signal will just be mimicked through simple prompting if too many people start tuning in to it. Or maybe that’s already happened?
Detection of copy-pasta is interesting - what it's calling out is not a deficiency in LLM's to code but in agentic rules in place that should just remind the agent to refactor into a common function when appropriate.
>> that should just remind the agent to refactor into a common function when appropriate.
This off-the-cuff statement buries so much complexity. Sure it catches new code the exactly implements existing code, but IME it is __way__ more common to need to slightly (or not so slightly) change existing code that can now be used by multiple consumers, and then delete the new "duplicate" code. That is not trivial and requires (1) judgement from your AI coder and (2) deep reviewer expertise from your human coder.
We already are performing our own unintentional form of geo-engineering with our relentless pumping of CO2 into the air. That said, not sure blocking the sun is our best plan right now for avoiding the worst of climate change. Instead of trying to have our cake and eat it too, we need to accelerate our focus on reducing carbon output, decarbonize electricity and transportation, and invest in massive amounts of energy production to the point where energy is so cheap we can use it to pull carbon from the air.
Agree on the last point, but the net zero strategy is a losing game. We can't reduce fast enough to avoid the multiplier effects (slowing heat exchanges in atmosphere and ocean currents, loss of polar reflectance, thawing of sea floor and boreal methane deposits, etc.).
The only way out at this point is fusion/fission and using excess power to decarbonize.
Population reductions in the developing world would help too, since that's where the majority of global carbon will be emitted over the next 50 years.
Working at Microsoft back in the early 00s I spent a lot of unfriendly hours with windbg. On one particular project we hunted for a terrible crash for months until it was uncovered that we were compiling against the single thread CRT when using threads extensively...whoops
fair point. I think I've just been burned too many times by dependabot looking to update single ts packages with single line changes. it's default configuration is overly aggresive
Dependabot doesn't try to guess what's in the changes. It can't really tell anyway. A trivial 1 line change may be either "this box is now 1px further to the right", or "a critical bug which will delete all your data tomorrow is fixed". It's up to dependabot to report any change available.
The security breaches be damned - the UI was terrible / constantly prompted me to store credit card info in LastPass and I was just not interested...but couldn't get it to stop this. deleted and moved to Dashlane.
I think a lot of the app currently in a phone make more sense on a heads up display. The main problem is the clumsyness of touching your glass to interact with it. And I think Meta neural wristband solves it.
