_______ __ _______
| | |.---.-..----.| |--..-----..----. | | |.-----..--.--.--..-----.
| || _ || __|| < | -__|| _| | || -__|| | | ||__ --|
|___|___||___._||____||__|__||_____||__| |__|____||_____||________||_____|
on Gopher (inofficial)
HTML Visit Hacker News on the Web
COMMENT PAGE FOR:
HTML Build Software. Build Users
wiseowise wrote 36 min ago:
Another fart in the wind. How to write lots of âprogramming
philosophyâ and say nothing.
fainpul wrote 1 hour 5 min ago:
This is ridiculous. I doubt this would work with a general AI, but it
surely cannot work with LLMs who understand exactly nothing about human
behaviour.
josters wrote 35 min ago:
They may not understand it but they may very well be able to
reproduce aspects of feedback and comments on similar pieces of
software.
I agree that the approach shouldnât be done unsupervised but I can
imagine it being useful to gain valuable insights for improving the
product before real users even interact with it.
crabmusket wrote 2 hours 56 min ago:
This is interesting, and I think worth trying. However,
The process is iterative:
Vibe code users <--> Vibe code software
Step by step, you get closer to truly understanding your users
Do not fool yourself. This is not "truly" "understanding" your "users".
This is a model which may be very useful, but should not be mistaken
for your users themselves.
Nothing beats feedback from humans, and there's no way around the
painstaking effort of customer development to understand how to satisfy
their needs using software.
bahmboo wrote 29 min ago:
I agree. I do like the general idea as an exploration.
Perhaps the idea is to use an LLM to emulate users such that some
user-based problems can be detected early.
It is very frustrating to ship a product and have a product show
stopper right out of the gate that was missed by everyone on the
team. It is also sometimes difficult to get accurate feedback from an
early user group.
DIR <- back to front page