About489 words. Time to Read: About 4 minutes.
My name is Ryan Palo. I’m a mechanical engineer, currently living in the Oakland, CA area. I’ve specifically got a focus on mold tool design, design for manufacturability/moldability, and turbomachinery. A lot of my turbomachinery calculations have been supported by Python scripts to optimize designs.
I’m creating this blog to keep track of all of the things I’m learning about. In the past couple of years or so, I’ve started to learn a lot about different aspects of software and programming. I want to be able to track my progress and feel accomplished in a year instead of feeling like a failure when I look up and still see how much there is that I don’t know. My goal is to at least post something every two weeks. Hopefully I can even improve on that. I’ll write about what I am currently learning, what is interesting to me, and try to explain the things that I’m learning to cement that knowledge. Probably, this won’t be interesting to anybody but me, but that’s ok.
This will also be a good way to exercise my writing muscle, and get more practice and fluency with Markdown, Git, Jekyll, and the various other components that are coming together to make this happen.
I love getting feedback and hearing from other people of different skill/experience levels in the community. I want to hear what you think, so please shoot me an email or message me on any of the available social medias… medii?.. median? Moods? Whatever.
You can see some of my projects on GitHub .
My DM’s are open, so probably the fastest and easiest way to provide quick feedback or ask me a question (about anything!) is on Twitter .
I cross-post most of my articles on Dev.to as well. It’s really a great community, and I can’t recommend it enough for people of any skill/interest level.
I’m also a contributor to Simple Programmer .
I’ve never really gotten much use out of it, but I keep my LinkedIn account up to date, and you can see how cool I am there.
You can also email me at firstname.lastname@example.org or email@example.com.