After reading  Gungor Ozcelebi‘s blog, Top 10 ABAP crimes, I though I would share some Wisdom from “The Zen of Python” written by Tim Peters. This is valid for any programming language or developer, especially ABAP 😳 . Also check out  Python’s PEP – 8 guideline which lays out strict coding formats and standards but the language does not enforce these. This would be a good idea for the ABAP elders to create some general consensuses or rules for programming guidelines.

Copied from https://www.python.org/dev/peps/pep-0020/

The Zen of Python by Tim Peters

    Beautiful is better than ugly.

    Explicit is better than implicit.

    Simple is better than complex.

    Complex is better than complicated.

    Flat is better than nested.

    Sparse is better than dense.

    Readability counts.

    Special cases aren’t special enough to break the rules.

    Although practicality beats purity.

    Errors should never pass silently.

    Unless explicitly silenced.

    In the face of ambiguity, refuse the temptation to guess.

    There should be one– and preferably only one –obvious way to do it.

    Although that way may not be obvious at first unless you’re Dutch.

    Now is better than never.

    Although never is often better than *right* now.

    If the implementation is hard to explain, it’s a bad idea.

    If the implementation is easy to explain, it may be a good idea.

    Namespaces are one honking great idea — let’s do more of those!



I would also like to point out that we should not be so quick to blame the fellow developers in ABAP but the rather the language. ABAP may be open source but it is proprietary. Many people in ABAP may have never worked with another language and often learn from outdated materials, bad examples, or over priced books. Another consequence of ABAP’s proprietary status is the lack of appreciation for the work, especially for contract developers. How many people do you know who develop in ABAP as a hobby or learned it just to make something cool? This may or may not even be some of the reasons SAP is offering an alternative JAVA instance (as if JAVA is a better alternative to anything). I think it is a good idea for any developer in any language to learn other technical skills/languages to get a broader appreciation for development. In any case, ABAP certainly has it’s advantages as well.

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Jason Scott

    I Agree with your comments here, although some of these statements are almost too zen-like unless you have a group of like minded programmers working together (which is rare in ABAP).

    I think the best thing that can ever be done is to is to put in place a code review system – that will typically always lead to better code. However I’m yet to ever see it instated at an ABAP development project/site.  😉

    As for SAP’s Java stack – it’s an outdated dinosaur with development and source code management tools that are highly unproductive and would make any experienced Java dev run for the hills!! Seriously.

    HANA Cloud Platform on the other hand is leading the way and you can use any good JVM language.

    I can’t wait till this  S4/HANA stuff gets out there with its HCP based extensions…  😉

    (0) 

Leave a Reply