<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Pratham Malhotra</title>
    <description>The latest articles on DEV Community by Pratham Malhotra (@prathammalhotra).</description>
    <link>https://dev.to/prathammalhotra</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4251140%2Fe0bfc5f1-5a96-44b2-bf09-d2c3ef5bf3b4.png</url>
      <title>DEV Community: Pratham Malhotra</title>
      <link>https://dev.to/prathammalhotra</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/prathammalhotra"/>
    <language>en</language>
    <item>
      <title>Turn Your Git Log Into a Week of LinkedIn Posts</title>
      <dc:creator>Pratham Malhotra</dc:creator>
      <pubDate>Wed, 18 Nov 2026 11:28:43 +0000</pubDate>
      <link>https://dev.to/prathammalhotra/turn-your-git-log-into-a-week-of-linkedin-posts-6j3</link>
      <guid>https://dev.to/prathammalhotra/turn-your-git-log-into-a-week-of-linkedin-posts-6j3</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fimages.unsplash.com%2Fphoto-1555066931-4365d14bab8c%3Fauto%3Dformat%26fit%3Dcrop%26crop%3Dentropy%26fm%3Djpg%26q%3D86%26w%3D1200%26h%3D504" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fimages.unsplash.com%2Fphoto-1555066931-4365d14bab8c%3Fauto%3Dformat%26fit%3Dcrop%26crop%3Dentropy%26fm%3Djpg%26q%3D86%26w%3D1200%26h%3D504" alt="Laptop displaying code" width="1200" height="504"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You fixed a flaky webhook on Tuesday. By Friday, the changelog reads “improved reliability.” The line that would make another developer stop scrolling is buried in the change: a retry can create the same invoice twice.&lt;/p&gt;

&lt;p&gt;If you build software and freeze every time you open a blank composer, start where the work already happened. Here’s a small Git workflow for finding a week’s worth of ideas, turning three into drafts, and deciding whether a tool like Taplio belongs in the final step.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Affiliate disclosure: I may earn a commission if you buy Taplio through the link below. AI generated the initial draft and helped revise it.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Look for decisions in the last two weeks of Git history
&lt;/h2&gt;

&lt;p&gt;Run this from a repository you’re authorized to review. The command reads local history and prints a short list. It won’t change the repo or send anything over the network.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git log --since=&lt;span class="s1"&gt;'14 days ago'&lt;/span&gt; --max-count=40 --no-merges \
  --date=short --format=&lt;span class="s1"&gt;'%ad  %h  %s'&lt;/span&gt; HEAD
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Here’s an &lt;strong&gt;illustrative&lt;/strong&gt; result from a fictional SaaS project:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;2026-11-13  a6f275e  Add safe retries to invoice webhook
2026-11-12  f92c2d0  Replace blank onboarding page with sample data
2026-11-10  e73dcb1  Revert inline PDF rendering
2026-11-08  16a8e4f  Upgrade test dependencies
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A Git subject is a pointer. To see what actually changed, inspect a promising entry with &lt;code&gt;git show &amp;lt;commit&amp;gt;&lt;/code&gt;. Include the angle the diff leaves out: the trade-off, the rejected approach, or a change in what you’d do next time. If your team records the real decisions in pull requests or incident notes, use those as your starting point instead.&lt;/p&gt;

&lt;p&gt;Take care with private repos. Treat the output as internal material, even when you’re the author of the commits. Before a story reaches a shared draft or an AI tool, remove customer names, incident details, code, identifiers, and any screenshots or numbers you lack permission to share. You can write about the pattern using a small made-up example and label it clearly.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Pick three stories that teach three different things
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What happened&lt;/th&gt;
&lt;th&gt;What the reader learns&lt;/th&gt;
&lt;th&gt;A possible first line&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Added safe retries to a webhook&lt;/td&gt;
&lt;td&gt;Why delayed retries can create duplicate work, and what an idempotency key protects&lt;/td&gt;
&lt;td&gt;“A retry fixed the timeout. It also made it possible to create the same invoice twice.”&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Added sample data to onboarding&lt;/td&gt;
&lt;td&gt;How an example can show what a blank dashboard never will&lt;/td&gt;
&lt;td&gt;“Our dashboard had three setup steps. The hardest one was figuring out what it was supposed to look like when they were done.”&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Reverted inline PDF rendering&lt;/td&gt;
&lt;td&gt;How to decide whether background processing is worth the extra complexity&lt;/td&gt;
&lt;td&gt;“A fast PDF export can still feel slow when it blocks the page you need next.”&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;These are writing prompts based on the fictional entries above. For your own drafts, keep the first line tied to what happened. A revert is worth writing about if you can explain what made the original approach look reasonable and what finally changed the decision.&lt;/p&gt;

