What do you do if your computer engineering mistakes are hindering your skill improvement?

One thing I say from experience is that mistakes are part of work, but what you learn from it and assess the situation, why it happened and how to protect from recurring similar one. What kind of additional check points to be added for existing processes for the team is the key. Most critical thing is not repeat same mistakes, that's a red flag.

In my experience acknowledging the error and trying to seek for help is more helpful than rebuilding the solution especially if you know what is happening and asking someone experienced

Always ask for feedback even you have no mistakes, feedbacks always improves your thinking towars the required target. A feedback from a senior or project coordinator is appreciated mor than for example your colleagues.

Getting constructive feedback is very important to grow for any individual. Sometimes, it's challenging to get one. If anyone gives feedback, first thing is to appreciate them for taking time to give feedback and then focus on what can you infer from it. Focus on technical part and don't get emotional, deal with it as professional as you can which will help you long way to grow as a person.

Mistakes are a normal part of engineering work, especially in many computer engineering tasks when we are expected to move fast and break things. But if you are not learning from past mistakes, it may be due to a misunderstanding of fundamentals. Stepping back and reviewing the problem from a first principles approach can provide you the space to really look at the problem and gain new insights, at the same time it will solidify your understanding of the basics.

If you see mistakes repeating in same area or subject, it's the time to step back and start reviewing your way of thinking or return back to basics. While that, you could also follow beginner tutorials which for certain you will find something new or something you know already but you don't use it or forgot about it.

In my experience, this is the most under practiced aspect as large young engineers are always focused on solving problems to meet deadlines. Very few are process oriented and I suggest anyone to put a method that's comfortably to you on checks and balances. If something goes off track, take feedback and update your checks. Over few iterations, the process will become rock solid and can't go wrong.

Absolutely, be open minded and always look out for challenging situations. Yes, it feels like lot of load initially. But the amount of learning you gain from finding solutions are enormous and helps you over long run.