또 다른 사이드 프로젝트를 만들었습니다. 하지만 이번에는 '좋아 보인다' 는 피드백 대신 솔직한 피드백을 주고 싶었어요.
I built another side project. But this time, I wanted honest feedback instead of "Looks good."
사이드 프로젝트를 구축하는 것은 흥미진진합니다.
핵심 요약
자동 요약- 1사이드 프로젝트를 구축하는 것은 흥미진진합니다.
- 2코딩을 하고, 버그를 수정하고, UI를 개선하고, 기능을 추가하는 데 밤을 보냈습니다.
- 3마지막으로, 누군가와 공유하고 다음과 같이 질문합니다.
원문 본문
출처 · dev.toBuilding a side project is exciting.
You spend nights coding, fixing bugs, improving the UI, and adding features.
Finally, you share it with someone and ask:
"What do you think?"
The answer?
"Looks good!"
And that's it.
No details. No suggestions. Nothing you can actually improve.
I've experienced this myself.
The problem isn't that people don't want to help.
Sometimes, we're just asking the wrong questions.
Instead of asking someone to review an entire product, what if we asked them just ONE specific question?
For example:
- Is it clear what my product actually does?
- Would you understand how to use this feature?
- What would stop you from trying this?
- What's the first thing you'd improve? That's the idea behind Critique, a project I've been building.
It's a free platform where builders can:
- Share something they've built.
- Ask one focused question.
- Get honest feedback from real people.
- Help other builders by sharing their own feedback. No AI-generated responses. No generic feedback scores pretending to understand your product.
Just people helping people build better things.
Try it here: https://critique.page
And here's something I'd genuinely appreciate:
If you try Critique, don't just submit your own project. Take a moment to help another builder too.
That's how I want this community to grow.
I'd love to hear from other developers:
What's the most useless feedback you've ever received about a project you built?
And what kind of feedback do you actually wish people would give you?
I'm reading the replies.
이 글은 dev.to 의 원문을 정제해 보여드립니다. 저작권은 원저작자에게 있습니다.
전체 내용이 궁금하다면
dev.to 원문에서 이어 읽기





