this post was submitted on 22 Oct 2023
61 points (94.2% liked)
ADHD
9661 readers
29 users here now
A casual community for people with ADHD
Values:
Acceptance, Openness, Understanding, Equality, Reciprocity.
Rules:
- No abusive, derogatory, or offensive post/comments.
- No porn, gore, spam, or advertisements allowed.
- Do not request for donations.
- Do not link to other social media or paywalled content.
- Do not gatekeep or diagnose.
- Mark NSFW content accordingly.
- No racism, homophobia, sexism, ableism, or ageism.
- Respectful venting, including dealing with oppressive neurotypical culture, is okay.
- Discussing other neurological problems like autism, anxiety, ptsd, and brain injury are allowed.
- Discussions regarding medication are allowed as long as you are describing your own situation and not telling others what to do (only qualified medical practitioners can prescribe medication).
Encouraged:
- Funny memes.
- Welcoming and accepting attitudes.
- Questions on confusing situations.
- Seeking and sharing support.
- Engagement in our values.
Relevant Lemmy communities:
Autism
ADHD Memes
Bipolar Disorder
Therapy
Mental Health
Neurodivergent Life Hacks
lemmy.world/c/adhd will happily promote other ND communities as long as said communities demonstrate that they share our values.
founded 1 year ago
MODERATORS
Is this in a software context? If so, mandating structured RFCs will help a lot. It will channel random streams of thoughts into constructive, actionable proposals.
Have your first RFC be about how to structure an RFC. Make a cost/benefit analysis (in real money if possible) be a mandatory part of the proposal. Commit all of them to a main branch in git even if they are rejected because you would preserve the original discussions around that particular proposal.
Basically anything that can be an epic ticket can and should be an RFC first.
Thanks, good advice. The context is technology. I'm on the tech side. The other person is outside of tech ("the business").