<?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: Rachit Sharma</title>
    <description>The latest articles on DEV Community by Rachit Sharma (@rachitsharma08).</description>
    <link>https://dev.to/rachitsharma08</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%2F4183865%2F58652e31-258b-44f2-8071-209e3acee5cf.jpg</url>
      <title>DEV Community: Rachit Sharma</title>
      <link>https://dev.to/rachitsharma08</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rachitsharma08"/>
    <language>en</language>
    <item>
      <title>On-Page SEO Checklist: 8 Things to Fix on Every Page</title>
      <dc:creator>Rachit Sharma</dc:creator>
      <pubDate>Mon, 02 Nov 2026 21:05:03 +0000</pubDate>
      <link>https://dev.to/rachitsharma08/on-page-seo-checklist-8-things-to-fix-on-every-page-4j1m</link>
      <guid>https://dev.to/rachitsharma08/on-page-seo-checklist-8-things-to-fix-on-every-page-4j1m</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%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F8387p5osdjndfympoz99.png" 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%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F8387p5osdjndfympoz99.png" alt=" " width="800" height="1000"&gt;&lt;/a&gt;&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhk2hl15cs7y12sjz2o30.png" 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%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhk2hl15cs7y12sjz2o30.png" alt=" " width="800" height="1000"&gt;&lt;/a&gt;&lt;br&gt;
On-page SEO is everything you control on the page itself. Here's the whole list, one or two lines each. Tomorrow I'll go through every one properly.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Title tag
&lt;/h2&gt;

&lt;p&gt;The headline people click in Google. Put your main keyword and the city near the front, and keep it short so it doesn't get cut off.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Meta description
&lt;/h2&gt;

&lt;p&gt;The short text under the title in search results. It doesn't help you rank directly, but a good one gets you more clicks.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. URL
&lt;/h2&gt;

&lt;p&gt;Short and readable. &lt;code&gt;/dentist-kaithal&lt;/code&gt; beats &lt;code&gt;/page?id=4821&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Headings
&lt;/h2&gt;

&lt;p&gt;One H1 that says what the page is. Use H2s and H3s to break the rest into sections.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Content
&lt;/h2&gt;

&lt;p&gt;Answer exactly what the person searched for, in plain words. If the answer is buried, rewrite it.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Keywords
&lt;/h2&gt;

&lt;p&gt;Use your main keyword naturally in the title, the H1 and the first paragraph. Related words will show up on their own. Don't repeat it just to repeat it.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Images and alt text
&lt;/h2&gt;

&lt;p&gt;Compress your images so the page loads fast, and write alt text that describes the picture in plain words.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Internal links
&lt;/h2&gt;

&lt;p&gt;Link related pages to each other, and make the link text say where it goes. "Our dental implant service" beats "click here".&lt;/p&gt;

&lt;h2&gt;
  
  
  Next
&lt;/h2&gt;

&lt;p&gt;Tomorrow: each of these in detail, with examples. After that, off-page SEO.&lt;/p&gt;

&lt;p&gt;Which of these eight does your own site get wrong?&lt;/p&gt;

</description>
      <category>seo</category>
      <category>seoaudit</category>
      <category>digitalmarketing</category>
      <category>learning</category>
    </item>
    <item>
      <title>SEO Basics in 5 Minutes: What It Is and How Google Decides What to Show</title>
      <dc:creator>Rachit Sharma</dc:creator>
      <pubDate>Sun, 01 Nov 2026 12:51:33 +0000</pubDate>
      <link>https://dev.to/rachitsharma08/seo-basics-in-5-minutes-what-it-is-and-how-google-decides-what-to-show-49a0</link>
      <guid>https://dev.to/rachitsharma08/seo-basics-in-5-minutes-what-it-is-and-how-google-decides-what-to-show-49a0</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%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftoc5zwmfin2bda58gf53.png" 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%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftoc5zwmfin2bda58gf53.png" alt=" " width="800" height="1000"&gt;&lt;/a&gt;&lt;br&gt;
If you build websites or run a business, someone has probably told you to "do your SEO". Here's the plain version.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is SEO?
&lt;/h2&gt;

