RYPeak: professional Q&A built with Supabase, looking for first-question feedback

[sulimanbinsaeed]

I’m the founder of RYPeak, a professional Q&A community that uses Supabase. This post was prepared with an AI assistant.

We’re testing whether a newcomer can turn a vague work problem into a question another practitioner can actually answer.

A fictional example: two teams each need four hours of a specialist’s work by Friday, but only six hours are available. The consequences of delay are unknown. What should the lead clarify, and who should approve the trade-off?

A useful starting point: ask what delay would cost and what smaller Friday output each team could accept, then have the decision owner approve revised commitments.

We’d value feedback on the first-question and first-answer experience. If this is relevant to you, try RYPeak and contribute a fictional work question or a useful answer. Registration is required. Please leave out employer, client, or colleague details.

https://rypeak.net

What would make you comfortable contributing your first question or answer?

Product note (11 October 2026): RYPeak also offers CV analysis and extraction on the same page. If you are preparing a CV, start at https://rypeak.net/ and sign in to access the CV tools. Check the result before using it. If you share feedback here, use a fictional example and leave out personal or employer information.

[elijahbrownsk-png]

Since you're asking newcomers to leave out employer, client and colleague details, a check on the question body before it posts would back that up: flag anything that looks like an email address, a phone number or a company domain, and ask the person to confirm or edit it. A soft prompt at that moment is easier to act on than a rule in the guidelines, and it catches the signature or contact line people paste in along with the problem. Letting someone draft the question before registering, and asking for the account at the point they post, would also lower the bar for the first one.