It's not new information that people can learn/practice in their sleep. This is already known and well documented. The interesting question is: what conditions increase the chance practicing in ones sleep? What are the mechanisms?
I suspect the commenter above is reflecting on 2026 USA and not 1850 USA. The past tense nature of your comment if part of the concern highlights a common recognition that there is limited evidence the country is currently capable of building.
The geographic and demographic orders of magnitude when comparing these two places makes it difficult to extrapolate applicability of best practices. Who's to say the Swiss model scales? Article doesn't convincingly address this.
For context:
41 US States are geographically larger than Switzerland. It's most comparable state in area is West Virginia. West Virginia is .064% of the national area.
Some fun distance contexts. Driving end to end in Switzerland is comparable in distance to:
Driving from Pittsburgh to Philadelphia, Detroit to Chicago, or New York City to Washington DC.
More likely the cultural practice was not passed down after the massive change in food preservation about 125 years ago. In the United States, fermentation was a universally practiced method for the pickling of vegetables. This practice has been so reduced that the word "pickle" now only refers to cucumber preservation.
And yet an accessible ecosystem of 3rd party non-emacs tooling has not been developed.
I would pay big bucks for an obsidian-styled org-mode clone that had a no-frills GUI interface. I find org-modes task tracking, calendar, and agenda views top tier.
I worked for a few years in an large org which utilized perl for build scripts, testing automation, and a few other things. I would summarize the half decade Perl learning curve as initial bewilderment, intermediate cult like praise, to advance level disillusionment.
There was something about scaling usage in large teams that felt awkward and high friction.
I think the primary issue is that there is massive demand for adolescent social interaction in a world that is increasingly physically isolating for kids.
Demographic shifts make suburban families too sparse to support children friend groups. Denser cities are increasingly financially impossible for families to move in.
This was before my time but I appreciate the write up and the nostalgia from folks in this thread.
My take away was that VisiCalc was a fairly straight forward technological problem, but a 10,000x+ impact idea. I feel like there are still idea's like this waiting in the shadows to be discovered by a lowly undergrad somewhere who tries something unique for the first time.
How did you verify that a software update can 1. Occur during driving operation of the vehicle and 2. results in vehicle power loss?
I worked in an auto supplier years ago and there where several protections in place to prevent the risk of update corruption on safety related components. One of the simplest one the UDS programming session having entry protections related to vehicle speed, vehicle driving mode, etc.
This article left me wishing it was "How I'm using coding agents to do <x> task better"
I've been exploring AI for two years now. It's certainly upgraded itself from the toy classification to a basic utility. However, I increasingly run into its limitations and find reverting to pre-LLM ways of working more robust, faster, and more mentally sustainable.
Does someone have concrete examples of integrating LLM in a workflow that pushes state-of-the-art development practices & value creation further?