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

Running out of PGA memory with MULTISET ops? Watch out for DISTINCT!

A PL/SQL team inside Oracle made excellent use of nested tables and MULTISET operators in SQL, blending data in tables with procedurally-generated datasets (nested tables).  All was going well when they hit the dreaded: ORA-04030: out of process memory when trying to allocate 2032 bytes  They asked for my help.  The error occurred on this SELECT: SELECT  *    FROM header_tab trx    WHERE (generated_ntab1 SUBMULTISET OF trx.column_ntab)       AND ((trx.column_ntab MULTISET             EXCEPT DISTINCT generated_ntab2) IS EMPTY) The problem is clearly related to the use of those nested tables. Now, there was clearly sufficient PGA for the nested tables themselves. So the problem was in executing the MULTISET-related functionality. We talked for a bit about dropping the use of nested tables and instead doing everything in SQL, to avoid the PGA error. That would, however require lots of wo...
4 comments
Read more

How to Pick the Limit for BULK COLLECT

This question rolled into my In Box today: In the case of using the LIMIT clause of BULK COLLECT, how do we decide what value to use for the limit? First I give the quick answer, then I provide support for that answer Quick Answer Start with 100. That's the default (and only) setting for cursor FOR loop optimizations. It offers a sweet spot of improved performance over row-by-row and not-too-much PGA memory consumption. Test to see if that's fast enough (likely will be for many cases). If not, try higher values until you reach the performance level you need - and you are not consuming too much PGA memory.  Don't hard-code the limit value: make it a parameter to your subprogram or a constant in a package specification. Don't put anything in the collection you don't need. [from Giulio Dottorini] Remember: each session that runs this code will use that amount of memory. Background When you use BULK COLLECT, you retrieve more than row with each fetch, ...
4 comments
Read more

PL/SQL 101: Three ways to get error message/stack in PL/SQL

The PL/SQL Challenge quiz for 10 September - 16 September 2016 explored the different ways you can obtain the error message / stack in PL/SQL. Note: an error stack is a sequence of multiple error messages that can occur when an exception is propagated and re-raised through several layers of nested blocks. The three ways are: SQLERRM - The original, traditional and (oddly enough) not currently recommended function to get the current error message. Not recommended because the next two options avoid a problem which you are unlikely  to run into: the error stack will be truncated at 512 bytes, and you might lose some error information. DBMS_UTILITY.FORMAT_ERROR_STACK - Returns the error message / stack, and will not truncate your string like SQLERRM will. UTL_CALL_STACK API - Added in Oracle Database 12c, the UTL_CALL_STACK package offers a comprehensive API into the execution call stack, the error stack and the error backtrace.  Note: check out this LiveSQL script if...
5 comments
Read more