A developer takes out "insurance" when they write code to "make sure" or "just in case". This can be unnecessary & unproductive. See examples.
Read moreAnton and Hayden take you through how to get APEX to tell you which item has been changed to make sure you're saving what you should.
Read moreMonty and Michelle chat with Brad Cardinal, Chief Technology Officer at Clay Lacy Aviation about how APEX allows their applications to take flight.
Read morePL/SQL packages are great! But there is one package feature you shouldn’t use: Initialization. Your first inclination should be to avoid it. Steven Feuerstein explains why.
Read moreJorge Rimblas, the master of Oracle APEX Classic Reports, shows us how to use a variety of template options to turn a classic report into a Alert Region that provides a useful confirmation message.
Read moreThe Automatic Time Zone setting in APEX presents some significant challenges. Anton adresses the issues by bypassing this feature with an implementation of his own.
Read moreScott Spendolini joins Monty and Michelle to chat about his amazing journey of the past year, heading an Oracle COVID19 app dev team
Read moreSteven discusses when it makes sense to choose a string-indexed associative array (one of the three types of PL/SQL collections)
Read moreWith declarative support built into Oracle APEX, markdown ensures a consistent look and feel, and removes cross-site scripting vulnerabilities.
Read moreLazy can be a good developer characteristic or a terrible one depending on how and when applied. Steven and Marlyn look at examples of each.
Read more
Recent Comments