Recent content by evanonhub

For TypeScript, it helps to think in terms of inputs, constraints, verification, and iteration. One important area is performance. 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...

I think research and lessons is the key part of this topic. A practical approach is to define the outcome you want, test it with a small example, and then check quality, speed and reliability separately. That way you can improve the workflow without losing track of what caused the improvement.

I have a question about Buying Advice that may be useful for other people working with it too. I am particularly interested in testing and prompt design. I would like to compare approaches that people have actually used rather than just theoretical suggestions. What would you tell someone...