> It sounds like you're frustrated that you don't find out about existing libraries/functions/classes/tools until your code review. That seems like a reasonable

> It sounds like you're frustrated that you don't find out about existing libraries/functions/classes/tools until your code review. That seems like a reasonable concern. Maybe next time you have a project come up with a rough plan and ask a senior developer for architecture-level feedback before you start coding. I couldn't agree with this point more. When I first started, my team lead gave me a rough plan to add new features so that I wouldn't go in blind. Until I could stand without the support of others, I drafted a quick plan of action to get the task accomplish. This let my team lead know how I was planning on accomplishing the task while allowing them to point out existing code that would take care something I would have written. It seems like unnecessary overhead, but the 5 minute conversation up front saves more time down the road.