2 ms·
"Either something is possible or it is not. If you don't know, that just means you're lacking knowledge (and maybe it's never been done before)." Exactly - and
by simonw 2y ago
"Either something is possible or it is not. If you don't know, that just means you're lacking knowledge (and maybe it's never been done before)."
Exactly - and that's what I use prototyping to figure out.
It's not just "is something possible?" - it's "is this possible given the time, tools and skills available to me?"
Here's a really simple example from a couple of years ago: I wanted to build a tool that exported my Apple Notes to a SQLite database.
Is that possible to build? What are the export options available?
I ended up using an LLM to write AppleScript (a language I had no prior experience with) to extract the notes data, and it worked great. I wrote up that prototyping experiment here: https://til.simonwillison.net/gpt3/chatgpt-applescript https://til.simonwillison.net/gpt3/chatgpt-applescript
- AdieuToLogic 2y ago>> "Either something is possible or it is not. If you don't know, that just means you're lacking knowledge (and maybe it's never been done before)." > Exactly - and that's what I use prototyping to figure out. Perhaps "prototyping" is an inappropriate descriptor here. A better one might be "one-off disposable code" considering the example described. Peer developers could easily interpret prototyping an AppleScript ETL as only requiring minimal research into identifying its applicability and subsequent reusable definition. However, a "one-off disposable AppleScript approach" expresses minimal investment (time) and also conveys a higher risk tolerance to potential incorrect code an LLM might generate. HTH
- simonw 2y ago"one-off disposable code" is pretty much exactly what I consider the term "prototyping" to mean.
- bombela 2y agoOne-off and prototype share similarities in development methodologies. But not in the long term goals. In a one-off I don't care about a few output errors that I can fix by hand once. Good enough is enough. A prototype requires to explore the limitations and estimate the effort required to eventually reach correctness. This estimate juggling time, cost, motivation, knowledge and "human resources" together.