No, it makes you a more dissatisfied programmer.
Dissatisfied with how poor the tools in other ecosystems are.
You can't take Haskell with you. Erik Meijer is wrong about this. You can't use monads productively in Python. You can try, but it doesn't work well.
You need Haskell. Laziness, FP, immutability, types, the whole shebang. It all hangs together in a well designed way. Not even Scala can do FP well.
https://twitter.com/bitemyapp/status/534498324296921088
https://twitter.com/bitemyapp/status/534498480430284801
https://twitter.com/bitemyapp/status/534498423870066688
https://twitter.com/bitemyapp/status/534498512398864384
https://twitter.com/bitemyapp/status/534500037901176832
To quote mwotton:
"here is a lightsaber, an elegant and powerful weapon. After you practice with this, you will be much better at stick-poking." is absurd.
More powerful abstractions tend to invalidate more and more combinations of terms. This means the space in which your program will be correct gets narrower and narrower.
The good news is, it means your abstractions will more precisely represent the correct program you want.
The bad news is, you'll want help from the computer and a well-designed language.
I have a video of my Haskell workflow here: https://www.youtube.com/watch?v=Li6oaO8x2VY
It's worth considering in this context what Haskellers mean when they talk about "type tetris".