Respond to comments

Author: ploeh

_posts/2024-05-13-gratification.html

@@ -271,4 +271,23 @@ <h2 id="comments-header">
         </div>
         <div class="comment-date">2024-05-16 13:57 UTC</div>
     </div>
+
+    <div class="comment" id="2a6dd3839e2e4bf9b06071221b330356">
+        <div class="comment-author"><a href="/">Mark Seemann</a> <a href="#2a6dd3839e2e4bf9b06071221b330356">#</a></div>
+        <div class="comment-content">
+            <p>
+                Thank you, both, for writing. In the end, it's up to every team to settle on technical solutions that work for them, in that context. Likewise, it's up to each developer to identify methodology and tools that work for her or him, as long as it doesn't impact the rest of the team.
+            </p>
+            <p>
+                The reason I suggest curl over other alternatives is that not only is it free, it also tends to be ubiquitous. Most systems come with curl baked in - perhaps not a consumer installation of Windows, but if you have developer tools installed, it's highly likely that you have curl on your machine. It's <a href="/2024/05/20/fundamentals">a fundamental skill that may serve you well if you know it</a>.
+            </p>
+            <p>
+                In addition to that, since curl is a CLI you can always script it if you need a kind of semi-automation. What prevents you from maintaining a collection of script files? They could even take command-line arguments, if you'd like.
+            </p>
+            <p>
+                That said, personally, if I realize that I need to maintain a collection of requests that I can re-execute whenever I want, I'd prefer writing a 'real' program. On the other hand, I find a tool like curl useful for ad-hoc testing.
+            </p>
+        </div>
+        <div class="comment-date">2024-05-21 5:36 UTC</div>
+    </div>
 </div>