By Peter Raganitsch
Oh child, exactly what took place?
Yesterday we delivered a psychological tweet after reviewing a bit of (open supply) rule, that wasn’t documented well and didn’t consist of inline responses:
After that we switched far from Twitter, decided to go to rest, got up once more, together with a day that is awesome the household. Until we looked at my Twitter reactions and mentions.
Check out examples:
This discussion steered a way that is wrong partly painted a wrong photo and wasn’t the thing I had been after. I WOULD LIKE feedback. IN MY OPINION they’ve been good and vital.
Simply because some remarks are wrong or unnecessary, doesn’t suggest you shouldn’t comment after all.
The exact opposite is true: should you ever stumble across a incorrect remark in some rule, lets change it out. Lets enhance it. Lets repair it.
Regardless of how smart you think you will be. In spite of how “self explanatory” you believe your genius rule is. Remarks are vital. Commentary is there to describe the thinking behind your (crappy? ) rule to OTHER PEOPLE. They could never be because smart they might not have the same information level while you as you.
Heck, for several we realize they could maybe perhaps perhaps not be developers that are#orclAPEX all. I’ve seen Java dudes (no offense) tempering with APEX applications. Mostly we come across regular database designers, or previous Forms designers scuba scuba scuba diving into APEX. They want guidance and much more description of the “oh so code” that is smart.
Now get the individual emotions apart and do your work. Precisely! And create the absolute most code that is beautiful ever!
P.S.: I Understand, I Am Aware. Life is difficult, there is absolutely no time. No one desires to spend you for additional time. But commenting your rule isn’t additional time. (suite…)