Given a philosophy that says your top hackers should be creating DSLs that facilitate dev in the problem space, this might be common at companies in well-define

Given a philosophy that says your top hackers should be creating DSLs that facilitate dev in the problem space, this might be common at companies in well-defined problem spaces. So, it might be quite exciting to dive into. If you are well-versed in maybe three programming paradigms (imperative, logical, functional?), you should probably be able to pretty quickly make some good guesses about how the code works and what it does. But, and it is a big but - are you looking at a position that puts you in place to work with (and learn from) the top hackers or are you going to be just another drone in a large faceless organization? These are continuums in reality, but I think you need to take care that you don't become pigeon-holed in your hacking career. So while I'd try hard to really dive into the test language, I might have a much harder time deciding about accepting an offer or not (ignoring other aspects that would of course affect any job decision).