Hidde de Vries writes in »How to avoid that your post about AI helps the hype« for hidde.blog The term “artificial intelligence” was coined as a way to make a branch of scientific research more attractive to potential funders. A lot of the tech we see today is neither artificial nor intelligent. It’s powerful and impressive technology, sure, but it’s machines. ...
Darryl K. Taft quotes David Mytton, CEO of Arcjet, in »No Code Is Dead« for thenewstack.io I expect GenAI to make building these apps a lot faster and easier, but it’s still going to make a technical mess. Vibe coding internal apps is going to be a huge source of technical debt in the coming years! In the public sector, Low-Code and No-Code are often hailed as a panacea for the growing need to automate in order to help offset demographic change. But this approach is already outdated. The article shows why No-Code is already obsolete and what challenges lie ahead. ...
Maximilian Henning schreibt in »Quartet of EU countries to cooperate on building sovereign digital infrastructure« für euractiv.com Today both France and Germany, along with the Netherlands and Italy, signed founding papers for a European Digital Infrastructure Consortium for Digital Commons – which they said will focus on publicly developed and publicly usable digital programmes. The signature alone is not enough. The consortium still needs to be established. ...
Matthew Prince writes in »Content Independence Day: no AI crawl without compensation!« for cloudflare.com That changes today, July 1, what we’re calling Content Independence Day. Cloudflare, along with a majority of the world’s leading publishers and AI companies, is changing the default to block AI crawlers unless they pay creators for their content. That content is the fuel that powers AI engines, and so it’s only fair that content creators are compensated directly for it. ...
Pedro Tavares writes in ‘Writing Code Was Never The Bottleneck’ for ordep.dev Tools like Claude can speed up initial implementation. Still, the result is often more code flowing through systems and more pressure on the people responsible for reviewing, integrating, and maintaining it. This becomes especially clear when: It’s unclear whether the author fully understands what they submitted. The generated code introduces unfamiliar patterns or breaks established conventions. Edge cases and unintended side effects aren’t obvious. We end up in a situation where code is easier to produce but harder to verify, which doesn’t necessarily make teams move faster overall. ...