<?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: Louis Carter</title>
    <description>The latest articles on DEV Community by Louis Carter (@louiscarter196).</description>
    <link>https://dev.to/louiscarter196</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%2F4196928%2Fad3cd563-8e23-4d34-af51-af6ffe0eaff5.png</url>
      <title>DEV Community: Louis Carter</title>
      <link>https://dev.to/louiscarter196</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/louiscarter196"/>
    <language>en</language>
    <item>
      <title>What 50 Backlinks Taught Me About Building a Niche Site in Public</title>
      <dc:creator>Louis Carter</dc:creator>
      <pubDate>Thu, 19 Nov 2026 06:10:44 +0000</pubDate>
      <link>https://dev.to/louiscarter196/what-50-backlinks-taught-me-about-building-a-niche-site-in-public-5h07</link>
      <guid>https://dev.to/louiscarter196/what-50-backlinks-taught-me-about-building-a-niche-site-in-public-5h07</guid>
      <description>&lt;p&gt;Somewhere this month, a spreadsheet I keep crossed fifty rows. Each row is a backlink — a profile, a guest post, an article on someone else's platform, pointing at the small men's grooming site I run, &lt;a href="https://fadehaircutstyles.com/" rel="noopener noreferrer"&gt;Fade Haircut Styles&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Fifty isn't a big number in SEO terms. Agencies promise hundreds. But I placed every one of those fifty myself, by hand, over about two months — and doing it the slow way taught me things I don't think a dashboard would have.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lesson one: the first ten links are tuition
&lt;/h2&gt;

&lt;p&gt;Almost nothing measurable happened after my first ten backlinks. Traffic didn't move. Rankings didn't move. What moved was me: I learned how to write a pitch that doesn't sound like a template, which platforms answer emails and which ones are contact forms into the void, and how long a genuinely personalised outreach message actually takes.&lt;/p&gt;

&lt;p&gt;If I'd judged the whole strategy by link number eight, I'd have quit before the strategy had a chance to be a strategy. Early links in a project like this are tuition. You pay them to learn the work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lesson two: relevance beats authority, and it isn't close
&lt;/h2&gt;

&lt;p&gt;The internet's advice is obsessed with domain authority. Chasing it sent me towards big, general platforms that had no real connection to grooming — and those turned out to be the hardest placements to get and, honestly, the least satisfying to land.&lt;/p&gt;

&lt;p&gt;The links that felt different were the boring ones: a grooming publication, a barber-adjacent community, an article where my link sat inside a paragraph that was actually about the thing it pointed to. A modest site in the niche beats a giant site outside it — for the reader who clicks, and, I'd bet, for the algorithm too.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lesson three: no single link does anything
&lt;/h2&gt;

&lt;p&gt;This is the one nobody wants to hear. There was no link — not the guest post I was proudest of, not the profile on the biggest platform — after which the graph jumped. What the graph did instead was drift: impressions a little higher each fortnight, a page creeping from position twelve to position nine.&lt;/p&gt;

&lt;p&gt;Backlinks at this scale are compound interest, not a lottery ticket. Each one is nearly worthless. Fifty of them, all relevant, all still live, are a foundation. The mindset shift is realising you're not collecting wins. You're making deposits.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lesson four: the spreadsheet is the strategy
&lt;/h2&gt;

&lt;p&gt;I track every placement: platform, date, the exact page, the anchor text, whether it's still indexed. It's unglamorous and it is, no exaggeration, the thing that makes the whole operation work. It stops me pitching the same site twice. It stops me reusing the same anchor text until my link profile looks manufactured. And on the flat weeks, it's the only evidence that the work is accumulating — fifty rows of it.&lt;/p&gt;

&lt;p&gt;Solo operators don't burn out from doing the work. They burn out from not being able to see it. The sheet is how you see it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lesson five: warm up before you link
&lt;/h2&gt;

&lt;p&gt;Several platforms on my list got value from me before they got a link from me: answers with no URL in them, posts that were purely useful, a profile that existed for a few weeks before it pointed anywhere. The accounts that opened with a link mostly went nowhere — a couple got removed, and they deserved to be.&lt;/p&gt;

&lt;p&gt;It cost me patience and nothing else. Everything in this project that's worked has worked on a delay, and the warm-up is just the delay applied on purpose.&lt;/p&gt;

&lt;h2&gt;
  
  
  What fifty links actually bought
&lt;/h2&gt;

