Nick T
@nt
one thing that serves me well when building is that I'm incredibly lazy with the early versions. I'll ignore pretty much everything outside of the highest-risk/uncertainty area in the product and build a throwaway prototype to derisk it. for example: current client wants to build an HR operating system for fast-growing scale-ups that uses a voice agent. my first MVP is literally throwing a bunch of manually collected data into the system prompt and getting the client to test it. it took me half an hour but we now know the limits of the tech for their use case. the next version is going to slightly simplify gathering the data and make it about 50% less manual so we can test it 5 times instead of once. I aim for at least one such test per day of building and make sure I test the most uncertain stuff first, and as a result progress tends to be pretty fast and smooth.
1 reply
0 recast
4 reactions
sardius.eth
@sardius
good advice
0 reply
0 recast
0 reaction
