Skip to main content

Fine-tuning the Quiz-taking Experience on the Oracle Dev Gym

Back in June 2016, we announced "early adaptor" access to the Oracle Dev Gym, a new skin on top of the PL/SQL Challenge quiz platform.

Since then, we've gotten lots of great feedback, and lots of usage on the site. Players have set up 543 monthly goals, with over 2,200 workout exercises (with 1,200+ actually completed :-) ). Plus more than 4,500 quizzes have been answered at the Dev Gym, vs. the "traditional" PL/SQL Challenge.

All good news.

When I held our first live Dev Gym workout with the Chicago Oracle User Group two weeks ago, however, I did get some very critical reviews of the quiz-taking experience.

Basically, we are using too much real estate for players to easily see the code in the question and the various multiple choices, some of which can be very long in and of themselves.

So we went back to the drawing board and made a number of changes, which we rolled into production today.

To summarize:
  • The left sidebar is closed by default to minimize distraction and usage of page real estate.
  • Each choice now uses up less space. We've reduced white space and padding wherever possible.
  • There is now a "scratchpad" in the right sidebar, so that you can write notes to yourself (comparisons between choices, for example) that remain visible even as you scroll up and down the question.
  • Choices can be expanded or compressed - individually or as a group. With just a click or two of your mouse, you can zoom in on a single choice, or two, allowing you to focus attention more tightly.
Note: there is one known issue with the collapsing process. When you collapse all the direction icon on the left is not changing. So you need to click twice on it to expand a particular choice. We should have that fixed soon.

We explored other possibilities, like using sliders to allow you to have the question remain on the left, while you scroll up and down through the choices. We decided not to pursue this approach because it does not work well on mobile devices, and we are aiming for a smooth, responsive website regardless of your device.

I offer some screenshots below to give you an idea of what we've done. Please do take a quiz on the Dev Gym (accessed through the PL/SQL Challenge) and let us know what think.

Oh, and that's not all: we've also added a dashboard on the home page.

And if you have other suggestions for improving the quiz-taking experience or the dashboard or anything else, don't hesitate to click on the Feedback link on the top right of the site!

Scratchpad

See something on Choice 1 you want to remember when looking at the other choices? Jot it down!



Collapsed Choices

You can Expand All or Collapse All and then fine-tune from there.













Just One Choice Uncollapsed

Open up one or more choices selectively. The banner on each choice displays green if you've selected it as correct. This is visible even when collapsed.












Dashboard

Let us know if you'd like to see different information or see this data differently (visually).


Comments

Post a Comment

Popular posts from this blog

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...
4 comments
Read more

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...
46 comments
Read more

Table Functions, Part 1: Introduction and Exploration

Please do feel encouraged to read this and my other posts on table functions, but you will learn much more about table functions by taking my Get Started with PL/SQL Table Functions class at the Oracle Dev Gym. Videos, tutorials and quizzes - then print a certificate when you are done! Table functions - functions that can be called in the FROM clause of a query from inside the TABLE operator - are fascinating and incredibly helpful constructs. So I've decided to write a series of blog posts on them: how to build them, how to use them, issues you might run into. Of course, I am not the first to do so. I encourage to check out the  documentation , as well as excellent posts from Adrian Billington (search for "table functions") and Tim Hall . Adrian and Tim mostly focus on pipelined table functions, a specialized variant of table functions designed to improve performance and reduce PGA consumption. I will take a look at pipelined table functions in the latter part...
31 comments
Read more