The challenge pot for the RLadies+ community — a weekly R challenge to give folks a low-stakes, friendly reason to write a bit of R and learn from each other.
Each week, Jinx posts a small R challenge to the community Slack, tagged with a difficulty:
- 🟢 Novice — beginner-friendly, one concept
- 🟡 Adept — comfortable with R, combine a few ideas
- 🔴 Oracle — experienced, non-trivial logic or idioms
You have a go, react ✅ if you cracked it or 🤔 if you're still stewing, and share your solution in the thread. That's it. Learn something, teach something, have a bit of fun.
Every challenge — whether a community member submitted it or Jinx drafted it — lives here as an issue and gets a human's thumbs-up before it goes out. Nothing reaches the community unreviewed.
- 🧑🍳 Submit a challenge — open the challenge form. Have a puzzle you'd love others to try? Brew it up. Start with the guidelines.
- 🧑⚖️ Help review — challenges arrive as
status: proposedissues. Skim one, check it's clear and fair, and approve it or suggest a tweak. It's genuinely light, and no R wizardry required. Want in? Say hi in an issue or ping us in the community Slack. - 📜 Help shape the rules — the guidelines are a first draft and meant to grow. Ideas on scope, difficulty, or fairness are very welcome.
See docs/architecture.md for the lifecycle of a challenge and how Jinx drafts, verifies, and posts them.
Part of the RLadies+ tooling family, alongside Jinx. Still early — help us shape it.