HN user

d_sem

510 karma
Posts0
Comments107
View on HN
No posts found.

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.

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?

I think the author did a sufficient job caveating his post without being verbose.

While reading through past posts I stumbled on a multi part "Writing an LLM from scratch" series that was an enjoyable read. I hope they keep up writing more fun content.

My experience working in an automotive supplier suggest that Tesla engineers must have always knowns this and the real strategy was to provide the best ADAS experience with the cheapest sensor architecture. They certainly did achieved that goal.

There were aspirations that the bottom up approach would work with enough data, but as I learned about the kind of long tail cases that we solved with radar/camera fusion, camera-only seemed categorically less safe.

easy edge case: A self driving system cannot be inoperable due to sunlight or fog.

a more hackernew worthy consideration: calculate the angular pixel resolution required to accurately range and classify an object 100 meters away. (roughly the distance needed to safely stop if you're traveling 80mph) Now add a second camera for stereo and calculate the camera-to-camera extrinsic sensitivity you'd need to stay within to keep error sufficiently low in all temperature/road condition scenarios.

The answer is: screw that, I should just add a long range radar.

there are just so many considerations that show you need a multi-modality solution, and using human biology as a what-about-ism, doesn't translate to currently available technology.

Shoutout to the Henry Ford Museum located in Dearborn, Michigan which is a treasure trove of 19th and early 20th century technology. A true celebration of, what I would consider, the most physically transformative era in human history thus far.

It has never been easier to realize your own open source hardware platform. Those dedicated to freedom can chose to offer alternatives. The challenge is we don't live in a post job society and people need to make money to survive. Until that changes, practical professionals will gravitate towards non-ideal systems that optimize for short term value over freedom.