The author
Hello!
Nice to see you, and I'm glad you found your way here! I have an M.Sc in mechanical engineering, but for some reason I really like to code. I didn't have much programming experience when I started university — while studying mechanical engineering, I took just one programming course: Introduction to Programming, basically an intro to Python. I didn't really shine in that course and honestly kind of hated programming back then. But during my studies I came to realize that if I wanted to do serious scientific calculations, I needed to know how to write code. So I decided the only way to learn was to read on my own and rely on Google. Since then, I've grown to love programming and now do a lot of coding both at work and in personal projects.
Once I started learning on my own, my path was pretty typical. First Python: the basics — lists, strings, functions, classes. At that point I thought: "This is nice, programming is easy." Then I started learning C++ and realized that was a lie. Compilers, templates, pointers, memory allocations... I pushed through and decided to try C next. It can't get any worse, right? But it was worth it. Since then I've worked with Java, Julia, JavaScript, and tried out a dozen more. Along the way I even stumbled into systems engineering, networking, distributed systems, and many other areas of software engineering.
So why am I writing this blog? I've used Google as my go-to tool for code snippets, error messages, and examples for years. Finding code for general programming problems is usually straightforward, but when it comes to finding clear examples of how to implement specific mathematical formulas or algorithms, that's a different story. Since my background is in mechanical engineering rather than software engineering, I thought I could contribute by writing posts on various mathematical models and their implementations.