>> Any thoughts/recommendations on how to get started in the software development side of things coming from a mechanical engineering background?

That's an interesting question. I know a guy who was (is) an ME. He worked in the auto industry calibrating ABS and traction control systems. That's an area where torques/forces/dynamics are required, but no real software background. He would either come up with new ideas, or try to track down bugs in the algorithms - he had access to the code since we were all at the same company. He moved on to fixing problems (the software team had a lot of things to do so weren't as responsive as he wanted?) and even implementing features. When I met him he was a solid embedded software engineer and I was a bit surprised to hear his path to get there.

So I guess find some niche that has overlap between what you know and what you want to do. Then gradually leverage that as you improve (and prove to others) your capability in the "other" area. How you find that overlap is up to you. For one guy it meant calibrating stability control systems was the start.

I've come to think the most flexible place to branch out from is product testing or manufacturing. You can learn a lot about a lot of different aspects of things there. Just don't let yourself stagnate.

I have a BS & MS in Mechanical Engineering, but I have spent the last 15+ years in Software. I first got my start learning to code on the side, but eventually made my way into Product Management. I would look for software engineering companies in the ME space think CAD, PLM, FEA type software companies and look for jobs in PM or even customer success and pre-sales engineering. Some of the best PM's that I've hired come from the customer success groups.

Robotics. I work at a robotics company. A lot of our folks are Mech E turned SWE. I myself am a SWE, but the amount of knowledge of forces, torque, controls, etc. I have had to pick up is huge.

Read up on Walter Bright