Skip to main content

Nine Years at the Oracle Dev Gym

Waaaaay back in 2010, on April 8 to be specific, I started a website called the PL/SQL Challenge. It featured a daily PL/SQL quiz (yes, that's right - a new quiz every weekday!) and gave Oracle Database developers a way to both deepen and demonstrate their expertise. Players were ranked and competed for top honors in our annual championships.

Not quite as waaaaay back, in 2014, I rejoined Oracle Corporation after 22 years away (from the company, not from the technology). The PL/SQL Challenge came with me, and a year later we rebranded it as the Oracle Dev Gym.

Today, we offer quizzes on SQL, PL/SQL, database design, logic, Java and Application Express. We've added workouts and classes.

Yesterday we celebrated the ninth anniversary of the Dev Gym / PL/SQL Challenge. And my oh my but Oracle Database developers have been busy!


Here are some stats from those nine years:
  • Almost 35,000 developers and DBAs have taken quizzes on the site, a total of 1.27M answers submitted.
  • They spent a total of over 118 YEARS of their cumulative time taking quizzes, workouts and classes.
  • Their average grade on quizzes is 75% (we have a lot of tough quizzes!).
  • Roughly 3,500 developers have been active on the site in the last three months.
  • We've had almost 35,000 sign-ups for our Dev Gym classes (the most popular being Chris Saxon's Databases for Developers classes).
  • Individual workouts have also been very popular, with just under 33,000 taken.
I'd also like to give a shout-out and big thanks to the following major contributors to the success of the Dev Gym:

  • Kim Berg Hansen, SQL quizmaster, author of hundreds of amazing SQL quizzes
  • Chris Saxon, Database Design quizmaster, creator of Databases for Developers class series
  • Rafael del Nero, Java quizmaster (new to 2018!), and Java Champion
  • Eli Feuerstein, our lead APEX developer
  • Elic (Vitaliy Lyanchevskiy), our ace database quiz reviewer, who has had an enormous positive impact on our quiz quality
  • Livo Curzola, our logic quiz reviewer, for his long and careful career checking over Eli's quizzes

The Dev Gym has become an essential part of the learning experience for thousands of developers. They've discovered new features of the database, learned from other developers, and even written their own quizzes for everyone to play.

If you haven't yet tried the Dev Gym, come check it out! Take a quiz, sign up for a class (they are on-demand, take them at your own pace) or take a workout. 



Comments

  1. Number 1 in this week's logic quiz.
    Does it get any better than that?
    (obviously not!)

    ReplyDelete

Post a Comment

Popular posts from this blog

Three tips for getting started right with Oracle Database development

By "Oracle Database development", I mean, more or less, writing SQL and PL/SQL. I assume in this post that you have access to Oracle Database (which you can get via Cloud services, Docker , GitHub and OTN ). A. Use a powerful IDE, designed with database programming in mind. There are lots of editors out there, and many IDEs that work with Oracle Database. Sure, you could use Notepad, but OMG the productivity loss. You could also use a popular editor like Sublime, and then it get it working with Oracle. I suggest, however, that you  download  and install Oracle's own own, free, powerful IDE: SQL Developer . If you like to complement your graphical IDE with a command line tool (or OMG if you actually prefer  a command line tool to a graphical interface), you should also check out the relatively new and generating-lots-of-excitement SQLcl . B. Enable compile-time warnings and PL/Scope. The database has tons of useful functionality burned right into it, ready for...

Why DBMS_OUTPUT.PUT_LINE should not be in your application code

A database developer recently came across my  Bulletproof PL/SQL  presentation, which includes this slide. That first item in the list caught his attention: Never put calls to DBMS_OUTPUT.PUT_LINE in your application code. So he sent me an email asking why I would say that. Well, I suppose that is the problem with publishing slide decks. All the explanatory verbiage is missing. I suppose maybe I should do a video. :-) But in the meantime, allow me to explain. First, what does DBMS_OUTPUT.PUT_LINE do? It writes text out to a buffer, and when your current PL/SQL block terminates, the buffer is displayed on your screen. [Note: there can be more to it than that. For example, you could in your own code call DBMS_OUTPUT.GET_LINE(S) to get the contents of the buffer and do something with it, but I will keep things simple right now.] Second, if I am telling you not to use this built-in, how could text from your program be displayed on your screen? Not without a lot o...

The future of Oracle PL/SQL: some thoughts on Sten Vesterli's thoughts

Sten Vesterli published a very thought-provoking post on his blog: Please stop reading this post, and read that one. When you are done, come on back here for my thoughts on Sten's thoughts. OK. You read it. Here we go. First, thanks, Sten, for being such an interesting, wise, sometimes provocative voice in our community. Next, Sten writes: Now, on the one hand, I certainly agree that the vast majority of young developers are currently caught up in the modern version of a Gold Rush, which is: "Build an app using JavaScript, pay no attention to that database behind the curtain." But I can assure you that I still do meet young PL/SQL programmers, regularly, when I am at conferences and doing onsite presentations at companies. So, young person who writes PL/SQL: do not be afraid! You are not alone! And you are super-smart to have made the choice you did. :-) Next, Sten offers this advice to managers: I agree that PL/SQL is a "spec...