Contact us

Using Feedback to Actually Improve Your Skills

by Arif Ikhsanudin, Backend Developer

Getting feedback can feel brutal, especially when it stings. But it’s also the fastest way to grow—if you know how to use it.

Stop Taking It Personally

Hearing criticism isn’t fun. Your first reaction might be defensive or frustrated.
The key is to separate yourself from your work. Feedback isn’t about your worth—it’s about what you can improve.

  • Listen first, react later.
  • Write down the points before responding.
  • Ask clarifying questions if something isn’t clear.

This mindset turns critique from a threat into a tool.

Identify Actionable Insights

Not all feedback is useful. Some is vague, some is subjective, and some might just be opinion.
Your goal is to find what you can actually apply.

  • Highlight points that directly affect results or skills.
  • Ignore irrelevant commentary.
  • Break big suggestions into smaller, concrete actions.

Example: instead of “Your code is messy,” focus on specifics like “Refactor this function to reduce duplication.”

Track Your Progress

Feedback only works if you use it consistently. Keep a log of what you’re improving and what still trips you up.
Seeing progress motivates you and reveals patterns in your weaknesses.

  • Maintain a personal journal or spreadsheet.
  • Review past feedback before starting new projects.
  • Celebrate small improvements—they compound.

Ask for Feedback Strategically

Waiting for someone to volunteer feedback rarely works. Be proactive, but thoughtful.

  • Request input from people experienced in the skill you’re developing.
  • Ask specific questions: “Does this function meet performance standards?” instead of “Is this okay?”
  • Use peer reviews, mentors, or online communities.

Make Feedback a Habit, Not a One-Off

Skill improvement is a marathon, not a sprint. Treat feedback as part of your routine, not a crisis.
Every project, every review, every bug report is an opportunity to refine your craft.

Remember: growth comes from consistently applying feedback, not just receiving it.
Master the art of using critique, and you’ll level up faster than you imagined.

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

Mocking in Spring Boot Tests: When It Helps and When It Hurts

Mocking is the most overused tool in the Spring Boot testing toolkit. Used well, it isolates units and speeds up suites. Used carelessly, it builds a test suite that passes confidently while your application fails in production.

Read more

The Financial Reality of Being an Independent Contractor

“Wait… that’s your hourly rate?” Yes. No, that’s not take-home pay.

Read more

Merge Conflicts Are Not Git's Fault. Here Is What Actually Causes Them.

Merge conflicts are a symptom of parallel work on the same lines of code. Understanding exactly how Git identifies conflicts — and what causes them — changes how you structure work to avoid them.

Read more

Stop Running Your App as Root Inside Docker

Running container processes as root is the default, and it's a security problem that's trivial to fix. If your container is ever compromised, root inside the container is far more dangerous than it needs to be.

Read more