We are not ready for that.

The Bullock Brothers are one of the lesser known permaculture projects in the PNW but they are somewhat locally famous.

Looking at their history page a while back, I noted that one of the first big milestones they brag about was the return of otters to their waterfront on Puget Sound.

Peterson isn't, is he?

I might sign up just to stay on top of a market change that I don’t have an employer paying me to learn.

But the two concerns I have are, what happens when someone uses it to make the projects I work on again but with one design change, and it this pulling up the ladder behind us? Will someone still be able to start a project five years from now and do what you’ve done? Or come into existing projects like I have?

> I might sign up just to stay on top of a market change that I don’t have an employer paying me to learn.

This is the thing I hate most about AI. It is a huge shift in power towards big companies that have the capital to throw at it. And towards those few mega corporations that control the tech.

It's a big shift away from hobbyists, tinkerers and people exploring ideas on their own time.

What’s the leading plan to combat that?

I don't know if there is one. There are models people can run on fairly expensive hardware at home, but will those be 'good enough' compared to the heavier duty resources that a big, well-funded corporation can deploy?

Like... while the open source models are improving, does that converge with the fancy models with tons of money behind them?

My understanding of the economics of it - so far - is that "more computing resources leads to better results" and capital wins that game.

Computers took like 3 decades before they weren’t just for the rich either.

In the late 70s, personal computers were still like $4-8k (in today’s money). It wasn’t until the 90s when regular people started getting computers.

So there is one… just time.

Writing code yourself?

I dont want to misrepresent, I am not the original author of any of these projects. I am not JDD of lodash (who is still involved and part of the TC) nor TJ Holowaychuk of express.

I dont know what the future will look like, but IMO open source is the intersection of code and community (aka the squishy bits) and for that reason I dont think AI will make it obselete, not now nor in the future.

Wireguard solves the data in motion problem but not the data at rest problem, doesn’t it?

Things most people don’t know about Illinois is that while the Mason Dixon line officially goes around the bottom of the state, philosophically it cuts through the middle. Peoria is maybe thirty miles north of the rednecks.

Add that he was a boomer and I was disappointed but not surprised when people started complaining about him.

Ha, I’d argue it starts right at Pekin.

That puts several university towns below the line. But little towns outside big towns in the Midwest have their own vibe.

The scary knife robot is way, way more intimidating in person.

I still remember the first time I met a scary knife robot. Working fast food night shift was crazy times.

I think there’s too many expectations around what logging is for and getting everyone on the same page is difficult.

Meanwhile stats have fewer expectations, and moving signal out of the logs into stats is a much much smaller battle to win. It can’t tell you everything, but what it can tell you is easier to make unambiguous.

Over time I got people to stop pulling up Splunk as an automatic reflex and start pulling up Grafana instead for triage.

We arrived to that too, Grafana does a lot of heavy lifting in localizing most of the issues.

So you’re not getting alerts at 2 am from hallucinations?

Not from AI no.

I think the context that some other responders are missing is that in some functional languages, like Elixir, streams and iterators are used idiomatically to do staged transforms of data without necessitating accumulation at each step.

They are those languages versions of goroutines, and JavaScript doesn’t have one. Generators sort of, but people don’t use them much, and they don’t compose them with each other.

So if we are going to fix Streams, an implementation that is tuned only for IO-bound workflows at the expense of transform workflows would be a lost opportunity.