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.
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.
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
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
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.
This is amazing. Not interested in growing vampire teeth - but the ability to regrow teeth when lost - or get a new set of chompers without coffee stains sounds super cool :)
Devil's advocate...how much do we really care about these different distros at this point. The world lives out of the browser. As long as I have chrome and VS Code I'm pretty good to go.
Founder here. Debugging CI pipelines is a pain and it often feels like a slow, unproductive printf() debugging process. All of us who have gone through the tedious cycle of run->fail->log->fix->run->fail-> can attest to the massive waste of time it creates.
To change this, we built Trunk's CI Debugger. We initially built this for Trunk because we found that CI jobs were not stable and took multiple hours to track down the root cause of failure. The debugger gave our team a way to add conditional breakpoints, receive alerts on and debug our CI like you do your code.
You can see how this works for GitHub Action in our repo: https://github.com/trunk-io/breakpoint, but it works with any CI system you use - Jenkins, GitHub Actions, Buildkite, Circle CI.
To get started, check out our CI Debugger in the link above. We learned a ton building this tool, and I would love to hear your feedback and answer any questions you might have. Here's to making the debugging process in CI systems as seamless as it should be.
It’s also massively more performant
https://trunk.io/merge-queue