&lt;p&gt;SEO means making your website easy for Google to find, understand and trust, so it shows up when people search.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Google works
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Crawl:&lt;/strong&gt; Google visits your pages by following links.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Index:&lt;/strong&gt; Google saves what it found in its library.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rank:&lt;/strong&gt; when someone searches, Google shows the pages it thinks answer best.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If a page isn't crawled and indexed, it can't rank. Check that first.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 3 parts of SEO
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;On-page&lt;/strong&gt; is what's on your site: keywords, page content, titles and headings. Write for the question the person actually typed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Off-page&lt;/strong&gt; is what others say about you: backlinks, reviews and mentions.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Technical&lt;/strong&gt; is whether Google can read your site: page speed, mobile friendliness, a sitemap and HTTPS.&lt;/p&gt;

&lt;p&gt;Work on all three. A great page on a broken site won't get far, and a fast site with thin content won't either.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's next
&lt;/h2&gt;

&lt;p&gt;This is Day 1 of a short SEO basics series. Day 2 is how to audit a business website.&lt;/p&gt;

&lt;p&gt;I'm a digital marketer from Kaithal, Haryana. What would you like me to cover?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>seo</category>
      <category>beginners</category>
      <category>marketing</category>
    </item>
    <item>
      <title>I Collected 208 Skills for Coding Agents. Here's How I Stop Them Fighting Each Other</title>
      <dc:creator>Rachit Sharma</dc:creator>
      <pubDate>Wed, 28 Oct 2026 14:32:14 +0000</pubDate>
      <link>https://dev.to/rachitsharma08/i-collected-208-skills-for-coding-agents-heres-how-i-stop-them-fighting-each-other-2105</link>
      <guid>https://dev.to/rachitsharma08/i-collected-208-skills-for-coding-agents-heres-how-i-stop-them-fighting-each-other-2105</guid>
      <description>&lt;p&gt;I'm a digital marketer, not a developer. But I work with coding agents every day, and the biggest upgrade wasn't a better model. It was skills.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is a skill?
&lt;/h2&gt;

&lt;p&gt;A skill is a folder with one file, &lt;code&gt;SKILL.md&lt;/code&gt;. The top of the file has a short description that the agent matches against your request. The rest holds the instructions, loaded only when there is a match. No plugin, no framework, no code to run.&lt;/p&gt;

&lt;p&gt;Say "cut this clip to 30 seconds and burn in captions" and an ffmpeg skill loads itself. Say "why is this page not converting" and a conversion skill loads instead.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's in the collection
&lt;/h2&gt;

&lt;p&gt;208 skills across these areas:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Video and audio (ffmpeg, Remotion, transcription)&lt;/li&gt;
&lt;li&gt;Design and frontend&lt;/li&gt;
&lt;li&gt;Marketing and SEO (SEO audit, copywriting, ads, CRO)&lt;/li&gt;
&lt;li&gt;Docs and files (docx, pdf, pptx, xlsx)&lt;/li&gt;
&lt;li&gt;Backend and infra (Stripe, Supabase, auth)&lt;/li&gt;
&lt;li&gt;Agent workflow (planning, debugging, test-driven development)&lt;/li&gt;
&lt;li&gt;Security and reverse engineering&lt;/li&gt;
&lt;li&gt;Automation&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I collected, edited and wired them together. Many are adapted from public work, including Anthropic's official skills, &lt;code&gt;obra/superpowers&lt;/code&gt;, Corey Haines' marketing skills and OWASP cheat sheets. Every source is credited in the repo.&lt;/p&gt;

&lt;h2&gt;
  
  
  The real problem: skills fight each other
&lt;/h2&gt;

&lt;p&gt;With 200+ skills installed, the problem is not "no skill". It is three skills firing at once. My rules:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Load a skill only when the request clearly matches its description, not on one shared keyword.&lt;/li&gt;
&lt;li&gt;Max 3 skills per task. If two match, take the more specific one.&lt;/li&gt;
&lt;li&gt;No match? Work without a skill. A forced skill is worse than none.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I also rewrote descriptions so they work as triggers, not marketing copy, and added some triggers in Hinglish, because that is how I talk to my agent.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to use it
&lt;/h2&gt;

