Should I learn Rust?

I’m learning Rust. Why?

Point made: learning different approaches, their features, and constraints opens up your mind.

Disclaimer: This blog post is a personal, subjective testimony of my motives to learn Rust, and as such YMMV. 😃

In this blog post you will find:

1. Why curiosity is a problem.
2. How the 90–25 principle differs from Pareto’s 80–20 rule.
3. Why you and I should learn a new programing language.
4. The goals I want to achieve by learning Rust.

Photo by Susan Q Yin on Unsplash

I’m a self-taught software engineer with a focus on data. 💻

I work at Tikal — a company composed of tech experts, where we provide hands-on consultancy, scaling R&D teams with cutting-edge technologies.

In my “past professional life,” I worked in finance. Investment banking, equity research, financial modeling and valuation, corporate finance, and management strategy... All this was part of my vocabulary jargon suitcase. As such, I was well aware of the 80–20 Pareto principle, since it was observed by an economist — Vilfredo Pareto — and coined by a management consultant — Joseph Moses Juran.