Key things to know about Make and best workflow

[rosie2573]

When working with Make, the biggest gains usually come from treating it as a repeatable workflow rather than a one-off prompt or experiment.

One important area is best workflow. Define what a good result looks like before changing tools or settings, then test one variable at a time so you can tell what actually improved the outcome.

Another area is productivity. Keep examples of both strong and weak outputs, check important facts or generated code independently, and document settings that produce consistent results.

The main takeaway is that Make becomes much more reliable when the workflow includes clear inputs, repeatable checks, and a way to learn from previous results.



Photo by

Please, Log in or Register to view URLs content!

on

Please, Log in or Register to view URLs content!

 

[ben4076]

The point about workflow and make is interesting. In practice I would keep the first test simple, record what worked, and only add extra complexity if it solves a specific limitation. That way you can improve the workflow without losing track of what caused the improvement.

 

[poppywanderer65]

The point about workflow and make is interesting. In practice I would keep the first test simple, record what worked, and only add extra complexity if it solves a specific limitation. The original point — "When working with Make, the biggest gains usually come from treating it as a repeatable workflow rather than a one-off prompt or experiment. One important area is best workflow. D…" — gives a useful starting point for that comparison.