Loving the homage to the Whole Earth Catalog. The pivot from "infinite growth and optimization" to "computing within limits" and permacomputing is becoming less of a fringe philosophy and more of a practical necessity.
As hardware recycling and e-waste become bigger challenges, projects like the Damaged Earth Catalog remind us that modern software bloat is a choice, not an inevitability. We need more focus on resilient, low-power, and maintainable tech stacks.
As a parent, I completely agree. We need to protect children from the dangers of the completely uncontrolled "jungle" of social media.
But above all, we need to give children back the right to experience a true, real childhood, made up of true friends, fresh air, friendships, and real relationships!
> If you are a junior developer, “learn SQL properly” is the most valuable 40 hours you can spend. Not a tutorial. Not an ORM. Actual SQL: joins, subqueries, window functions, query plans. That investment pays you back at every job, in every stack, for decades
This is the power of low-level reasoning.
Today, even for a junior developers, even if they have AI that solves syntax problems, SQL teaches you to reason and approach problems logically. Without any wrapper masking low-level logic.
It's something like the letters of the alphabet that form concepts: why should they change?
> ..idea anticipated centuries ago by the philosopher Baruch Spinoza: that our Soul could be a phenomenon of the same basic nature as any other phenomenon in nature.
Even the current Artificial Intelligence revolution is showing us that:
what was thought to be purely immaterial and intangible, that is, human abstract Reasoning and Thoughts, are actually tangible, physical, and even machine-reproducible.
For most of human history, access to a great education has been a function of where you were born and how much money your family had, and of a parents social class.
The best teachers, the best tutors, the best learning resources, they’ve always been concentrated in a small number of places and available to a small number of people.
In my opinion, the AI has the potential to genuinely disrupt that.
The direction of travel is toward a world where a kid in a rural area with a smartphone has access to a quality of personalized instruction that would have been unimaginable only one generation ago.
> During the 40 years since the disaster, it has become clear that many species are living quite happily within the 37-mile-wide (60km) exclusion zone set up around the ruined power plant. But that's not to say nature hasn't changed here – sometimes for the worse.
So.. the radiations has had virtually no impact on the natural ecosystem's regrowth?
Not only... we've always been told about the disastrous consequences of nuclear radiation, but, according to the BBC article (by Chris Baraniuk), that's not the case.
> All of these features are about breaking the coupling between a human sitting at a terminal or chat window and interacting turn-by-turn with the agent.
This means:
- less and less "man-in-the-loop"
- less and less interaction between LLMs and humans
- more and more automation
- more and more decision-making autonomy for agents
- more and more risk (i.e., LLMs' responsibility)
- less and less human responsibility
Problem:
Tasks that require continuous iteration and shared decision-making with humans have two possible options:
If they put a pricing page, I think there would be someone who would buy it, especially nowadays when with embedded llms there is a huge hunger for RAM (as well as CPU). :))
In my opinion, nothing could be more wrong. GitHub's own ratings are easily manipulated and measure not necessarily the quality of the project itself, but rather its Popularity. The problem is that popularity is rarely directly proportional to the quality of the project itself.
I'm building a product and I'm seeing what important is the distribution and comunication instead of the development it self.
Unfortunately, a project's popularity is often directly proportional to the communication "built" around it and inversely proportional to its actual quality. This isn't always the case, but it often is.
Moreover, adopting effective and objective project evaluation tools is quite expensive for VCs.
> All "access control" logic lived in the JavaScript on the client side, meaning the data was literally one command away from anyone who looked
This is the top!
This is a typical example of someone using Coding Agents without being a developer: AI that isn't used knowingly can be a huge risk if you don't know what you're doing.
AI used for professional purposes (not experiments) should NOT be used haphazardly.
And this also opens up a serious liability issue: the developer has the perception of being exempt from responsibility and this also leads to enormous risks for the business.