this post was submitted on 17 Mar 2025
1353 points (99.7% liked)

Programmer Humor

34442 readers
187 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 14 hours ago (2 children)

Devils advocate, not my actual opinion; if you can make a Thing that people will pay to use, easily and without domain specific knowledge, why would you not? It may hit issues at some point but by them you’ve already got ARR and might be able to sell it.

[–] [email protected] 16 points 13 hours ago

If you started from first principles and made a car or, in this case, told an flailing intelligence precursor to make a car, how long would it take for it to create ABS? Seatbelts? Airbags? Reinforced fuel tanks? Firewalls? Collision avoidance? OBD ports? Handsfree kits? Side impact bars? Cupholders? Those are things created as a result of problems that Karl Benz couldn't have conceived of, let alone solve.

Experts don't just have skills, they have experience. The more esoteric the challenge, the more important that experience is. Without that experience you'll very quickly find your product fails due to long-solved problems leaving you - and your customers - in the position of being exposed dangers that a reasonable person would conclude shouldn't exist.

[–] [email protected] 2 points 13 hours ago* (last edited 7 hours ago)

Yeh, arguably and to a limited extent, the problems he's having now aren't the result of the decision to use AI to make his product so much as the decision to tell people about that and people deliberately attempting to sabotage it. I'm careful to qualify that though because the self evident flaw in his plan even if it only surfaced in a rather extreme scenario, is that he lacks the domain specific knowledge to actually make his product work as soon as anything becomes more complicated than just collecting the money. Evidently there was more to this venture than just the building of the software, that was necessary to for it to be a viable service. Much like if you consider yourself the ideas man and paid a programmer to engineer the product for you and then fired them straight after without hiring anyone to maintain it or keep the infrastructure going or provide support for your clients and then claimed you 'built' the product, you'd be in a similar scenario not long after your first paying customer finds out the hard way that you don't actually know anything about your own service that you willingly took money for. He's discovering he can't actually provide the service part of the Software as a Service he's selling.