Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #6676

S

Swimm

Company blog · swimm.io/blogprogrammingcareer

Swimm is the company blog at swimm.io, writing about programming and career. Since 2020, 11 different Hacker News readers have linked it 43 times, most often “Swimm: Knowledge Management and Documentation for Code”. It is still writing: the last post was on 2026-10-07, and you can follow it by feed.

Visit the blog
43mentions?
11HN people?
2020–2023first – last linked?
Links on Hacker News per year · peak 22 in 2020

Too few sampled comments (3) to say how often HN recommends it.?

Why HN links it

HN commenters link Swimm's blog for a comparison of code comments and documentation, and mention its docs-as-Markdown-in-repos idea. None of the comments judge the writing itself.

Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

We build what you need, grounded in your existing system, and leave your team an agent-ready foundation to keep building on, with Swimm or on their own.

Most-linked posts?

  1. Swimm: Knowledge Management and Documentation for Code
    4 people · 4 mentions · first linked 2020-10-08
  2. We Chose Node.js over Python for Our Product
    2 people · 2 mentions · first linked 2020-10-31
  3. Don't Sink, Swim: Guide for Dev Mentors
    2 people · 2 mentions · first linked 2020-09-14
  4. Vue vs React: Best Choice for Startups
    2 people · 2 mentions · first linked 2020-09-23
  5. We Switched from GitHub Issues to Jira to ClickUp
    2 people · 2 mentions · first linked 2020-12-17

What Hacker News says?

  1. 2 different things https://swimm.io/blog/code-comments-vs-documentation/

    Comment linking /blog/code-comments-vs-documentation/

    on “Developers spend most of their time figuring the system out”
  2. Submitted Vue vs React: Best Choice for Startups as a story · 63 points

    HN discussion
  3. You should check https://swimm.io/ 1. Docs are kept as .MD files in your repos 2. You can use Docusaurus to Publish them 3. They use the Github hierarchy and authorization to decide who has access to the docs. They are in beta, worth checking

    Comment linking /

    on “Ask HN: How do you keep documentation?”
  4. Submitted Get Started with Infection Monkey, Open Source Security Tool as a story · 52 points

    HN discussion
  5. There are two main problems with wikis : Maintaining and Finding. I'll start with the second, because it is 2023, and wikis are finally embracing semantic search [0] This will not only almost solve this problem. It will also alleviate the need for heavy handed organization in general 9categories..) The first problem is best solved IMO with getting someone responsible for gardening it as someone put it in this thread…

    Comment linking /

    on “Ask HN: What's the best way to organize a company's engineering wiki?”
  6. Submitted Creating Effective Tutorials for Your Dev Team as a story · 25 points

    HN discussion
  7. Submitted Creating up-to-date diagrams in internal docs with Mermaid as a story · 17 points

    HN discussion
  8. Submitted Software Development Knowledge Sharing Methods Are Broken: Here’s Why as a story · 10 points

    HN discussion
  9. Submitted What Every Manager Has to Know About Developer Happiness as a story · 9 points

    HN discussion
  10. Submitted Forming Professional Dev Team Habits as a story · 8 points

    HN discussion
  11. Submitted Should developer documentation be included in the Definition of Done? as a story · 5 points

    HN discussion
  12. Submitted Remote dev teams need better internal documentation as a story · 3 points

    HN discussion
  13. Submitted Swimm: Knowledge Management and Documentation for Code as a story · 3 points

    HN discussion
  14. Submitted How to Document Tribal Knowledge While Offboarding Employees as a story · 3 points

    HN discussion
  15. Submitted We Migrated from Webpack to Vite as a story · 3 points

    HN discussion
  16. Submitted We built our GitHub app as a story · 3 points

    HN discussion
  17. Submitted Creating a Guide for Code Review as a story · 3 points

    HN discussion
  18. Submitted Effective Feedback for Engineers as a story · 3 points

    HN discussion
  19. Submitted Rewriting History and Overcoming Git Disasters as a story · 3 points

    HN discussion
  20. Submitted We Chose Node.js over Python for Our Product as a story · 3 points

    HN discussion
  21. Submitted The End to Pseudo Onboarding: Your Engineers Will Thank You as a story · 3 points

    HN discussion
  22. Submitted Evangelizing Mentorship within Asana's R&D Teams as a story · 2 points

    HN discussion
  23. Submitted End-to-end testing: challenges, lessons, implementation as a story · 2 points

    HN discussion
  24. Submitted Remote onboarding doesn't have to suck as a story · 2 points

    HN discussion
  25. Submitted Supabase now in beta, get started with Vue as a story · 2 points

    HN discussion
  26. Submitted Supabase now in beta, get started with Vue as a story · 2 points

    HN discussion
  27. Submitted Learn how to dive into a new codebase (Front end vs. back end) as a story · 2 points

    HN discussion
  28. Submitted We Chose Node.js over Python for Our Product as a story · 2 points

    HN discussion
  29. Submitted Don't Sink, Swim: Guide for Dev Mentors as a story · 2 points

    HN discussion
  30. Submitted Developing Open Source Skills as a story · 2 points

    HN discussion

Search all of HN for swimm.io