Contact us

Getting Feedback That Helps Instead of Confuses You

by Arif Ikhsanudin, Backend Developer

Feedback can be a goldmine—or a maze of contradictions.
Here’s how to make sure what you hear actually moves you forward.

Know What You’re Looking For

Before asking for feedback, define your goal.

  • Are you improving a feature, polishing a design, or refining communication?
  • Specific questions get specific answers.
  • Avoid vague requests like “What do you think?”—it often leads to mixed signals.

Key: Clarity upfront saves hours untangling confusing advice later.

Choose the Right People

Not everyone’s feedback is equally useful.

  • Ask people with experience in your domain or direct knowledge of the project.
  • Balance perspectives: some can critique details, others can focus on bigger picture.
  • Avoid soliciting feedback from people who aren’t invested—it usually adds noise.

Tip: Quality over quantity beats a flood of contradictory opinions.

Ask for Actionable Input

Feedback is only useful if you know what to do next.

  • Request concrete suggestions, not just opinions.
  • Questions like “Which part is unclear?” or “What would improve this flow?” are gold.
  • If someone says “It’s confusing,” follow up with why and how to fix it.

Pro insight: Actionable feedback is like a map, not a riddle.

Process, Don’t React

It’s easy to feel defensive when feedback stings.

  • Take time to digest before responding.
  • Look for patterns: repeated points are usually important.
  • Separate emotional reaction from practical advice.

Remember: Feedback is a tool, not a personal critique.

Implement and Reflect

Finally, act on the feedback and evaluate the impact.

  • Make changes incrementally to see what truly improves the outcome.
  • Reflect on which feedback helped most and why.
  • Over time, you’ll get better at filtering the useful from the confusing.

Closing line: Smart feedback isn’t about pleasing everyone—it’s about turning insight into progress, one clear, actionable step at a time.

Scale Your Backend - Need an Experienced Backend Developer?

We provide backend engineers who join your team as contractors to help build, improve, and scale your backend systems.

We focus on clean backend design, clear documentation, and systems that remain reliable as products grow. Our goal is to strengthen your team and deliver backend systems that are easy to operate and maintain.

We work from our own development environments and support teams across US, EU, and APAC timezones. Our workflow emphasizes documentation and asynchronous collaboration to keep development efficient and focused.

  • Production Backend Experience. Experience building and maintaining backend systems, APIs, and databases used in production.
  • Scalable Architecture. Design backend systems that stay reliable as your product and traffic grow.
  • Contractor Friendly. Flexible engagement for short projects, long-term support, or extra help during releases.
  • Focus on Backend Reliability. Improve API performance, database stability, and overall backend reliability.
  • Documentation-Driven Development. Development guided by clear documentation so teams stay aligned and work efficiently.
  • Domain-Driven Design. Design backend systems around real business processes and product needs.

Tell us about your project

Say Hej

Our offices

  • Copenhagen
    1 Carlsberg Gate
    1260, København, Denmark
  • Magelang
    12 Jalan Bligo
    56485, Magelang, Indonesia

More articles

Sharding Your Database Sounds Exciting Until You Actually Have to Do It

Database sharding is one of the most operationally complex decisions in backend engineering. Understanding what it actually involves — and what you give up — should make you reach for every other option first.

Read more

Questions to Ask Before Starting a Backend Project

“We just need an API… should be quick, right?” That sentence has started more fragile backend systems than anyone admits.

Read more

Depends On in Docker Compose Does Not Mean What You Think It Means

depends_on controls container start order, not service readiness. Without health checks and explicit conditions, your app container starts before its dependencies are ready to accept connections — and your logs are full of startup errors that disappear on the second attempt.

Read more

Java Generics Beyond `List<T>` — Wildcards, Bounds, and When They Actually Matter

Most Java developers use generics as glorified type-safe containers and stop there. Wildcards and bounds solve real API design problems — here is what they are, when they help, and when they make things worse.

Read more