It does--but a particular form of Capture The Flag where there is a computer system and the "capturing" is breaking in or exploiting a security issue in that system.
every line of code is a liability. open, closed, doesn't matter. companies will have to treating it that way--which means actual engineering--or they will get burnt, and hard.
> Working software over comprehensive documentation
this is 100% backwards for anything safety-critical or that needs to be maintained past a butterfly's lifetime. this is what encourages yolo-driven-development instead of considering what actually should be done, and this is why agile or Agile or whatever formalization or bastardization of it can not be considered software engineering, but merely code monkeying.
I would love to use the drive units from a Tesla in a conversion project. Unfortunately, they're cryptographically paired with the main computer, and there's no way to use them.
Interesting! I am getting tired of looking at Roundcube and having weird issues and was thinking of doing the same. Were you planning on making the result public?
It's really difficult for me to understand the level of cynicism in the HN comments on this topic, at all. The amount of goalpost-moving and redefining is absolutely absurd. I really get the impression that the majority of the HN comments are just people whining about sour grapes, with very little value added to the discussion.
I'd like to see someone disagree with the following:
Building a C compiler, targeting three architectures, is hard. Building a C compiler which can correctly compile (maybe not link) the modern linux kernel is damn hard. Building a C compiler which can correctly compile sqlite and pass the test suite at any speed is damn hard.
To the specific issues with the concrete project as presented: This was the equivalent of a "weekend project", and it's amazing
So what if some gcc is needed for the 16-bit stuff? So what if a human was required to steer claude a bit? So what if the optimizing pass practically doesn't exist?
Most companies are not software companies, software is a line-item, an expensive, an unavoidable cost. The amount of code (not software engineering, or architecture, but programming) developed tends towards glue of existing libraries to accomplish business goals, which, in comparison with a correct modern C compiler, is far less performance critical, complex, broad, etc. No one is seriously saying that you have to use an LLM to build your high-performance math library, or that you have to use an LLM to build anything, much in the same way that no one is seriously saying that you have to rewrite the world in rust, or typescript, or react, or whatever is bothering you at the moment.
I'm reminded of a classic slashdot comment--about attempting to solve a non-technical problem with technology, which is doomed to fail--it really seems that the complaints here aren't about the LLMs themselves, or the agents, but about what people/organizations do with them, which is then a complaint about people, but not the technology.
Especially as congress has, for as long as I remember, been about the superset of infosec, society, art, etc. IMHO it's more along the lines of complaining about any ride that isn't a roller coaster at a theme park--no one is forcing you to go on any rides, other people clearly enjoy them, they're not taking anything away from your roller coaster, and having them increases the diversity of the crowd in an ultimately positive-for-everyone way.
Some people just like to complain that they have to take a shower and can't harass women like they used to like they could when congress was at the BCC and that kind of nonsense didn't immediately get you thrown out like today.
I came here to post this. We make a lot of the same sorts of optimizations for our OS distro (debian based) -- disabling frequency scaling, core pinning, etc. Critically, CPU0 has a bunch of stuff you cannot push, and you're better off with using one of the other cores as an isolated island.
This is what the scheduler latency looks like on our isolated core:
# Total: 000300000
# Min Latencies: 00001
# Avg Latencies: 00005
# Max Latencies: 00059
# Histogram Overflows: 00000
My big issue with this study is it points to a cause. How can they know the issue is social media, and not, say, the climbing atmospheric CO2 or other long-COVID related issues?
I work in an organization which is part of a huge multinational. We've successfully managed to spearhead Gitlab into our giant company, and it's slowly making inroads.
until this price change
And now we're looking at alternatives. Sorry, the price hike for our case (~500 devs) is hefty, to the point where we're willing to eat crow and go with Gerrit+Jira+Confluence+Jenkins, and basically disentangle ourselves.
So like, I guess it makes financial sense in the short term? But definitely will hurt in the mid-long term. You've lost us at least as a customer. And no--we aren't going to talk to our account leader about this, or discuss any discounts or anything.