> The days of techies gatekeeping these experiences are over.
Why do people keep using the word "gatekeeping"? "Techies" made open source. Anyone could have taken the time to learn what they wanted, the tools and the resources were available.
The disdain for tech will always baffle me. Yes, this stuff is hard. A lot of it requires a certain level of skill. Even now, you still require some level of skill to get good results.
No non-corporate tech person has ever wanted to prevent another soul from using their work or learning their craft.
The top-level comment feels a lot like the perspective of somebody who never cared to try.
With robots for agriculture, delivery, and food processing, the days of farmers gatekeeping food will be over
Also, the "techies" are naturally going to be a lot better at pushing AI to its limits. This doesn't change the playing field - it means more people can do more things, but the upper end of the skill range is going to be just as far ahead, if not further ahead, of everyone else as it always was.
> Anyone could have taken the time to learn what they wanted, the tools and the resources were available.
False in reality. Just ask any dev who has had to listen to family and friends' app ideas over the last decade. The good news for them is soon they will never be asked again.
Having a concept is completely different, their unwillingness to dive into implementation cannot be blamed on the "techies". I would wager that the same people who were pitching unrealistic app ideas then are still not trying to make apps using AI.
What AI has largely changed is how the communication barrier (or perception thereof) is dealt with between two sides: one which consists of those who perceive gatekeeping or attribute their lack of substantive progress to it, and the other side which consists of the time, resources, and skills the former feels entitled to or indebted towards.
I’ve had a running theory for a few years now that some tech folks are more open to receiving an error message from a compiler or other tool, than they are to critical feedback from a peer. If they’re blocked and finally have exhausted their other avenues (pre-LLM: web searches, forums, etc), they’ll reluctantly engage with a peer, and do so with extremely limited patience.
The first paragraph of this reply is extending that theory to non-tech —-> tech, but replace compilers with LLMs that _appear_ to be more useful (or at least busy) working with what limited context you provide them, especially when it’s insufficient.
It won’t quite tell you your app idea is unrealistic or that the implementation is nearly impossible, but after burning a bunch of time and tokens, those people will eventually get the point.
Or reluctantly reach out to a tech person anyway.