&lt;p&gt;Try this filter before you queue anything: &lt;strong&gt;could another builder make a better decision after reading this?&lt;/strong&gt; An update like “shipped our new dashboard” tells readers what you did. Explaining why you populated the empty state with sample data gives them something they can try.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Draft the post around one thing the reader can test
&lt;/h2&gt;

&lt;p&gt;Take the fictional webhook commit. The title tells you that retries were added. The story starts with the scenario that makes retries tricky.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;An invoice webhook can time out after the invoice has already been created. The sender sees a failure and tries again. If your handler treats the retry as a new event, a transient timeout can turn into a duplicate invoice.&lt;/p&gt;

&lt;p&gt;One way to handle it: store the incoming event ID with a uniqueness constraint and make the invoice write part of the same database transaction. Then test the path where the database commit succeeds but the response never reaches the sender.&lt;/p&gt;

&lt;p&gt;A happy-path test answers “can we create the invoice?” A replay test answers “can the invoice be created twice?”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That’s a compact post with a failure mode, a design decision, and a test someone can borrow. The transaction suggestion assumes the event record and invoice write live in the same transactional database. For external side effects, you’ll need a separate way to handle retries safely.&lt;/p&gt;

&lt;p&gt;For each new draft, jot down four sentences: what you expected, what actually happened, what you changed, and how somebody else could test the same thing. If you can’t fill in the last sentence, check whether the story has enough detail to stand on its own.&lt;/p&gt;

&lt;p&gt;Write the other two posts using different evidence. Show a redacted before-and-after for onboarding, or sketch the flow you considered for the PDF export. If all three posts read like the same template, keep the one with the strongest example and hold the others until there’s a real lesson.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Schedule a week, then review it
&lt;/h2&gt;

&lt;p&gt;Use three slots you can stick to. For example, ship the failure-mode story on Monday, the UX decision on Wednesday, and the architecture trade-off on Friday. Set aside time to reply yourself when someone asks a question. A thoughtful follow-up can become your next draft.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.linkedin.com/help/linkedin/answer/a1347212" rel="noopener noreferrer"&gt;LinkedIn already lets you schedule posts&lt;/a&gt; and &lt;a href="https://www.linkedin.com/help/linkedin/answer/a525196/viewing-analytics-for-your-shared-posts" rel="noopener noreferrer"&gt;inspect post analytics&lt;/a&gt;. That’s enough to run this workflow with a notes app and a spreadsheet.&lt;/p&gt;

&lt;p&gt;Taplio is worth considering if you’re already producing drafts and keep losing time moving them between notes, your publishing queue, and analytics. Its Starter plan lists scheduling and core analytics. Check which features are in the plan you’d keep, especially if you’re evaluating features during its seven-day trial, which Taplio says gives you Pro access. If a separate queue would save you time, &lt;a href="https://taplio.com/?via=pratham" rel="noopener noreferrer"&gt;see Taplio’s plans and trial options&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;At the end of the week, give each post one row in a spreadsheet: &lt;strong&gt;topic, minutes spent, impressions, and strongest reader question&lt;/strong&gt;. If the webhook post gets fewer views than the onboarding post but two people ask how you handle concurrent retries, those questions give you a concrete follow-up. A second post could show the test with two workers processing the same event at once.&lt;/p&gt;

&lt;p&gt;The next time &lt;code&gt;git log&lt;/code&gt; shows a vague “fix reliability” commit, open the diff and ask what somebody else could learn from it. There’s a better opening line in there somewhere.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Cover photo by &lt;a href="https://unsplash.com/photos/turned-on-macbook-pro-wit-programming-codes-display-f77Bh3inUpE" rel="noopener noreferrer"&gt;Arnold Francisca on Unsplash&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>buildinpublic</category>
      <category>git</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
