I’ve noticed a trend lately with the design of new tools becoming increasingly abstract. It’s an interesting development, and I can see how it could be beneficial in many ways. However, I sometimes find myself struggling to bridge the gap between abstract concepts and their practical applications, particularly when the provided documentation or related literature also adopts this high level of abstraction.
Take, for example, the multitude of “foo bar” examples. While they do serve a purpose in illustrating theoretical concepts, I often find it challenging to translate these into real-world, production-level scenarios. Perhaps it’s just a matter of my learning style requiring more concrete examples to grasp these concepts fully.
Furthermore, when it comes to reading explanations, I can’t help but feel they’re written in a manner that might only be comprehensible to those deeply versed in nix-lang. I’m not suggesting that these resources should be simplified to the point of losing their technical integrity. Still, a balance could be struck to make them more accessible to a broader audience.