I'm thinking that this can be a good pattern for photography portfolio sites. Voice over from photographer talking about his inspiration, walking through key memories, while letting the user browser around.

The point I'm trying make is that there is more nuance than a simple HN user stereotype.

At least in late 90s, there used to be a law to black out half the headlamp. Either that was no longer the case or it's not as vigorously enforced.

This is the classic case of tragedy of commons!

Because of the well bound nature of the problem space, we are able to unlock a lot of power from LLMs and put together a good end-to-end product that delivers the promise.

Still early days. I know there are lot of folks who care about a11y. I would love to chat and learn from your experience.

[1] https://workback.ai/

Also usefulness is very subjective too depending on the context and scope.

zmodload zsh/mapfile

But in reality, these are very subtle. Understanding that what you are experiencing is a failure or what you are building is feature bloat is extremely hard. These aren't obvious moments. I call these micro signals. The skill is in fact developing the thinking muscle to pick on these micro signals and act on them.

Probably most of the "self help" fall in this category - very obvious when reading, but will fail to identify in reality. Internalizing is about understanding how these would manifest in reality (and be aware that these will be very very tiny signals)

At this point, my network is bunch of 'aunts' and 'uncles'. I take secret pleasure by posting stuff that irks them :)

It's scary to look at the scale of 'organized' crime / modern slavery. This is almost like Squid Games.

I've slightly alternate perspective. Imo, using OSS without contributing is the value extraction without giving back.

If someone can fix a bunch of chores (that still take human time), with the use of AI (even though they don't become stewards), I still see it as giving back. Of course, there is a value chain - contributing with AI without understanding code is the bottom of value creation. Like you mentioned, also being a steward is the top of the value chain. Along the way, if the contributor builds some sorta reputation that would help with their career or other outcomes, so be it.

So in that sense, I don't see it as enshittification. AI might make a pathway to resolve a bunch of things which otherwise wouldn't be resolved. In fact, this was the line of thinking for the tool we built. Instead of people making these mindless PRs, can we build an agent that can take care of 'trivial' tasks. I manually created PRs to test that hypothesis.

There is also a natural self selection here. If someone was able to fix something without understanding any code, that is also indicative of how trivial the task is. There is a reverse effect to my argument though. These "AI contributors" can create a ton of PRs that would create a lot of work for maintainers to review them.

In my case, I was being upfront about how I'm raising PRs and requesting permissions if it is OK to work on certain issue. Maintainers are quite open and inviting.

One thing that did work in my favor is that, I was clearly creating a failing repro test case, and adding before and after along with PR. That helped getting the PR landed.

There are also a few PRs that never got accepted because the repro is not as strong or clear.

[1] https://workback.ai