exactly, the benchmark just needs to be downvoted into oblivion each times it's posted. The outcome is not deterministic and the model needs to determine what level of detail is appropriate for an svg. There is no wrong answer to this unless it's obviously un-Pelican-like.
I think you're seeing a big shift around it.... since it's been markedly cheaper and also still easily available from OpenCode, it's getting large enterprise traction.
Hacker News is so annoying about this. It really feels like sour grapes that people are shipping cool projects without one of the Y Combinator-type software engineers blessing the project with their handwritten code.
Sooooo much of what is considered "code quality" today is irrelevant when robots are writing the code. We've been largely optimizing for things like composability/unit testability in the past 15 or so years, and that's primarily a human concern that's unrelated to the final output.
Totally agreed that we're not looking at the correct metric right now. Increasingly, code quality will be determined by outcomes.
I don’t agree with this. The things people care about with code quality if you really think about it actually match up surprisingly well with the metric which models are trained to emulate in pre training, namely compression and modularity. Those two ideas actually seem to be universal to intelligent systems. Writing verbose highly coupled code is I think provably stupid, though I don’t know that I could formalize it.
On the other hand, there are claims that the best languages for robots tend to be terse (allegedly); I tend to regard a rich domain model (static types, not terse) as a major facet of high-quality code.
> There's some psychological mechanism by which my brain immediately recognizes AI generated text and just short-circuits to "there is no information here".
I think you need to self-correct here, because otherwise you'll be ineffective in an information setting, where I expect AI-generated resources will not only be the norm, they will absolutely swamp the environment.
AI-generated resources swamping the information environment only makes it more important to have the mental mechanisms for quickly filtering out their non-information.
Perhaps we'll all become metaphorical pandas, spending 14 hours a day ingesting nutrient-poor bamboo. (And producing a proportionate amount of excrement ourselves.)
Sounds dubious. Every software architect that I encountered who did not code at the same time was a bit of an embarrassment. But everyone pretended that they know what they are doing either because they (usually management) could not evaluate usefulness or expertise of these so called "architects" or because we simply needed to keep our jobs to pay the bills.
I have bad stories about classic corporate architects too, but that's far from all there is. The job of a typical Staff / Principal in a modern organization is most often to lead, shepherd and conduct technical decisions and people to execute a project, very different from managing them as personnel. Having some hand in execution helps a lot, but the value of their contribution is typically not in the hands-on execution part.
reply