&lt;p&gt;Not traffic, not yet — a position. The site shows up for things it didn't show up for in August. The next fifty links get to push on rankings that already exist instead of starting from zero.&lt;/p&gt;

&lt;p&gt;If you're building something small in public: how are you counting progress when the graph refuses to jump?&lt;/p&gt;

</description>
      <category>writing</category>
      <category>career</category>
      <category>productivity</category>
      <category>discuss</category>
    </item>
    <item>
      <title>What Writing One Good Reference Page Taught Me About Documentation</title>
      <dc:creator>Louis Carter</dc:creator>
      <pubDate>Thu, 05 Nov 2026 03:13:30 +0000</pubDate>
      <link>https://dev.to/louiscarter196/what-writing-one-good-reference-page-taught-me-about-documentation-90</link>
      <guid>https://dev.to/louiscarter196/what-writing-one-good-reference-page-taught-me-about-documentation-90</guid>
      <description>&lt;p&gt;I write documentation for a living in the loosest sense: I run a small niche content site on my own, and most of its pages are reference pages. Somebody arrives with one question, wants one answer, and leaves. For a long time I wrote those pages like essays — a bit of background, a bit of history, the answer somewhere in the middle if you were patient enough to find it.&lt;/p&gt;

&lt;p&gt;Then I rewrote one page properly, and it changed how I think about every page I write now, including the technical notes I keep for myself.&lt;/p&gt;

&lt;h2&gt;
  
  
  A reference page is a contract, not an essay
&lt;/h2&gt;

&lt;p&gt;The useful mental model, borrowed shamelessly from API design, is this: the reader arrives with a single call in mind. They want to know what a thing is, what it does, and how to use it — in that order, without ceremony.&lt;/p&gt;

&lt;p&gt;If the first paragraph does not answer the question, the page has already failed, however well written the rest of it is. Nobody opens a reference page to be persuaded. They open it to be oriented, and then to act.&lt;/p&gt;

&lt;p&gt;That sounds obvious. It took me an embarrassing number of pages to actually honour it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The four-part shape that finally worked
&lt;/h2&gt;

&lt;p&gt;The page that clicked for me follows a shape I now reuse everywhere:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. A definition in plain language.&lt;/strong&gt; One paragraph, no jargon that needs its own explanation. If the definition needs a glossary, it is not a definition yet.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Scope and boundaries.&lt;/strong&gt; What the thing is, and just as importantly what it is not. Most confusion I see in documentation — mine included — is not a lack of information. It is a reader applying the right concept to the wrong case, because nobody told them where the concept stops.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Concrete usage.&lt;/strong&gt; Not a list of possibilities, but the exact words, commands, or steps a person would use in real life. Vague advice is worse than no advice, because it looks complete while leaving the reader to guess.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. What happens over time.&lt;/strong&gt; How long the answer stays true, what degrades first, and when to come back. A reference page that pretends nothing changes is lying by omission.&lt;/p&gt;

&lt;p&gt;The clearest example I have is &lt;a href="https://fadehaircutstyles.com/taper-fade-haircut/" rel="noopener noreferrer"&gt;a guide to the taper fade&lt;/a&gt;: it starts by separating a taper from a full fade, then names exactly where the taper lives, gives the reader the words to use when asking for it, and ends with how long it holds its shape before it needs attention. The structure is doing the work, not the prose.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I stopped doing
&lt;/h2&gt;

&lt;p&gt;Three habits, all of which felt like good writing at the time:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Opening with history.&lt;/strong&gt; Interesting, sometimes, but it delays the answer and tells the reader this page is about the author's knowledge rather than their problem. History goes at the end now, if it goes anywhere.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Covering every edge case up front.&lt;/strong&gt; Edge cases belong in a clearly marked section after the main path, not woven into the definition. When everything is equally prominent, nothing is findable.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Writing for the reader who already agrees.&lt;/strong&gt; I used to write as if the reader had arrived convinced. In practice, the reader who most needs a reference page is the one who is unsure, or who has heard two conflicting versions. Writing for that person — naming the confusion directly, then resolving it — made the pages measurably more useful, because it answered the question they actually typed.&lt;/p&gt;

&lt;h2&gt;
  
  
  A test I run before publishing
&lt;/h2&gt;

&lt;p&gt;Before a reference page goes out, I ask three questions:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Can a stranger state the answer in one sentence after thirty seconds?&lt;/li&gt;
&lt;li&gt;Can they act on it without re-reading the page?&lt;/li&gt;
&lt;li&gt;Can they tell when it no longer applies to them?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If any answer is no, the page is not finished, no matter how polished it reads. Usually the fix is not more writing. It is moving one paragraph to the top, deleting one paragraph entirely, or adding a single sentence that says "this is not for you if…"&lt;/p&gt;

