For this
article I've found plenty of interesting things, starting with the concept of
the “pointy-haired boss”, the one that doesn’t know of technology, but has some
specifications based on the popularity of a language or the standardization of the
software industry. I liked this concept principally because of the necessity of
comprehension from the technologists to the authorities, but not submitting about
the thinks that we know for sure, like the importance of the development’s
language for a project.
I’ve found
some value on the premise that the most modern programming languages slowly are
becoming more and more like Lisp, and even when it was, at first, a shocking statement,
I’ve realized that it is true. Python, for example, it tending to the simplicity
at the expressions and is starting to look like a functional based language (considering
that Python wasn’t thought for that), that doesn’t happen to be an accident, is
just a better way of making more complex problems, easier.
Talking
about the part of the averages vs the uncommon and more powerful languages, he mention’s
again about the macros and the impact of using Lisp on a practical way, not
only because it’s easier to develop for problems with a high complexity, but also
for the velocity in a business matter. The comparison was simply brutal, a
develop made in a year with C compared to the same advance in Lisp only using 3
or 4 weeks, a bet that everyone will take.
For last, I
think that the lesson went beyond this time, is not only to use Lisp or to try
it for startups or in certain situations, The lesson that I felt reading this
article was to sometimes is really worth to take risks and to do things by the
unconventional way, not to do this always, but at the times that could be reliable,
don’t stay at the “industry best practices” and go further, the reward may be
greater than you think.
No hay comentarios.:
Publicar un comentario