I want to become a Haskell developer.

Last year, during my unemployment, I cracked open Haskell
Programming from First Principles and read through all 1200
plus pages. I did every exercise, made Anki flashcards of
every quirk of the language. And after about 2 and a half
months of going at it – I claimed victory.

Then I stowed it away. Because I was a new engineer in an
unknown country and my financial situation was getting
increasingly dire and I knew I had to find a job as soon as
that passport came through from Ireland – fast. I wouldn’t
have time to fritter away on longshots. So I
resorted the
little text file of technologies I wanted to dive deep on,
with “better” being “more immediately useful in a job
search”. And then I started executing.

My approach to learning new technologies is always the same:
Start with reading a book on it. Take notes. Then build
something nontrivial with it. I read the first 5 chapters of
The Definitive Guide to SQLite; then I used it to help
build a custom Anki deck for
Finnish.
I read Django for Beginners and learned building websites
with actual databases was actually a lot of fun – and that
I could use my knowledge of SQLite to help me out a ton
there. I built myself a few basic websites, all for personal
use. I read a hundred or so pages of The Kubernetes Book,
and later The Docker Book, and I built myself a few
Dockerized REST servers using Django and SQLite. And, at
long last, I finally got my passport, and got cleared to
work in Finland, and got a job o