<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tip on TutorialEdge.net</title><link>https://tutorialedge.net/series/tip/</link><description>Recent content in Tip on TutorialEdge.net</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 01 Sep 2024 06:00:00 +0000</lastBuildDate><atom:link href="https://tutorialedge.net/series/tip/index.xml" rel="self" type="application/rss+xml"/><item><title>Replacing curl with HTTPie</title><link>https://tutorialedge.net/tips/using-httpie-to-replace-your-curl-commands/</link><pubDate>Sun, 01 Sep 2024 06:00:00 +0000</pubDate><guid>https://tutorialedge.net/tips/using-httpie-to-replace-your-curl-commands/</guid><description>&lt;p&gt;If you are building out http-based services, it&amp;rsquo;s almost inevitable that you&amp;rsquo;ll need to craft HTTP requests in order
to validate some of your endpoints.&lt;/p&gt;
&lt;p&gt;Recently, I&amp;rsquo;ve become a bit of a convert away from traditional &lt;code&gt;curl&lt;/code&gt; commands and started to adopt the tool &lt;code&gt;HTTPie&lt;/code&gt;,
which is potentially pronounced as HTT-pie?&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s been a fantastic little tool that allows me to craft more natural HTTP requests quickly and easily and also lets
me drop back down to raw &lt;code&gt;curl&lt;/code&gt; should I need it.&lt;/p&gt;</description></item><item><title>Crafting the Perfect Pull Request</title><link>https://tutorialedge.net/tips/crafting-the-perfect-pull-request/</link><pubDate>Mon, 19 Aug 2024 11:35:43 +0000</pubDate><guid>https://tutorialedge.net/tips/crafting-the-perfect-pull-request/</guid><description>&lt;p&gt;It&amp;rsquo;s become de facto in our day-to-day development to work on new features via a branch and open pull requests (or merge requests for GitLab users)
to merge any changes we&amp;rsquo;ve made on our development branches into a production or deployment branch.&lt;/p&gt;
&lt;p&gt;As a crafter of some seriously awful pull requests in my time, I figured it was worth sharing some handy reminders that will help you avoid
the most grievous of mistakes that I&amp;rsquo;ve succumbed to over the years.&lt;/p&gt;</description></item><item><title>Splitting Code Changes into Separate Commits</title><link>https://tutorialedge.net/tips/splitting-changes-commit-by-commit/</link><pubDate>Mon, 19 Aug 2024 11:35:43 +0000</pubDate><guid>https://tutorialedge.net/tips/splitting-changes-commit-by-commit/</guid><description>&lt;p&gt;The systems we build are inherently incredibly complex. The successful ones will encapsulate years of accumulated business
logic and context and hopefully, become legacy systems that future developers will complain about or perhaps suggest rewriting
entirely for no other reason that it&amp;rsquo;s a pain in their arse.&lt;/p&gt;
&lt;p&gt;There then comes a moment of time where someone, somewhere, will start working in a section of code that features a particularly
perplexing bit of logic that makes the unsuspecting developer go &amp;ldquo;huh?&amp;rdquo;.&lt;/p&gt;</description></item><item><title>Aliasing your Git Commands for Maximum Productivity</title><link>https://tutorialedge.net/tips/aliasing-your-git-commands/</link><pubDate>Sat, 17 Aug 2024 11:35:43 +0000</pubDate><guid>https://tutorialedge.net/tips/aliasing-your-git-commands/</guid><description>&lt;p&gt;This is a little tip for those of you wanting to optimize your developer productivity and reduce the
toil around some of the tasks that you&amp;rsquo;ll perform likely hundreds of times per week.&lt;/p&gt;
&lt;p&gt;I tend to spend a lot of time raising pull requests, writing commits or running various git commands
in order to get my current working branch in order prior to getting it merged into production.&lt;/p&gt;
&lt;p&gt;It can feel a little tedious running &lt;code&gt;git add -p&lt;/code&gt; or &lt;code&gt;git add -A&lt;/code&gt; followed by &lt;code&gt;git commit -m &amp;quot;blah&amp;quot;&lt;/code&gt;
and finally either a &lt;code&gt;git push origin main&lt;/code&gt; or &lt;code&gt;git rebase -i origin/main&lt;/code&gt; depending on what stage
of the cycle I&amp;rsquo;m in.&lt;/p&gt;</description></item></channel></rss>