The issue here isn't beautiful code vs quick code. I think it's between spending some time and thinking about the problem you are trying to solve vs brute forc

The issue here isn't beautiful code vs quick code. I think it's between spending some time and thinking about the problem you are trying to solve vs brute forcing a quick prototype to get it done. I think your code will look beautiful by itself if the engineer fully understands the problem at hand. This process takes time and practice. I personally throw away my quick first solution and let the fog clear first. Somethings that have generally given me good results: drawing stuff, taking small breaks, listening to my tests (if my tests hurt, it means my design is bad) Would love to hear other thoughts on this !