> The author is essentially arguing that fewer people will be able to build software in the future.
Setting aside the fact that the author nowhere says this, it may in fact be plausible.
> That's the opposite of what's happened over the past year or two. Now many more non-technical people can (and are) building software.
Meanwhile half[0] the students supposed to be learning to build software in university will fail to learn something important because they asked Claude instead of thinking about it. (Or all the students using llms will fail to learn something half the time, etc.)
The author tell his experience regarding his joy programming things and figuring stuff out. In the end he says that AI made him lose this joy, and he compares it to cheating in a game. He does not say one word about societal impact and or the amount of engineers in the future, it's what you interpreted yourself.
“ In some countries, more than 90% of the population lives on less than $5 per day. If agentic AI code generation becomes the most effective way to write high-quality code, this will create a massive barrier to entry”
> The author is essentially arguing that fewer people will be able to build software in the future.
You comment is talking about ability to build software, vs. the article (in only a single sentence that references this topic, while the other 99% circles around something else) talks about the job market situation. If what you wanted so say "The author is arguing that people will probably have a harder time getting a job in software development", that would have been correct.
> That's the opposite of what's happened over the past year or two. Now many more non-technical people can (and are) building software.
You're (based on the new comment) explicitly saying that people without technical knowledge are getting jobs in software development sector. Where did you get that info from? Would be an interesting read for sure, if it's actually true.
Yes, they could be, but then you 100% rely on the client tools doing a good job doing that, which they aren't always good at, and they also have to reinvent the wheel on what are becoming essentially commodity features.
E.g. one of the biggest annoyances for me with cursor was external documentation indexing, where you hand it the website of a specific libarary and then it crawls and indexes that. That feature has been completely broken for me (always aborting with a crawl error). Now with a MCP server, I can just use one that is specialized in this kind of documentation indexing, where I also have the ability to tinker with it if it breaks, and then can use that in all my agentic coding tools that need it (which also allows me to transfer more work to background/non-IDE workflows).
The Guardian used to be considered a serious paper, then a few years ago the quality declined dramatically. Now it's not much better than most tabloids.
Political polarization increases as traditional "newspapers" shift to the Web and get ever more specialized, and don't have to appeal to a broad political audience anymore.
The upshot of this is that anyone will be able to order a couple of robot arms from China and then set them up in a garage, programming them with just text, like we do with LLMs now.
The cost of robotics is coming down, check out Unitree. A couple of robot arms would cost about the same as a minimum wageworker for 1 year right now. But of course they can go virtually 24/7 so likely 1/3rd the cost
It's quite telling that these discussions often end up at conclusion that we are becoming a developing (or 3rd world) country again, and not Star Trek society.
Those tracks could be at the ceiling. Imagine a robot arm in a kitchen that is dangling from the ceiling. It could be helping when needed and disappear in a cupboard after that.
Larger context windows are helping solve this, though.
I use ALpineJS which is not as well known as React etc, but I just added a bunch of examples and instructions to the new cursor project rules, and it's now close to perfect.
Gemini models have up to 2M context windows, meaning you can probably fit your whole codebase and a ton of examples in a single request.
Furthermore, the agenetic way Cursor is now behaving, automatically building up context before taking action, seems to be another way around this problem
Above & Beyond's label has a huge following. I have been to many events around the world. They do a big gathering each year e.g. https://www.youtube.com/watch?v=JEqySVgNkIA
That JSON you get might be syntactically valid, but how do you know that it is accurate wrt your original input? That, for example, no values have a one-character-off misspelling?
Totally agree. React and Vue are overkill and bloated, and actually lead to a worse experience a lot of the time e.g. users starting at spinning loaders with broken browser functionality (like back buton)
A hybrid approach of server-side views with a simple lib like AlpineJS or HTMX for dynamic bits is far better in most cases. The initial page load is blazing fast because the server does the work. Then, for things like filtering or updating lists, you use the lightweight library for smooth, efficient updates. You get the best of both worlds—a super-fast initial experience and the ability to add dynamic features without the React baggage (and often-neglected backend).
I've been using Inertia.js with laravel and Vue and its been great, no need to write an API layer. You get the simplicity of writing server rendered with the interactivity of an SPA
I've generally agreed with this but found the UI (ie. HTML) story on the backend is utter shite. Namely it's usually been handled by templates which inevitably lead to ridiculously inconsistent UIs with so much redundancy. In contrast something like JSX is really good and makes building small components for reuse natural.
Fortunately there has been some change in this area. FastHTML is a batteries-included library for Python and there are numerous standalone HTML generation libraries that can be used with other frameworks like Django, e.g. htpy, htmy etc.
I've been using alpine on a static site and it's really quite impressive just how much of "the stuff you probably want js for" it covers. So much so that you can pretty much say "if you can't do it in alpine, maybe we shouldn't do it at all".
I am using Laravel Blade components which are effectively just fully server rendered templates in component style, so you get the benefit of that mental model.
> For useful background on the first version of Durable Objects take a look at Cloudflare's durable multiplayer moat by Paul Butler, who digs into its popularity for building WebSocket-based realtime collaborative applications.
First apps that come to mind that have RT collaboration:
- Google Docs/Sheets etc
- Notion
- Miro
- Figma
These are all global scale collaborative apps, I'm not sure a Laravel stack will support those use cases... Google had to in house everything and probably spearheaded the usage of CRDTs ( this is a guess!) but as the patterns emerge and the building blocks get SAASified, mass-RT collaboration no longer becomes a giant engineering problem and more and more interesting products get unlocked
That's the opposite of what's happened over the past year or two. Now many more non-technical people can (and are) building software.
reply