r/learnmachinelearning Community Analysis

1. Data Sources & Methodology

• Subreddit: r/learnmachinelearning (624,006 subscribers)
• Total unique posts analyzed: 364 (after deduplication across 16 raw JSON files)
• Date collected: 2026-04-03
• Score range: 2 to 5,663
• Median score: ~541 (estimated from position ~182 in ranked dataset)
• Top 25 threshold: ~1,839
• Top 50 threshold: ~1,200

Period breakdown:

Cross-subreddit score calibration: r/learnmachinelearning peaks at ~5,663 -- lower than r/webdev's ~18,701 or r/ClaudeAI's ~8,084 but higher than r/learnpython's ~3,657 or r/macapps' ~2,029. Despite 624K subscribers, this community's scores are moderate because it is education-oriented rather than a viral content engine. A score of 500+ is a solid hit. 1,000+ is a strong performer. 2,000+ puts you in legendary territory (only ~12 posts ever). The median is comparable to r/learnpython (~194) adjusted upward, reflecting slightly more meme/visual content that attracts passive scrollers.

This is a content strategy guide, not a sociological study.

2. Subreddit Character

r/learnmachinelearning is a classroom that periodically turns into a group therapy session for people who feel overwhelmed by the pace of AI. It is not a research forum (that is r/MachineLearning), not a product launch platform, and not a career board (though career content increasingly dominates). It exists for people learning ML -- from high schoolers writing their first neural network to grad students struggling with diffusion model papers.

Community identity: Primarily students and early-career professionals. A striking proportion are from South Asia (references to CampusX, Hindi-language tutorials, Indian university programs like Amazon ML Summer School appear frequently). The audience skews young (college students, recent grads), technically ambitious but often overwhelmed. Many are self-taught, transitioning from software engineering, or pursuing masters degrees. A recurring archetype is "I know Python, now what?"

Product launches: Not explicitly banned but structurally discouraged. Rule 3 states: "Post nothing that involves monetary transactions." The community tolerates free tools enthusiastically (TensorTonic with 824 score, ml-visualized.com with 609 score) but becomes hostile toward anything with a commercial smell. The "AI Skills Matrix" post by Kirill_Eremenko (417 score, 0.78 ratio) shows what happens when content feels like marketing -- heavy downvote friction despite high absolute score. Two identical "TensorFlow is becoming COBOL" posts from different accounts (netcommah at 649/0.90 and IT_Certguru at 415/0.93) both contained embedded course marketing links and generated skepticism.

Key cultural values (ranked):

1. Math fundamentalism -- "ML is math. You need math" (761 score, 149 comments). The community deeply values understanding fundamentals over API-calling. Posts about learning linear algebra from scratch, hand-deriving backprop, and building neural networks without frameworks consistently outperform.
2. From-scratch credibility -- Building things without frameworks is the highest-status activity. CNN in x86 assembly (1,776 score), neural net in C++ at age 15 (1,839 score), neural net from scratch in JS (1,009 score). The community rewards demonstrated understanding over production utility.
3. Free resource sharing -- Free books, free courses, free Stanford lectures, free Google Drive links. The "50 Free ML and DS Ebooks" post (1,883 score) and "Free ML, AI, and DL Books" post (1,842 score) are all-time top performers.
4. Career anxiety solidarity -- "Traditional ML is dead" (2,038 score, 359 comments), "Why most people learning AI won't make it" (672 score, 142 comments). The community bonds over shared fear about the job market.
5. Anti-credentialism tempered by credential worship -- Posts from FAANG engineers and 19-year veterans get massive engagement (AMA from 19-year ML vet: 1,860 score, 538 comments), while simultaneously the community celebrates 15-year-olds building neural nets from scratch.

Enforcement mechanisms: Light moderation. Rule 2 limits self-promotion to once per week. Rule 3 prohibits monetary content. AutoModerator runs weekly "Project Showcase Day" threads. The "Misleading" flair exists as a community correction mechanism (applied to "Neural Networks Cheat Sheet" at 1,390 score, 0.92 ratio). There is no karma requirement or blacklist system.

