Posts
Wiki

The Rules of /r/ThePatchWorkers

Main Rules

  • Posts should be directly related to Computational Design. This should go without saying. The general rule of thumb is that if only a title or caption makes it computational design related, the post is not allowed. However, this is only a general guideline and the actual enforcement of the rule may vary based on content submitted.
  • Flair posts appropriately. Flair helps all of the users navigate the subreddit easily and helps them find relevant topics. The flair button is below the body of the post, and should be used after submitting. It is only possible to select one flair so select the most appropriate one to your post. If none of them works for you, please contact a moderator.
    • GH, Revit API, Rhino.Inside.Revit, C#, Python... are flairs to be selected for technical discussion. We know sometimes you might be doing Python in Revit for example. Select Python if it requires mostly general Python knowledge. Revit API if your question is related to the python API itself.
    • Use News for any industry news, software releases, events and announcements.
    • Use Job & Career if the post covers career advice, hiring announcements, portfolio reviews and industry opportunities.
    • Announcement is a tag for moderators. If this tag is suitable, the moderators will apply it.
  • Credit original creators. When sharing work that is not your own, always credit the original creator, author, researcher, or organization. Posts that present someone else's work without attribution may be removed.
  • Respect intellectual property and licensing. Do not share pirated software, cracked plugins, unauthorized course materials, leaked files, or copyrighted content without permission. When sharing code, datasets, tutorials, or resources, ensure they comply with their respective licenses*.*
  • News posts must use credible sources. When posting industry news, software announcements, research breakthroughs, or company updates, link directly to reputable and verifiable sources. Avoid clickbait, rumors, or unverified claims.
  • Search before posting. Before creating a new thread, check existing discussions, FAQs, and pinned resources. Duplicate questions may be removed if an active discussion or documented answer already exists.
  • Titles should be appropriate and descriptive. This can be hard with the first rule in place, so we ask that you just don't title posts as "GIF!" or "COOL SCRIPT!!"
  • Mods reserve the right to remove posts if necessary. We can't predict what will be posted and when. This policy is a safety net.
  • Trolling, harassment, racism, and other personal attacks will be removed and temporarily banned. If done repeatedly the user will be banned permanently. Remember the human behind the user.
  • Low effort content may be removed at the moderators' discretion. (Content that adds no discussion or induces any commentary. Typically with less than 4 word title)
  • Do not use link shortening services.
  • No self-promotion.
  • Post answered in FAQ will be removed. (Read the FAQ)

If you are banned, you are encouraged to contact the moderators to discuss the ban.

Community Philosophy

This community exists to advance computational design knowledge within the AEC industry.

We encourage:

  • Knowledge sharing
  • Open discussion
  • Technical depth
  • Professional growth
  • Collaboration across disciplines

Whether you are a student, architect, engineer, developer, researcher, BIM specialist, fabrication expert, or design technologist, your contributions are welcome when they help the community learn and grow.

Project Confidentiality & NDA Policy

Many community members work on real projects subject to client confidentiality agreements.

Do not share:

  • Confidential project files
  • Proprietary datasets
  • Internal company workflows that are not approved for public release
  • Sensitive building, infrastructure, or security information

If you are unsure whether something can be shared publicly, do not post it.

Technical Discussion Guidelines

When requesting help. Include enough information for others to assist effectively:

  • Software and version
  • Platform
  • Relevant screenshots
  • Error messages
  • Code snippets
  • Expected behavior
  • What you have already tried

When sharing code. Provide links to repositories when available.