&lt;p&gt;That last sentence is the most underrated line in documentation. It costs nothing, and it saves the reader who was about to follow the wrong instructions entirely.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this matters beyond content sites
&lt;/h2&gt;

&lt;p&gt;I am not a developer by trade, but I suspect this is familiar territory. The README nobody reads, the internal wiki page everyone skims and then asks about in chat anyway, the API doc that explains authentication in paragraph nine — these are all the same failure. The information is there. The contract is not.&lt;/p&gt;

&lt;p&gt;Good documentation is not comprehensive documentation. It is documentation that respects the shape of the question: what is this, where does it stop, how do I use it, and how long does it last?&lt;/p&gt;

&lt;p&gt;If you maintain docs, internal or public, I am curious: which page of yours gets the most "I read it but still wasn't sure" questions — and which of those four parts is it missing?&lt;/p&gt;

</description>
      <category>documentation</category>
      <category>writing</category>
      <category>career</category>
      <category>discuss</category>
    </item>
    <item>
      <title>What Running a One-Person Outreach Operation Taught Me About Follow-Ups</title>
      <dc:creator>Louis Carter</dc:creator>
      <pubDate>Sun, 25 Oct 2026 06:01:55 +0000</pubDate>
      <link>https://dev.to/louiscarter196/what-running-a-one-person-outreach-operation-taught-me-about-follow-ups-2p7c</link>
      <guid>https://dev.to/louiscarter196/what-running-a-one-person-outreach-operation-taught-me-about-follow-ups-2p7c</guid>
      <description>&lt;p&gt;I spent a long time thinking follow-ups were rude. Sending a second email to someone who hadn't replied felt like nagging — like I was the person who double-texts and then wonders why nobody answers.&lt;/p&gt;

&lt;p&gt;Then I started running outreach for a one-person content operation, and I learned the opposite: most non-replies aren't rejections. They're just lost in someone else's inbox.&lt;/p&gt;

&lt;h2&gt;
  
  
  The inbox is not a verdict
&lt;/h2&gt;

&lt;p&gt;Editors, site owners, and collaborators get dozens of pitches a week. Mine was landing somewhere between a newsletter, a PR blast, and an invoice reminder. If it didn't get opened in the first day, it sank — not because it was bad, but because inboxes don't resurface things on their own.&lt;/p&gt;

&lt;p&gt;Once I accepted that, follow-ups stopped feeling like pressure and started feeling like a second chance for the first email to be seen at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  One follow-up, then I move on
&lt;/h2&gt;

&lt;p&gt;My rule now is simple: one polite follow-up, about a week later, and then I drop it and move on.&lt;/p&gt;

&lt;p&gt;The follow-up is short — shorter than the original pitch. It restates the idea in one line, adds nothing new to argue about, and ends with an easy out: "No worries at all if it's not a fit." That last line matters more than it looks. It gives the other person permission to say no quickly, which is the only kind of no that doesn't linger.&lt;/p&gt;

&lt;p&gt;What I don't do: a second follow-up, a "just bumping this to the top of your inbox" third email, or a follow-up that pretends the first one never happened. One is professional. Two starts to feel like a funnel.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rejection is data, silence usually isn't
&lt;/h2&gt;

&lt;p&gt;The replies I actually learned from were the no's. A short "not right for us right now" told me more about fit than a month of silence ever did. Silence, on the other hand, taught me almost nothing — the same pitch that got no reply from one editor got an enthusiastic yes from another.&lt;/p&gt;

&lt;p&gt;So I stopped rewriting pitches based on silence. If an idea gets no reply twice, from two different people, that's a signal about the idea. If it gets no reply once, that's a signal about timing, workload, or a Tuesday afternoon inbox. Those are very different problems, and only one of them is worth fixing.&lt;/p&gt;

&lt;h2&gt;
  
  
  The spreadsheet that made it bearable
&lt;/h2&gt;

&lt;p&gt;The unglamorous part: I track every outreach in one sheet — who, when, what I pitched, and whether I followed up. Without it, I either forgot to follow up entirely or, worse, followed up with someone I'd already pitched twice.&lt;/p&gt;

&lt;p&gt;The sheet also quietly changed my attitude. When you can see forty pitches and twelve replies in one place, a single silence stops feeling personal. It's just a row in a table. That distance is what lets a solo operator keep pitching without burning out on it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd tell another solo operator
&lt;/h2&gt;

