Revenge of the nerds (Commentary)

IT industry problems almost always start with a classic case of "blind leading the blind", specially when testing new features. Inspiration is not something very valued by IT companies these days (unless you're thinking of companies of gargantuan size, or teeny tiny forgetable startups), the boss will always go for whatever is safest, and "safest" in most cases translates to "cheapest". Every once in a while, the boss will think to themselves "Hey, look, <hip programming platform here> <version number here> is out, let's all move our processes to that.", without really knowing what <hip programming platform here> truely is or what <version number here> implements.

There are so many other options beside what's "hip" or "standarized" that can do a better job at not crashing everything within a company's system, and were actually built for those specific task you're trying so desperately to write out in Java (oh, crap, what are you doing?). Take for instance LISP, there's only so many ways one can nail down a nail, you don't need a mechanical drill, or a hydraulic press, you don't even need a hammer (if you're brave enough). So, why try to over complicate things?

One of the few things I've come to cherish about LISP is it's elegant no-nonsense design thought for the solution of simple one-way problems, and it can also be used for a world of complex tasks for a swift, easily manageable and maintainable solution. It is said that most modern programming languages are created with LISP simmilarities in mind, and, though I cannot find any actual true simmilarities between Python and LISP (for Python is not mind-numbingly complicated), I agree that this shift is not necessarily a bad thing.

Unless you make me (write (like this)).