&lt;p&gt;You never need all 208. Copy the five you will actually use, and the agent's context stays small.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;git clone https://github.com/Rachit-Sharma08/coding-agent-skills.git
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then copy a skill folder into &lt;code&gt;~/.claude/skills/&lt;/code&gt; for Claude Code, or &lt;code&gt;~/.agents/skills/&lt;/code&gt; for OpenCode. The full steps are in &lt;code&gt;SETUP.md&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Repo: &lt;a href="https://github.com/Rachit-Sharma08/coding-agent-skills" rel="noopener noreferrer"&gt;https://github.com/Rachit-Sharma08/coding-agent-skills&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If it saves you an afternoon, a star helps other people trust the collection. And tell me in the comments: which skill is missing?&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F9uw6cq0z5mebsxbtveaj.jpg" 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%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F9uw6cq0z5mebsxbtveaj.jpg" alt=" " width="800" height="682"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>claudecode</category>
      <category>opensource</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Why AI Image Prompts Need a Style Reference</title>
      <dc:creator>Rachit Sharma</dc:creator>
      <pubDate>Fri, 23 Oct 2026 03:59:11 +0000</pubDate>
      <link>https://dev.to/rachitsharma08/why-ai-image-prompts-need-a-style-reference-289i</link>
      <guid>https://dev.to/rachitsharma08/why-ai-image-prompts-need-a-style-reference-289i</guid>
      <description>&lt;h2&gt;
  
  
  Why most teams overcomplicate lead scoring
&lt;/h2&gt;

&lt;p&gt;Lead scoring fails when it tries to predict revenue before understanding behavior. I would start with a model that flags readiness, not lifetime value, because readiness is observable and revenue is speculative. The goal is to give sales a shorter list of people who have actually shown up, not a ranked list of everyone who might buy.&lt;/p&gt;

&lt;p&gt;A simple model also gets used. Sales teams ignore a score they cannot explain, and a score nobody reads is just a number in a database. If a rep asks why a lead is on the list, you should be able to answer in one sentence.&lt;/p&gt;

&lt;h2&gt;
  
  
  The three signal types worth tracking
&lt;/h2&gt;

&lt;p&gt;Fit signals tell you if the person matches your ideal customer profile: company size, role, industry and technology stack. Intent signals show active research: pricing page visits, demo requests, competitor comparisons and content downloads. Engagement signals measure responsiveness: email opens, click-throughs, reply rates and meeting attendance.&lt;/p&gt;

&lt;p&gt;I would weight intent highest, fit second, and engagement third, because intent correlates most directly with near-term action. Engagement alone can mislead. Someone can open every email you send and never intend to buy.&lt;/p&gt;

&lt;h2&gt;
  
  
  Building the model in a spreadsheet first
&lt;/h2&gt;

&lt;p&gt;Create four columns: lead identifier, fit score (0 to 10), intent score (0 to 20) and engagement score (0 to 10). Assign points using rules you can explain in one sentence each. For example, "VP title at a 50 to 500 employee SaaS company = 8 fit points" or "visited the pricing page twice in seven days = 15 intent points."&lt;/p&gt;

&lt;p&gt;Sum the rows. Anything above 25 goes to sales, 15 to 25 stays in nurture, and below 15 gets archived. Then test the thresholds against your last 50 closed-won and closed-lost deals to see whether the line feels right. If most of your won deals score below 25, the thresholds are too strict, or a signal is missing.&lt;/p&gt;

&lt;p&gt;Keep the first version rough. A model that is roughly right and easy to explain beats a perfect one nobody trusts.&lt;/p&gt;

&lt;h2&gt;
  
  
  How often should you review the scores?
&lt;/h2&gt;

&lt;p&gt;Review the rules on a fixed schedule, such as once a month, and change one thing at a time. If you change three rules at once, you cannot tell which change helped. Ask sales which leads they enjoyed working and which felt like a waste, then check how those leads scored.&lt;/p&gt;

&lt;h2&gt;
  
  
  When to graduate to automation
&lt;/h2&gt;

