4 ms·
One of the things I find really helpful and grounding, both to me and the LLM, is working in a tree-like (or fractal) pattern. First I create the trunk (a broa
by jawns 2y ago
One of the things I find really helpful and grounding, both to me and the LLM, is working in a tree-like (or fractal) pattern.
First I create the trunk (a broad outline of what I wish to accomplish). Then I concentrate on filling out the branches (the individual bullet points of that broad outline). Then I drill down into the twigs and then the leaves.
It's a different workflow than what I used to follow before LLMs arrived, where I tended to build bottom-up, rather than top-down. But it seems to keep both me and the LLM on track.
Even though it's structured, is it still vibe coding? Well, I think of vibe coding mostly in terms of the psychology. If whatever I'm doing induces a feeling of flow, then that's the vibe I'm going for. https://en.wikipedia.org/wiki/Flow_(psychology) https://en.wikipedia.org/wiki/Flow_(psychology)
- AdieuToLogic 2y ago> One of the things I find really helpful and grounding, both to me and the LLM, is working in a tree-like (or fractal) pattern. > First I create the trunk (a broad outline of what I wish to accomplish). Then I concentrate on filling out the branches (the individual bullet points of that broad outline). Then I drill down into the twigs and then the leaves. This is also known as "top-down", Structured Programming[0], and/or Imperative Programming[1]. The only difference here is the language used. 0 - https://en.wikipedia.org/wiki/Structured_programming https://en.wikipedia.org/wiki/Structured_programming 1 - https://en.wikipedia.org/wiki/Imperative_programming https://en.wikipedia.org/wiki/Imperative_programming
- skydhash 2y agoYou read through the evolution of the arguments for using LLMs for coding on HN and it seems like the rediscovery of all the programming principles again. Maybe in a few months, we will have flowchart, some smalltalk like environment, and UML again.