Where to post software engineering articles

Here's the full landscape for where to post software engineering content, organized by goal:

Own domain (best for long-term SEO and personal brand)

• Ghost — fast, clean technical SEO out of the box (metadata, sitemaps, URL structure), minimal setup overhead.
• WordPress.org (self-hosted) — most flexible, extensive SEO plugin ecosystem, more maintenance.
• Hashnode — publishes to your own custom domain while still getting developer-community discovery layered on top; the easiest option that doesn't sacrifice ownership.
• GitHub Pages (Jekyll/Hugo) — free, Git-native, fully portable, but zero built-in discovery — you're entirely responsible for driving traffic.

Fast community feedback and validation

• Dev.to — large, active developer audience, tag-based discovery, strong peer engagement (comments/reactions); good for validating whether a piece resonates before investing more in it.
• Hacker News — not a publishing platform, but sharing genuinely strong engineering content there (when relevant, not self-promotional) can produce real traffic and is widely read by engineers and founders.

Editorially curated, bigger reach and credibility

• The Pragmatic Engineer — the standout destination specifically for engineering management, architecture, and Big Tech practice content, though it's primarily a single-author publication rather than open to general submissions.
• In Plain English — curated network (~3.5M monthly views), accepts guest posts and syndication with editorial review; strong for both reach and credibility.
• HackerNoon — open submissions with editorial curation, broad tech/engineering culture coverage.
• InfoQ, The New Stack — skew toward architecture, DevOps, and enterprise engineering specifically — a good fit if your content is more systems/infrastructure-focused than general programming tutorials.
• Martin Fowler's site — not open to submissions, but worth knowing as the benchmark for what "timeless architecture writing" looks like if you're aiming for that register.

Company/engineering-team blogs (if you're writing on behalf of an org)

• Publishing under your own company's engineering blog (Netflix/Uber/Stripe-style) builds both the company's technical brand and individual authors' credibility — real postmortems and architecture decisions consistently outperform generic advice for engagement and citations.
• If your company doesn't have one yet, platforms like Ghost or a subdirectory on the main company site (rather than a subdomain) are recommended for SEO consolidation.

Broad reach / secondary distribution

• Medium — large cross-industry audience, useful for visibility and referral traffic, but nofollow links limit direct SEO benefit; best as a syndication target, not a primary home.
• LinkedIn Articles — strong for professional/career-oriented engineering content specifically, reaches hiring managers and industry peers directly.

The practical strategy, consistent with everything covered in this thread

1. Publish canonically on your own domain (or company engineering blog) first — this is where authority and ownership compound.
2. Syndicate to Dev.to and/or Hashnode with a canonical URL back to your original — captures community reach without losing SEO value.
3. Pitch standout, well-developed pieces to a curated publication (In Plain English, InfoQ, HackerNoon) for a larger one-time reach and credibility boost.
4. Share selectively in relevant communities (Hacker News, niche subreddits/Discords) framed around genuine relevance, not self-promotion.

How to choose based on what you're writing

• Deep architecture/systems content → your own domain + InfoQ/The New Stack for reach.
• Quick tips, how-tos, early drafts → Dev.to directly.
• Engineering culture, career, industry analysis → In Plain English or pitch to The Pragmatic Engineer-adjacent publications.
• Company-representing technical writeups → your company's own engineering blog, syndicated selectively.