&lt;p&gt;Move to a CRM or marketing automation tool only after the spreadsheet model has run for two full sales cycles without major rule changes. At that point you have proven the logic, identified the data gaps, and earned the right to spend budget on implementation. Until then, manual scoring forces you to confront every assumption and keeps the feedback loop tight between marketing and sales.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://rachitportfolio-rouge.vercel.app/blog/why-ai-image-prompts-need-style-reference" rel="noopener noreferrer"&gt;https://rachitportfolio-rouge.vercel.app/blog/why-ai-image-prompts-need-style-reference&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>aidesign</category>
      <category>marketing</category>
      <category>abotwrotethis</category>
    </item>
    <item>
      <title>A Starter Lead Scoring Model You Can Build in a Day</title>
      <dc:creator>Rachit Sharma</dc:creator>
      <pubDate>Thu, 22 Oct 2026 09:10:22 +0000</pubDate>
      <link>https://dev.to/rachitsharma08/a-starter-lead-scoring-model-you-can-build-in-a-day-3n7m</link>
      <guid>https://dev.to/rachitsharma08/a-starter-lead-scoring-model-you-can-build-in-a-day-3n7m</guid>
      <description>&lt;h2&gt;
  
  
  Why most teams overcomplicate lead scoring
&lt;/h2&gt;

&lt;p&gt;Lead scoring fails when it tries to predict revenue before understanding behavior. I would start with a model that flags readiness, not lifetime value, because readiness is observable and revenue is speculative. The goal is to give sales a shorter list of people who have actually shown up, not a ranked list of everyone who might buy.&lt;/p&gt;

&lt;p&gt;A simple model also gets used. Sales teams ignore a score they cannot explain, and a score nobody reads is just a number in a database. If a rep asks why a lead is on the list, you should be able to answer in one sentence.&lt;/p&gt;

&lt;h2&gt;
  
  
  The three signal types worth tracking
&lt;/h2&gt;

&lt;p&gt;Fit signals tell you if the person matches your ideal customer profile: company size, role, industry and technology stack. Intent signals show active research: pricing page visits, demo requests, competitor comparisons and content downloads. Engagement signals measure responsiveness: email opens, click-throughs, reply rates and meeting attendance.&lt;/p&gt;

&lt;p&gt;I would weight intent highest, fit second, and engagement third, because intent correlates most directly with near-term action. Engagement alone can mislead. Someone can open every email you send and never intend to buy.&lt;/p&gt;

&lt;h2&gt;
  
  
  Building the model in a spreadsheet first
&lt;/h2&gt;

&lt;p&gt;Create four columns: lead identifier, fit score (0 to 10), intent score (0 to 20) and engagement score (0 to 10). Assign points using rules you can explain in one sentence each. For example, "VP title at a 50 to 500 employee SaaS company = 8 fit points" or "visited the pricing page twice in seven days = 15 intent points."&lt;/p&gt;

&lt;p&gt;Sum the rows. Anything above 25 goes to sales, 15 to 25 stays in nurture, and below 15 gets archived. Then test the thresholds against your last 50 closed-won and closed-lost deals to see whether the line feels right. If most of your won deals score below 25, the thresholds are too strict, or a signal is missing.&lt;/p&gt;

&lt;p&gt;Keep the first version rough. A model that is roughly right and easy to explain beats a perfect one nobody trusts.&lt;/p&gt;

&lt;h2&gt;
  
  
  How often should you review the scores?
&lt;/h2&gt;

&lt;p&gt;Review the rules on a fixed schedule, such as once a month, and change one thing at a time. If you change three rules at once, you cannot tell which change helped. Ask sales which leads they enjoyed working and which felt like a waste, then check how those leads scored.&lt;/p&gt;

&lt;h2&gt;
  
  
  When to graduate to automation
&lt;/h2&gt;

