Are we including just technical people in these crowds?

Because there's a third crowd: everyone else/the general public that are standing up vibe coded websites and don't give a hoot how things work in the background or know as long as money is coming in. There are people that are using AI and thinking less and less causing their brains over the long term to become more inelastic.

We're in for a very, very painful future that will have mixed results. On one hand, you can boostrap things a lot quicker with less mental effort and it helps get up to speed without having to know some complex things (e.g. deep knowledge in coding). This can help us innovate on basic things faster, probably.

On the other ... people aren't going to learn. If something breaks in that state where they don't know how something works, what, we're just going to ask another AI to fix it? I don't know how I feel or think about that. On a long enough timeline, there are people that won't know how any of this was designed in the first place.

That's the world we actually live in. And that's what will survive despite crowd 1 and 2 that you mentioned above.

▲

yieldcrv 5 hours ago | parent [-]

I’m working with an ideas guy, no skills and no capital but for the first time can deliver code

He wants my tech expertise, his code is spaghetti, he is making all the mistakes, he is experiencing AI psychosis, his AI makes md files warning him that its all going to burn him which he forwards to me lackadaisically without reading

But can he sale? Yes

Its tempting for me to proselytize that he isnt using feature branches or project tickets or even deploying with committed code

But I bite my tongue and tell him to focus on the MVP since he wants to prompt Claude Code for 48 hour sessions without there being any indication of how other devs could contribute

Because he has clients that wants what he described, and because he has no capital I get a huge cut of that

I’m fine with that, I’ll clean up the project very quickly

	▲	wiether 27 minutes ago \| parent [-]
		I've also have to work with a guy like that. It could be okay if it wasn't for the fact that they have a high esteem of themselves and don't learn shit. The first POC they vibecoded and managed to sell was a pile of trash that we couldn't realistically deploy as it. So we spent two weeks to make it something decent enough to have the minimum confidence of the thing being reliable and safe enough to reach staging. Two weeks during they told us daily how we were slowing everything down. After that we spent an hour explaining them how making something works on their computer, without tests, without thinking about edge cases... was not the same thing as deploying it and releasing it to actual users. We agreed on, next time, asking us for an estimate on how much it would take to move the POC to something that could be released, before signing on any engagement with a customer. Well, last week they came with a new deal they just signed on a completely new POC. Customer was expecting it for yesterday. To make it work, we have to setup a VPN between our infra and customer infra. Their internal process make it impossible to have this under a month. Now, my guy and the customer, are mad at me because I can't deliver. And the first POC? Customer wants new features. My guy don't want to deal with it because it's not their job.