I like the responses above. As a high-technology management consultant, not sure why you would be trying to impress 'hard core coders.' If you're applying for a product manager position, you should be communicating examples of the value you have created with technology to the hiring managers (HR, consultants, business development managers) who are looking for valuable team members. What you're describing, by pulling different tools and technologies together to create solutions, could be a sign of understanding and creativity around system architecture, but the actual tools you're using likely would not apply to the more robust systems that many companies that you'd want to work for would use when building innovation or managing product lifecycle processes.
Demonstrating that you can learn foreign tools and you've been using what you have at your disposal could be valuable for your story -- but backing that story up with an understanding of the leading systems being adopted for architecture or digital product capability is likely more relevant to joining a team. Truth be told, many great developers aren't aware of all of the functionalities of the tools that a company introduces to them for product innovation, but their ability to understand, learn, and quickly adapt to the systems, so much so that they can alter the process through new functionality aligned to business results, is what makes their 'code' skill valuable to the team and company. Product managers may take a higher view of the process, but need to be able to communicate effectively with all members of the team -- including developers -- to drive client and business outcomes. From data layers, to architecture integrations and functionalities, if you've got a great dev staff and can work effectively with them, you'll be able to ask questions and learn about the systems native to the company's product process. However, popular platforms and systems for different industries are worth knowing. Having a firm understanding of SCRUM, the process developers go through to build new capabilities, emerging digital product tools, and having the personality qualities of a manager who expresses genuine appreciation and acknowledgement to those who know things you don't, won't hurt your case. Overall, there are certainly many ways product managers combine technical intellect and people awareness to create value for a team or project. While learning code can't hurt you (unless time is a major factor), having a real understanding of the big systems that govern product development (or specific systems and tools that a company you love uses in their architecture) is likely a good next step for skill building and preparation.