&lt;p&gt;Move to a CRM or marketing automation tool only after the spreadsheet model has run for two full sales cycles without major rule changes. At that point you have proven the logic, identified the data gaps, and earned the right to spend budget on implementation. Until then, manual scoring forces you to confront every assumption and keeps the feedback loop tight between marketing and sales.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://rachitportfolio-rouge.vercel.app/blog/starter-lead-scoring-model-one-day" rel="noopener noreferrer"&gt;https://rachitportfolio-rouge.vercel.app/blog/starter-lead-scoring-model-one-day&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>marketingautomation</category>
      <category>marketing</category>
      <category>abotwrotethis</category>
    </item>
    <item>
      <title>Cleaning an Inactive Email List Without the Panic</title>
      <dc:creator>Rachit Sharma</dc:creator>
      <pubDate>Mon, 19 Oct 2026 04:01:04 +0000</pubDate>
      <link>https://dev.to/rachitsharma08/cleaning-an-inactive-email-list-without-the-panic-2png</link>
      <guid>https://dev.to/rachitsharma08/cleaning-an-inactive-email-list-without-the-panic-2png</guid>
      <description>&lt;h2&gt;
  
  
  Why do inactive subscribers hurt deliverability?
&lt;/h2&gt;

&lt;p&gt;Mailbox providers judge your sender reputation largely by how recipients interact with your incoming messages. When a large share of your list ignores, deletes, or leaves emails unopened for months, providers like Gmail and Yahoo assume your content is unwanted and begin routing future sends toward the spam folder.&lt;/p&gt;

&lt;p&gt;Deliverability is not just about avoiding explicit spam complaints or hard bounces. Modern filtering algorithms look closely at positive engagement signals, including open rates, replies, and moves to priority folders. If you keep broadcasting to addresses that show zero activity, you drag down your aggregate engagement score across the entire domain. The result is that even your most loyal readers may stop seeing your updates in their primary inboxes.&lt;/p&gt;

&lt;p&gt;There is also a direct financial cost to maintaining inactive records. Most email service platforms tier their pricing based on contact counts rather than pure send volume. Paying monthly fees to store thousands of dead mailboxes produces negative leverage on your marketing budget, draining funds that could support other channels.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you define an unengaged subscriber?
&lt;/h2&gt;

&lt;p&gt;An unengaged subscriber is someone who has not opened, clicked, or completed a purchase within a defined time window tailored to your regular sending cadence. For daily or weekly senders, that window is typically between sixty and ninety days of complete inactivity.&lt;/p&gt;

&lt;p&gt;I prefer to use a tiered definition rather than an arbitrary cutoff. If you publish once a week, someone who has missed twelve consecutive issues is demonstrating clear disinterest, especially if they joined months earlier. However, if your business publishes only once a month, extending the inactivity window to six months makes more practical sense. The goal is to measure consistent disinterest across multiple opportunities to engage.&lt;/p&gt;

&lt;p&gt;It is also essential to account for privacy features like Apple's Mail Privacy Protection, which can trigger automated pixel loads and show artificial opens. Because open data is no longer perfectly reliable on its own, I look at click events, recent site logins, or purchase history to verify real human attention before categorizing an address as active.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does a safe sunset sequence look like?
&lt;/h2&gt;

&lt;p&gt;A safe sunset sequence is a short, automated two-part workflow designed to give disengaged contacts one final, low-friction chance to confirm their interest. It should be direct, respectful of their time, and clear about the outcome if they choose not to respond.&lt;/p&gt;

&lt;p&gt;I recommend keeping the first email plain text or minimal in design to distinguish it from standard marketing broadcasts. The subject line should be straightforward, asking whether they still want your updates. Inside the message, state plainly that you are cleaning your list to avoid sending unwanted mail, and provide a single prominent link or button that allows them to remain subscribed with one click.&lt;/p&gt;

&lt;p&gt;If the subscriber does not click that link within five to seven days, a second and final notification should let them know they are being removed. This final message should also provide a permanent resubscribe link in case they change their mind later. If there is still no interaction after forty-eight hours, the contact should be moved out of your active broadcast segments immediately.&lt;/p&gt;

&lt;h2&gt;
  
  
  When is it better to delete than to keep trying?
&lt;/h2&gt;

&lt;p&gt;It is better to delete or permanently suppress cold contacts as soon as they complete a sunset workflow without taking action. Spending additional creative effort or ad budget trying to reactivate addresses that ignored multiple direct outreach attempts rarely produces positive returns.&lt;/p&gt;

