3 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
by 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.