&lt;p&gt;Follow up once, politely, and then let it go. Treat silence as inbox physics, not judgement. And keep a record, because your memory will either catastrophise the silence or forget the follow-up — and both cost you more than the email itself.&lt;/p&gt;

&lt;p&gt;If you run outreach solo, I'm curious: what's your follow-up rule? One and done, or do you have a number that works for you?&lt;/p&gt;

</description>
      <category>career</category>
      <category>writing</category>
      <category>productivity</category>
      <category>discuss</category>
    </item>
    <item>
      <title>I Run a One-Person Content Business — Here's the Publishing System That Keeps It Sane</title>
      <dc:creator>Louis Carter</dc:creator>
      <pubDate>Tue, 20 Oct 2026 21:32:02 +0000</pubDate>
      <link>https://dev.to/louiscarter196/i-run-a-one-person-content-business-heres-the-publishing-system-that-keeps-it-sane-22g6</link>
      <guid>https://dev.to/louiscarter196/i-run-a-one-person-content-business-heres-the-publishing-system-that-keeps-it-sane-22g6</guid>
      <description>&lt;p&gt;I don't have a team. It's me, a laptop, and a publishing schedule that would collapse inside a week if it lived in my head.&lt;/p&gt;

&lt;p&gt;I run a small niche content site solo — research, writing, editing, publishing, promotion, all of it. After a few years of doing this the loud way (bursts of motivation, then silence), I rebuilt the whole operation around one idea: &lt;strong&gt;the system should be boring, so the work doesn't have to be.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Here's what actually stuck.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. One calendar, not five apps
&lt;/h2&gt;

&lt;p&gt;Everything I publish — articles, updates, guest posts, social posts — goes on a single calendar. Not a project board, not a notes app, a calendar with dates on it.&lt;/p&gt;

&lt;p&gt;The rule that made it work: &lt;strong&gt;drafting and publishing are separate events, on separate days.&lt;/strong&gt; I write things when I have the energy, then schedule them to go out spaced like a person actually lives — one or two a day, never a burst of nine. A queue of finished work sitting between me and the publish button is the whole trick. Motivation fills the queue; the calendar empties it.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Two queues, brutally labelled
&lt;/h2&gt;

&lt;p&gt;Every piece of content is in exactly one of two states:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Ready&lt;/strong&gt; — finished, checked, could go live today.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;In draft&lt;/strong&gt; — everything else, no matter how "almost done" it feels.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;"Almost done" is where solo operations go to die. If it's not ready, it doesn't get a date. This one distinction killed the Sunday-night scramble completely.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Batch by type of energy, not by topic
&lt;/h2&gt;

&lt;p&gt;Research days, writing days, editing days. Switching between them is where my hours used to leak. A research session produces raw material for four or five pieces, not one. A writing session is only allowed to open drafts, never a blank page and a search engine at the same time.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. One spreadsheet for what happened
&lt;/h2&gt;

&lt;p&gt;I track every piece I publish in one plain spreadsheet: where it went, when, and what it links to. Once a week, ten minutes, I update it and look at what's actually moving. Not daily — daily metrics-watching is just anxiety with charts.&lt;/p&gt;

&lt;p&gt;The spreadsheet has saved me more than once. Duplicate content, forgotten follow-ups, a pitch I sent twice to the same editor (once — never again).&lt;/p&gt;

&lt;h2&gt;
  
  
  5. A weekly review that takes 20 minutes
&lt;/h2&gt;

&lt;p&gt;Same time every week:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;What's in the ready queue? (Less than a week of runway = writing becomes the priority.)&lt;/li&gt;
&lt;li&gt;What's waiting on someone else? (One polite follow-up, then I move on.)&lt;/li&gt;
&lt;li&gt;What did last week's numbers quietly tell me?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;That's it. No quarterly planning theatre. The review is small enough that I never skip it, which matters more than it being thorough.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd tell another solo operator
&lt;/h2&gt;

&lt;p&gt;Your system doesn't need to be impressive. It needs to survive your worst week, not showcase your best one. Mine is a calendar, two queues, and a spreadsheet — and it has carried the whole business for years now.&lt;/p&gt;

&lt;p&gt;If you run something solo, I'd genuinely like to hear what your version looks like. Especially if it's weirder than mine.&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>writing</category>
      <category>career</category>
      <category>discuss</category>
    </item>
  </channel>
</rss>