&lt;p&gt;Marketing teams often hesitate at this step because smaller list counts look like a regression on internal reporting dashboards. That instinct is understandable, but vanity metrics do not pay invoices or protect your IP reputation. A smaller list with an engaged audience produces higher delivery rates, cleaner data for testing, and more predictable campaign performance.&lt;/p&gt;

&lt;p&gt;I prefer to export the suppressed segment to a secure local backup file before removing them from active sending status in the platform. Storing the file ensures you maintain a suppression record against accidental re-imports while keeping your daily database clean, focused, and financially lean.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://rachitportfolio-rouge.vercel.app/blog/cleaning-inactive-email-lists" rel="noopener noreferrer"&gt;https://rachitportfolio-rouge.vercel.app/blog/cleaning-inactive-email-lists&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>emailmarketing</category>
      <category>marketing</category>
      <category>abotwrotethis</category>
    </item>
    <item>
      <title>I Don’t Code. I Built My Portfolio With an AI Coding Agent</title>
      <dc:creator>Rachit Sharma</dc:creator>
      <pubDate>Wed, 14 Oct 2026 07:22:46 +0000</pubDate>
      <link>https://dev.to/rachitsharma08/i-dont-code-i-built-my-portfolio-with-an-ai-coding-agent-877</link>
      <guid>https://dev.to/rachitsharma08/i-dont-code-i-built-my-portfolio-with-an-ai-coding-agent-877</guid>
      <description>&lt;p&gt;I’m Rachit, a digital marketer from Siwan, a village in Kaithal district, Haryana, India. I’m doing a BBA and a Digital Marketing with AI course. I have never written code in my life. Not properly, anyway.&lt;/p&gt;

&lt;p&gt;So when I decided I wanted a real portfolio website, not a template, I had a problem. I knew exactly what I wanted it to look like and what it should say. I just couldn’t build it.&lt;/p&gt;

&lt;p&gt;How I started&lt;/p&gt;

&lt;p&gt;I got into AI in 2025 and haven’t really stopped since. Now I use around 25 AI tools. The ones I use most are OpenCode (a coding agent), GPT, Claude, ElevenLabs and Cartesia.&lt;/p&gt;

&lt;p&gt;For this project I split the work in two. Claude was my planner. I’d explain what I wanted, and it helped me turn that into small, clear tasks. OpenCode was the builder. It read my instructions and actually changed the code in my project.&lt;/p&gt;

&lt;p&gt;I didn’t write a single line myself. My job was deciding what to build, checking what came back, and saying no when something looked wrong.&lt;/p&gt;

&lt;p&gt;The rules I made up&lt;/p&gt;

&lt;p&gt;I learned pretty fast that if you give a coding agent a big, vague job, you get a big, vague mess. So I set some rules for myself:&lt;/p&gt;

&lt;p&gt;One small task at a time.&lt;br&gt;
Every task gets its own commit, so I can go back if something breaks.&lt;br&gt;
The agent reports what it did and waits. It does not go off and “fix” other things on its own.&lt;br&gt;
Nothing gets pushed live until the checks pass.&lt;/p&gt;

&lt;p&gt;Honestly, the last two saved me more than once.&lt;br&gt;&lt;br&gt;
“Things that went wrong” &lt;/p&gt;

&lt;p&gt;The biggest one happened on 6 October 2026. My Google account got disabled. Because of that, I had to re-host all my projects, create my GitHub again, and make new accounts for everything. I basically started over from zero. The old version of my site is still online, but this new one is the real one. My projects are now on my new GitHub: &lt;a href="https://github.com/Rachit-Sharma08" rel="noopener noreferrer"&gt;https://github.com/Rachit-Sharma08&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’m still learning, and I’m not pretending to be a developer. I’m a marketer who found a way to build things. If that sounds like you, you can see what I made here: &lt;a href="https://rachitportfolio-rouge.vercel.app/" rel="noopener noreferrer"&gt;https://rachitportfolio-rouge.vercel.app/&lt;/a&gt; and you can see my projects on my GitHub: &lt;a href="https://github.com/Rachit-Sharma08" rel="noopener noreferrer"&gt;https://github.com/Rachit-Sharma08&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>marketing</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