How this sub differs from similar subs: r/MachineLearning is for research papers and industry news. r/datascience is for working professionals. r/MLQuestions is for technical Q&A. r/learnmachinelearning is uniquely the "learning journey" sub -- where the process of learning is as valued as the output.

3. The All-Time Leaderboard

Dataset median: ~541. Top 25 threshold: ~1,839.

Notable: The #1 post (Elon Musk fraud, 5,663) is a pure community opinion post with the lowest ratio in the top 10 (0.90), showing that controversial takes can score high but generate friction. The highest-ratio posts (0.99) are universally educational content, project demos, or relatable memes.

4. Content Type Dominance at Scale

Most surprising finding: Posts with NO flair dominate the top 25 (12 of 25, 48%). This community does not enforce flair usage, and many of the highest-performing posts -- memes, opinion pieces, resource shares -- are posted without flair. The "Meme" flair has the highest average score (~1,600) but the smallest sample size (~12 posts), confirming that humor punches far above its weight here.

5. Content Archetypes That Work

Archetype 1: "The Relatable ML Meme" (Score ceiling: 5,663)

Score range: 400-5,663 Examples:

• "So we can all agree that Elon musk is a fraud?" (5,663)
• "Why always it's maths?" (3,727)
• "All the people posting resumes here" (2,712)
• "Life as an AI Engineer" (2,160)
• "Data cleaning is so must" (2,086)

The pattern: Image memes that capture a shared frustration or absurdity of the ML learning journey. Math anxiety, data cleaning drudgery, impostor syndrome, job market despair -- these are the emotional touchpoints. The best memes are specific to the ML experience (not generic tech humor). They consistently score 0.94+ ratios.

Why it matters for distribution: If you are building an ML tool, you cannot launch with a meme. But you CAN build community presence by sharing relatable ML humor before your launch. Meme creators like "harsh5161" and "astarak98" accumulate recognition that would transfer to product launches.

Archetype 2: "Built It From Scratch" (Score ceiling: 3,669)

Score range: 400-3,669 Examples:

• "Machine Learning + Augmented Reality Project" (3,669, VIDEO)
• "I am trying to make a game that learns how to play itself" (2,855, VIDEO)
• "I'm 15 and built a neural network from scratch in C++" (1,839, TEXT)
• "CNN from scratch in x86 Assembly" (1,776, GALLERY)
• "made a neural net from scratch using js" (1,009, VIDEO)

The pattern: Projects that demonstrate deep understanding by eschewing frameworks. The more extreme the constraint (assembly language, no libraries, age 15), the higher the score. VIDEO format dominates because watching an ML model learn in real-time is inherently compelling. GitHub links are expected and rewarded.

Why it matters for distribution: If your tool helps people learn ML fundamentals, framing it as "I built X from scratch to understand Y" is the optimal archetype. The community does not want polished products -- they want visible learning journeys.

Archetype 3: "Free Resource Treasure Chest" (Score ceiling: 1,883)

Score range: 400-1,883 Examples:

• "50 Free ML and Data Science Ebooks" (1,883)
• "Free ML, AI, and DL Books (Google Drive Link)" (1,842)
• "All Stanford AI courses (100% free!)" (1,147)
• "Cornell's entire ML class is now on YouTube" (1,204)
• "List of free educational ML resources I used to become a FAANG ML Engineer" (1,050)

The pattern: Curated collections of free learning resources. The title must emphasize "free." The more comprehensive the list, the better. University-branded content (Stanford, Cornell, Columbia) adds credibility. Google Drive links to book collections are controversial but massively upvoted.

Why it matters for distribution: If your product has a free tier, a free course, or free educational content, this is your entry point. Frame as "free resources" rather than product promotion. The Columbia University course post (572 score, 207 comments) with a promo code shows that even monetized content can succeed if the free angle is genuine.

