Stop pretending studying arrow theory improves your apping

Given two functors S,T:C→B, a natural transformation τ:S→T is a function which assigns to each object c of C an arrow τ_c=τc:Sc→TC of B in such a way that every arrow f:c→c' in C yields a diagram
ﾠﾠﾠﾠﾠﾠﾠﾠﾠﾠﾠτc
c ﾠﾠ Sc---→Tc
|ﾠﾠﾠﾠﾠﾠﾠﾠ|ﾠﾠﾠﾠﾠﾠﾠ|
|fﾠﾠﾠﾠﾠSf↓ﾠﾠﾠﾠﾠ↓Tf
↓ﾠﾠﾠﾠﾠﾠﾠ|ﾠﾠτc'ﾠﾠ|
c', ﾠﾠﾠ Sc'--→Tc'

which is commutative. When this holds, we also say that τ_c=τc:Sc→Tc is natural in c. If we think of the functor S as giving a picture in B of (all the objects and arrows of) C, then a natural transformation τ is the set of arrows mapping (or, translating) the picture S to the picture T, with all squares (and parallelograms!) like that above commutative:
ﾠaﾠﾠﾠﾠﾠﾠﾠﾠﾠﾠSa----------→Ta
ﾠ|ﾠ╲fﾠﾠﾠﾠﾠﾠﾠ ﾠ|ﾠ╲Sfﾠﾠﾠﾠﾠﾠﾠﾠﾠ|ﾠ╲Tf
ﾠ|ﾠﾠﾠ↘ﾠﾠﾠﾠﾠﾠﾠ|ﾠﾠﾠ↘ﾠﾠﾠτbﾠﾠﾠ|ﾠﾠﾠ↘
ﾠ|ﾠﾠﾠﾠﾠbﾠﾠﾠﾠ ﾠ|ﾠﾠﾠﾠSb----------→Tb
ﾠ|ﾠﾠﾠ╱ﾠﾠﾠﾠﾠﾠﾠ|ﾠﾠﾠ╱ﾠﾠﾠﾠﾠﾠﾠﾠﾠ|ﾠﾠﾠ╱
↓ﾠ↙ﾠﾠﾠﾠﾠﾠ ﾠ↓↙Sgﾠﾠﾠﾠﾠﾠﾠﾠ↓ﾠ↙Tg
ﾠcﾠﾠﾠﾠﾠﾠﾠﾠﾠﾠSc----------→Tc

I prefer Haskell as imperative language even without lenses. I write quite a bit of networking/runtime system/concurrent code, so it's basically lots of IO all over the place and programs really nicely.

I think lots of people somehow get convinced that IO should be avoided at all cost, but very imperative and IO heavy coding in Haskell is really pleasant in my experience. You still get to have the type system, ADTs/pattern matching, and having first-class IO is also lovely.