Commenting your code is vital !

Oh boy, what happened?

Yesterday I sent an emotional tweet after reviewing a piece of (open source) code, which wasn’t documented well and didn’t include inline comments:

https://twitter.com/PeterRaganitsch/status/1208142535442522114

After that I turned away from Twitter, went to sleep, got up again, and had an awesome day with the family. Until I looked at my Twitter responses and mentions.

Here are some examples:

This discussion steered a wrong way and partly painted a wrong picture and wasn’t what I was after.
I WANT comments. I BELIEVE they are good and vital.

Just because some comments are unnecessary or wrong, doesn’t mean you shouldn’t comment at all.

The opposite is true: if you ever stumble across a wrong comment in some code, lets change it. Lets improve it. Lets fix it.

No matter how smart you think you are. No matter how “self explanatory” you think your genius code is. Comments are vital. Comments are there to explain the reasoning behind your (crappy?) code to OTHERS. They might not be as smart as you, they might not have the same information level as you.

Heck, for all we know they might not be #orclAPEX developers at all. I’ve seen Java guys (no offense) tempering with APEX applications. Mostly we see regular database developers, or former Forms developers diving into APEX. They need guidance and a bit more explanation of your “oh so smart code”.

Now get your personal feelings aside and do your job. Properly! And produce the most beautiful code, ever !

P.S.: I know, I know. Life is hard, there is no time. Nobody wants to pay you for extra time. But commenting your code is not extra time. Writing documentation about implementation details is not extra time. It is an essentialPART of software development.

If you are in a job that doesn’t give you the time to comment your code, think of a change.

Speeding up APEX Static Application and Workspace Files

A few years ago it was deemed state-of-the-art to store any kind of extra resources (images, css/js-files) directly on the webserver.

Of course this was just the best-practice, left with many who were not able to follow because of company restrictions: no access to web server, not allowed to store files, too many regulations, and so on.

Luckily APEX 5++ gave us nicely working Static Application Files and Static Workspace Files. Now everyone is using those to store extra files.

Continue reading

Streaming flat File data into Database

For my little Webserver Logfile Analysis project I had to solve the problem of how to stream data from a flat file into a relational datamodel in my target database.

Since I used NodeJS in several projects over the past years, it came to my mind at first. On a second thought and by consulting some friends another, easier, solution materialized:

Continue reading

Question: Table names singular or plural?

Yesterday I put a question on twitter, to find out what others prefer: table names using singular or plural form. I expected one or two replies, not an avalanche :-)

Continue reading

How to update a custom public theme in Oracle APEX

In the last post I showed how you can upload a custom theme to the instance repository so that all your developers can choose that theme within the create application wizard. And more importantly, subscribe that theme from the theme repository.

Now the next question is how to update that public theme so that all applications can inherit the changes. Continue reading

Creating a custom public workspace theme

The Universal Theme introduced with APEX 5 is immensly good looking and comes with a powerful Theme Roller to customize it.

With that new theme most, if not all, older themes are obsolete.

That leaves us just with a few corporate designs which can’t (or don’t want to) be replaced by the UT.

Now ideally you want your developers to use that custom theme in all applications and also subscribe to that. Continue reading