Close

What an Oracle Developer Ought to Know

The title of this series may sound presumptuous; but please, allow me to elaborate. Whether coding an application in vb, c#, java, R, python, or any other language/platform there is a good chance at some point you’ll be talking to an Oracle database to get to your business information.  Like any technology though, there are good ways and bad ways to use that database. Unfortunately, a great many people don’t know how and resort to whatever crude techniques they happen across first to solve their problem.  Oracle is big, and everybody has to start somewhere so it’s entirely reasonable that early attempts may be sub-optimal.  The obvious question then is “What should be the next steps?  What should a new developer work on to get up to speed more quickly?”

From my own early struggles, to helping developers where I work, to answering several thousand questions in online forums I’ve noticed patterns of confusion. Questions and problems that surface over and over again, regardless of the industry, country, or platforms involved. To me, this repetition indicated fundamental skills of Oracle development. So, my claim is not merely an opinion of what I think developers should know; but rather a distillation of the questions developers did need to know to do their jobs.

This blog series is a based on a talk of the same name I’ve presented multiple times at the Collaborate and KScope conferences as well as to small developer groups. Using the article format will allow me to extend more into each of the topics that were covered quickly and narrowly within a 1-hour speaking format.

Content links under construction.