Perception is key, I wouldn't air your own dirty laundry. We all make mistakes as SWE. As a lead developer there are times I see mistakes that a Sr. or Jr. ma

Perception is key, I wouldn't air your own dirty laundry. We all make mistakes as SWE. As a lead developer there are times I see mistakes that a Sr. or Jr. makes and it reveals the limits of their knowledge and skills. This is concerning, as you lose trust in that developer and this affects what tasks you are willing to assign to them. Which makes them less valuable to the team. Causes you to spend more time reviewing their PRs. These 'costs' do lose the company money through lost productivity. It sounds like you're new to a code base and lang so take some extra time to learn and investigate as you're working on a task. Be curious, explore and learn. Review your code before you setup a PR. Test your code locally. Does it meet all the requirements. Are tests passing. Did I add enough tests? Could I bulletproof it further? Are there any areas we could improve performance or make other improvements I could recommend as a future card/task to my mgr? Every team has different levels of SWEs regardless of title or even experience. So not everyone is going to perform as well as everyone else. You just want to make sure you're not at the bottom. Be curious, keep learning, be positive, get tasks completed and working properly and you'll be fine. (edit) definitely own your mistakes, we all make them, make sure they are a learning experience.