Keep learning everything you possibly can. Start with the skills you use most at work and start improving them. As you do this try and be self aware about where your own faults are. Keep making a fool of yourself in meetings? Maybe your communication skills should be worked on next. In the absence of feedback remember this: if you were doing an absolutely horrible job there would have been feedback. You can also talk to your co-workers and see if they have suggestions for you.

Context: I'm a Sr. Software Engineer, and I am currently fighting with management to get them to understand we have two bad devs on our team. This is exactly the right way to judge a developer, you just have to keep in mind that you need to grade all of these on a curve. There will always be bugs, but too many bugs is a problem. There will always be things that take longer than expected, but if it becomes a pattern with one dev you need to look closer. There will always be things you discover that slow down your progress, but if someone has been saying "I'm almost done" for two weeks you need to investigate. Sometimes it is better and faster to teach/explain something, but if one dev keeps taking away other dev's time to have things explained to them then there may be an issue. You can't be productive 100% of the time without getting burnt out, but you shouldn't be wasting time 90% of the time either. There is a balance there. If you are the manager and can't judge some of these things, find someone you can trust. Maybe the person you can trust is on your team, maybe you have to pull in someone else and ask a favor. Ultimately, a good developer is going to want to do good work with as little headaches due to bad devs as possible and ought to be willing to help you out.