Archetype 4: "Career Confessional / AMA" (Score ceiling: 2,038)

Score range: 350-2,038 Examples:

• "[RANT] Traditional ML is dead and I'm pissed about it" (2,038, 359 comments)
• "I've been doing ML for 19 years. AMA" (1,860, 538 comments)
• "Advice from someone who interviewed 1,000 MLE candidates" (972, 201 comments)
• "How I Cracked an AI Engineer Role" (571, 44 comments)
• "A first big tech company ML interview experience" (436, 39 comments)

The pattern: Raw, honest career stories generate the highest comment-to-upvote ratios in the dataset. The "19 years AMA" post has 538 comments on 1,860 upvotes (0.29 C/U ratio), making it the most discussion-generating post type. Vulnerability and specificity are key -- "I definitely bombed it" resonates more than polished success stories.

Why it matters for distribution: If you are a domain expert, an AMA or career story builds massive credibility. The audience desperately wants career guidance. A product mention within a genuine career narrative would be far more effective than a standalone launch post.

Archetype 5: "The Learning Journey Series" (Score ceiling: 1,604)

Score range: 340-1,604 Examples:

• "Just Completed 100 Days of ML" (1,604)
• "Day 1 of learning mathematics for AI/ML as a no math person" (566)
• "Day 4 of learning mathematics for AI/ML" (552)
• "Day 2 of learning mathematics for AI/ML" (508)
• "1 Month of Studying Machine Learning" (349)

The pattern: Public accountability posts documenting a learning journey. The "uiux_Sanskar" series (Days 1-4) is remarkable -- each post accumulates 500+ upvotes despite being elementary math notes. The community rewards consistency and vulnerability. Handwritten notes photos are a signature visual.

Why it matters for distribution: A learning tool could sponsor or integrate with this archetype -- "I used [tool] to learn X over 30 days" would be a natural fit, provided the emphasis stays on the journey rather than the tool.

Archetype 6: "Visual ML Explainer" (Score ceiling: 2,881)

Score range: 400-2,881 Examples:

• "A simple example for false positives and false negatives" (2,881)
• "Difference in Image Classification, Semantic Segmentation, Object Detection..." (1,622)
• "Different Distance Measures" (1,307)
• "Deep Learning Activation Functions using Dance Moves" (1,196)
• "Not every problem needs Deep Learning" infographic (1,065)

The pattern: Single-image infographics or cheat sheets that explain an ML concept visually. The simpler and more memorable, the better. These are low-effort to consume but high-effort to create well. They achieve near-perfect ratios (0.98-0.99) because they are universally helpful and non-controversial.

Why it matters for distribution: If your tool produces visualizations, output screenshots that explain concepts can serve as standalone content pieces.

6. Format Analysis

Visual content (IMAGE + VIDEO + GALLERY) accounts for 84% of the top 25 and ~73% of the full dataset. The dominance of IMAGE in the top 25 (56%) reflects the power of memes and infographics in this community.

What Format to Use For What

• ML project demos -- VIDEO is the clear winner. 7 of the top 25 are video demos of ML models in action. Screen recordings of models learning (reinforcement learning games, AR apps, object detection) are the highest-performing project format.
• Educational content -- IMAGE (infographics, cheat sheets, concept diagrams). Single-image explainers consistently outperform multi-image galleries.
• Career stories / rants / AMAs -- TEXT. The "[RANT] Traditional ML is dead" post (2,038) and the "19 years AMA" (1,860) prove that text-only posts can compete with visual content when the emotional payload is strong enough.
• Resource sharing -- IMAGE (screenshot of book covers or course lists) + link in comments. The top resource posts use a visual hook (photo of books, screenshot of course page) with the actual links in the selftext or comments.
• Humor/memes -- IMAGE exclusively. No video memes appear in the top 100.

What Makes a Good Demo Video

Based on top-performing VIDEO posts:

1. Show the model learning in real-time -- The reinforcement learning game videos (Little_french_kev's multiple posts, all 1,500+) work because you can watch the agent improve.
2. Physical/tangible output -- AR apps, robotics, real-world object detection score higher than screen-only demos.
3. No narration needed -- The top video posts have zero audio explanation. The visual is self-explanatory.
4. Under 60 seconds -- Short loops that demonstrate one clear capability.
5. GitHub link in comments -- Every top video project post includes a repo link.

7. Flair/Category Strategy

Raw Performance Ranking

Distribution Utility Ranking

1. Project -- Best for product distribution. Highest ratio (0.98), community expectation of sharing work, and GitHub links are welcomed. Frame your product as a "project I built" rather than a launch.
2. Discussion -- Most versatile. Career stories, concept debates, and resource shares all fit. Good for thought leadership posts that mention your product tangentially.
3. (no flair) -- Acceptable for everything. The community does not gatekeep on flair.
4. Meme -- High risk, high reward. Only use if your content is genuinely funny and ML-specific.
5. Tutorial -- Underused but perfect-ratio. If you have educational content, this flair signals quality.

Flair Anti-Patterns

• "Misleading" flair -- Applied by mods to content that oversimplifies or misrepresents concepts (e.g., "Neural Networks Cheat Sheet" at 1,390 score got this flair). Avoid posting oversimplified content that could attract this label.
• "Help" flair for non-help content -- Using Help when you are actually promoting something will generate friction.

No Pricing Model Hierarchy Needed

This community does not discuss pricing models. Rule 3 explicitly bans monetary transactions. The community values FREE above all else. If your product is free or open-source, lead with that. If it has paid tiers, do not mention pricing -- link to the product and let users discover pricing on their own.

8. Title Engineering

Deconstructing the Top 10 Titles

1. "So we can all agree that Elon musk is a fraud?" -- Technique: Community consensus invitation. Assumes shared opinion, invites validation.
2. "Started learning today and tried classifying my face using my facial recognition AI..." -- Technique: Self-deprecating beginner narrative. The humor comes from the AI failing.
3. "Why always it's maths?" -- Technique: Shared pain in 4 words. Minimal, emotional, uses emoji to signal humor.
4. "Machine Learning + Augmented Reality Project App Link and Github Code given in the comment" -- Technique: Feature combo + deliverables in title. Promises both a demo and source code.
5. "Solve your Rubik Cube using this AI+AR Powered App" -- Technique: Concrete utility + wow factor. Tells you exactly what it does.
6. "Moving on up" -- Technique: Cryptic optimism. Only 3 words. Relies on the image to deliver the joke.
7. "A simple and easy-to-remember example for false positives and false negatives" -- Technique: Promise of simplicity. The word "simple" is a powerful signal in this community.
8. "I am trying to make a game that learns how to play itself using reinforcement learning" -- Technique: Process narration. "I am trying" is more relatable than "I made."
9. "Machine Learning Pipelines" -- Technique: Bare concept name. Works only with a compelling video thumbnail.
10. "All the people posting resumes here" -- Technique: Meta-commentary. References the community itself; only works for frequent visitors.

Title Formulas

Formula 1: "I built [thing] from scratch in [constraint]"

• "I'm 15 and built a neural network from scratch in C++" (1,839)
• "I implemented a CNN from scratch entirely in x86 Assembly" (1,776)
• "made a neural net from scratch using js" (1,009)

Formula 2: "[Concept] visualized / explained simply"

• "A simple and easy-to-remember example for false positives and false negatives" (2,881)
• "Gradient Descent Visualized" (1,185)
• "Different Distance Measures" (1,307)

Formula 3: "[Free resource type] + [credibility signal]"

• "50 Free Machine Learning and Data Science Ebooks by DataScienceCentral" (1,883)
• "All Stanford AI courses (100% free!)" (1,147)
• "Cornell's entire Machine Learning class (CS 4780) is now entirely on YouTube" (1,204)

Formula 4: "[Emotional state] + ML context"

• "[RANT] Traditional ML is dead and I'm pissed about it" (2,038)
• "How tf do you stay up to date in such a breaknecking speedy field?" (1,204)
• "I can't be the only one..." (1,386)

Formula 5: "I've been doing ML for [N years]. [Offer]"

• "I've been doing ML for 19 years. AMA" (1,860)
• "Advice from someone who has interviewed 1,000 MLE candidates over 15 years" (972)
• "I started my ML journey in 2015... AMA" (353)

Title Anti-Patterns

• Clickbait without substance: "Helppp" (541 score, but only because it was a meme image about a book). Single-word panic titles work only with strong visual content.
• Marketing language: "AI Skills Matrix 2025 - what you need to know as a Beginner!" (417 score, 0.78 ratio -- the lowest ratio in the top 100). The exclamation mark and "what you need to know" framing triggered the community's marketing detector.
• Over-promising: "Which AI lies the most?" (431 score, 0.72 ratio -- the lowest ratio in the entire year dataset). The methodology was challenged in comments. Claims of novel research must be backed by rigorous methodology.
• Duplicate posts: Two nearly identical "TensorFlow is COBOL" posts appeared weeks apart from different authors (649 and 415). The community noticed.
• "[D]" prefix: Borrowed from r/MachineLearning convention. "[D] Can someone please teach me how transformers work?" (640, 0.93) -- the meme worked but the prefix felt out of place.

9. Engagement Patterns

If your goal is VISIBILITY: Post a meme or visual explainer image. These get the highest scores relative to effort and accumulate upvotes from passive scrollers who never comment.

If your goal is RELATIONSHIPS and discussion: Post a career story, AMA, or opinion piece about the state of ML. The "I've been doing ML for 19 years. AMA" post generated 538 comments -- 10x the comments of a typical 1,800-score post. These build name recognition and trust.

Highest-discussion topics (regardless of score):

1. "Traditional ML vs GenAI/LLMs" -- 359 comments on the "Traditional ML is dead" post
2. Career AMAs from experienced practitioners -- 538 comments on the 19-year veteran AMA
3. Amazon ML Summer School results -- 315 comments on a 334-score post (0.94 C/U ratio)
4. "LLMs will not get us AGI" -- 225 comments on a 337-score post
5. Interview experiences -- 201 comments on the "1,000 MLE candidates" advice post

10. What Gets Downvoted

Ratio Tiers

• Above 0.94: Universally well-received. Educational content, from-scratch projects, and genuine memes live here.
• 0.85-0.94: Net positive but with friction. Opinion pieces, career advice with embedded promotion, and hot takes.
• Below 0.85: Controversial or community-hostile. Marketing disguised as content, poorly-argued AGI takes, and gatekeeping.

Notable Low-Ratio Posts

Anti-Patterns

1. "The Stealth Marketer" -- Posts that appear educational but contain embedded affiliate or marketing links. "AI Skills Matrix 2025" (0.78 ratio) by Kirill_Eremenko links to a paid course. "TensorFlow is becoming COBOL" appeared twice from different accounts, both linking to netcomlearning.com. The community can smell marketing.

2. "The Hot Take Without Rigor" -- "LLM's will not get us AGI" (0.84 ratio) presents an opinion without technical depth. The community tolerates strong opinions only when backed by evidence or experience.

3. "The Gatekeeping Rant" -- "Please don't be one of those cringe machine learners" (0.86 ratio) and "Why most people learning AI won't make it" (0.88 ratio) both talk down to learners. In a community that explicitly values being "beginner-friendly" (sidebar), gatekeeping generates backlash.

4. "The Methodology-Questionable Experiment" -- "Which AI lies the most?" (0.72 ratio, the worst in the dataset) claimed to test hallucination rates but used a methodology that commenters found flawed. The community has enough technical knowledge to challenge weak research.

5. "The Thinly Veiled Self-Promotion" -- "Built 4 ML Apps and None of Them Made a Single Dollar" (0.86 ratio) tells a relatable failure story but ends with a pitch for freelancing services and specific tools. The narrative arc from "failure" to "here's how to hire me" felt inauthentic.

6. "The Sensationalist Claim" -- "AI can now see through walls using WiFi signals" (0.89 ratio) -- overhyped headlines trigger the community's BS detector.

7. "The Cross-Post Spam" -- Posts that appear across multiple subreddits simultaneously (high num_crossposts values) tend to score lower ratios. The community values content created for this community specifically.

11. The Distribution Playbook

Phase 1: Pre-Launch (2-4 weeks before)

1. Establish presence through education, not promotion. Share 3-5 genuinely helpful posts: infographic explaining an ML concept, a curated resource list, or a meme that demonstrates domain expertise. Target 200-500 score range to build karma and name recognition.
2. Comment on career/learning posts with specific, actionable advice. The highest-engagement threads are career AMAs and "how do I learn ML" posts. Helping people there builds trust.
3. Identify your archetype. If your product is a learning tool, plan a "Built From Scratch" or "Learning Journey" post. If it is a visualization tool, plan a "Visual ML Explainer." If it is infrastructure, plan a "Free Resource" post.
4. Understand the Rule 3 constraint. Nothing involving monetary transactions. Your post cannot include pricing, purchase links, or revenue claims. Link to GitHub or a landing page; let users discover pricing themselves.

Phase 2: Launch Day

1. Format: VIDEO for project demos (show the model/tool in action, under 60 seconds). IMAGE for educational tools (screenshot of the most impressive output). TEXT for comprehensive write-ups.
2. Flair: Use "Project" flair. It has the highest average ratio (0.98) and sets the right expectation.
3. Title: Use the "I built [thing] from scratch to [understand/solve X]" formula. Emphasize the learning motivation, not the commercial potential.
4. Content: Include a GitHub link. Mention it is free or open-source. Describe what you learned building it. Include technical details (architecture, training details, challenges).
5. Timing: Based on the data, year-period top posts were created across all times of day. There is no strong timing signal, but weekday posts appear to perform slightly better than weekend posts.

Phase 3: First 24-48 Hours

1. Respond to every technical question within 2 hours. This community values engagement. The "19 years AMA" post worked because the author answered questions for hours.
2. Accept criticism gracefully. If someone points out a flaw, acknowledge it. "Good catch -- I'll fix that" scores better than defending your approach.
3. Do not redirect to external sites for answers. Answer questions directly in comments. Link to documentation only as supplementary material.
4. Common objections and responses for this community:
   • "Is this just a wrapper around [framework]?" -- Be honest about dependencies. Explain what you built vs. what you used.
   • "Why not just use [existing tool]?" -- Explain the specific problem you were solving. Acknowledge alternatives.
   • "Did you use AI to build this?" -- If yes, be transparent. The community respects honesty about AI assistance (see the "no-magic" project post that openly credited Claude as co-author and scored 499).
   • "Where's the GitHub?" -- Always have it ready. Projects without repos score lower.
   • "How does this help me learn?" -- Frame everything in terms of educational value, not productivity.

Phase 4: Ongoing Presence

1. Follow up with iteration posts. "Built a Neural Network Visualizer" (669 score) worked as a single post, but a series ("v2 with conv layers") would build sustained engagement.
2. Participate in weekly Project Showcase Day threads. Low competition, high engagement from the core community.
3. Share learnings, not updates. "What I learned building X" posts outperform "I updated X" posts. The community wants educational content, not changelogs.
4. Cross-post to r/MachineLearning and r/datascience only if the content is research-grade. This community is forgiving of beginner-level work; those communities are not.

Score-Tier Calibration

• Free learning tools with demo videos: Realistic ceiling 600-1,200. TensorTonic (824), ml-visualized (609), MNIST visualizer (669).
• From-scratch implementations: Realistic ceiling 1,000-1,800. Depends on the constraint (assembly > C++ > JS > Python).
• Resource compilations: Realistic ceiling 1,000-1,900 if genuinely free and comprehensive.
• Career content: Realistic ceiling 800-2,000 if from an experienced practitioner.
• Memes: Realistic ceiling 1,500-3,700 if genuinely funny and ML-specific.
• Do not expect 5,000+. Only one post in the dataset exceeds 5,000, and it was a viral opinion post about Elon Musk.

Post-Publication Measurement

• 0-4 hours: If your post has <10 upvotes after 4 hours, it likely will not gain traction. Consider deleting and reposting at a different time.
• Ratio above 0.95: You are in safe territory. The community approves.
• Ratio 0.85-0.94: You have friction. Check comments for objections and address them.
• Ratio below 0.85: Something is wrong. Common causes: embedded marketing, weak methodology, gatekeeping tone.
• Comments > 50 with score < 500: You have a discussion post, not a viral post. Lean into the discussion -- these build stronger relationships than high-score, low-comment posts.

12. Applying This to Any Project

Quick-Reference Checklist

1. Is your product free or open-source? Lead with that in the title.
2. Do you have a GitHub repo ready? Link it in the post body.
3. Are you using "Project" flair?
4. Does your title follow the "I built [X] to [learn/solve Y]" formula?
5. Is your post formatted as VIDEO (demo) or IMAGE (output screenshot)?
6. Have you removed all pricing mentions and commercial language?
7. Have you prepared answers for "Why not just use [existing tool]?" and "Where's the GitHub?"
8. Have you spent at least 2 weeks being helpful in comments before your launch post?
9. Is your post focused on what you LEARNED, not what you're SELLING?
10. Are you prepared to engage with every comment for 24-48 hours?

Scenario-Based Launch Guides

If your product is free/open-source:

• Optimal launch formula: "I built [tool] from scratch to help learn [concept]. It's free and open-source" + VIDEO demo + GitHub link.
• Key risk: Being dismissed as "just another tutorial project." Differentiate with a unique constraint or novel visualization.

If your product uses one-time/lifetime pricing:

• Optimal launch formula: Do NOT mention pricing. Post as a Project flair post showcasing the educational value or technical innovation. Let users discover pricing on the website.
• Key risk: Rule 3 violation. If a mod detects commercial intent, the post gets removed. Frame everything as a learning project, not a product.

If your product uses subscription pricing:

• Optimal launch formula: This is the hardest scenario. Post about the underlying technology or the problem you solved, not the product. Share a free component (open-source library, free tier, educational blog post) that stands on its own merit.
• Key risk: "Another SaaS wrapper" reaction. The community is suspicious of subscription models in general and has zero tolerance for paid course promotion (Rule 3).

If your product was built with AI:

• Optimal launch formula: Be transparent. The "no-magic" project (499 score) explicitly credited Claude as co-author and was well-received. Frame as "I designed the architecture and used AI for implementation."
• Key risk: Being seen as "vibe-coded." The community values from-scratch understanding. If AI wrote your code and you cannot explain it, the community will call you out.

Cross-Posting Guidance

Based on existing analyses of related subreddits:

• On r/learnmachinelearning: Frame as "I built this to understand [concept]." Emphasize the learning journey.
• On r/learnpython (if your tool uses Python): Frame as "I used Python to build [ML tool]." Emphasize the Python implementation details.
• On r/webdev (if your tool has a web interface): Frame as "I built [web app] -- here's the tech stack." Post on Showoff Saturday only.
• On r/MachineLearning: Only if your work has research-level novelty. Frame as "[R] or [P] -- Novel approach to [problem]."
• On r/SideProject: Frame as "I built [product] -- here's the journey." Emphasize business context and user feedback.
• On r/LocalLLaMA (if LLM-related): Frame around performance benchmarks and local deployment. Technical depth is essential.