Skip to main content

Feedback needed for the Oracle Dev Gym dashboard

Waaaaaay back on June 27, we opened up the doors to the Oracle Dev Gym, our next generation website built on the quiz platform that powers the PL/SQL Challenge.

One of the big changes for Dev Gym is a de-emphasis on the competitive aspect of quizzes, combined with making it much, much easier for a visitor to quickly take a quiz from our library of 2000+ quizzes.

So far, overall, feedback has been quite positive, and we are very pleased.

But a number of longtime players have offered feedback like the following:
About Dev Gym: It is much easier to find what you want to do with this layout. The only thing I miss is the Dashboard where I can see at a glance the results of the latest quiz and maybe "Top Players (and You)", especially when I'm not at the first page of the Leaderboard :-)
The home page of the PL/SQL Challenge offers both a dashboard (sorry about this "empty" example, but as a site admin, I cannot compete):


and a Top Players (and You) section:


We will show lots of the Top Players report on our Leaderboard page, no problem there. But we'd like to add a high-level dashboard to the Dev Gym home page.

Requirements for this dashboard include:
  • Simple, clean presentation: keep the amount of text and data to a minimu
  • Make it interesting for both competitive players and those simple wanting to strengthen their skills
So I have decided to ask our players to give us feedback: what would you prioritize for display in the dashboard? Can you point to any other sites that present this sort of data in a way you find helpful, intuitive, dazzling?

Thanks!
Steven


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: Save your source code to files

PL/SQL is a database programming language. This means that your source code is compiled into  and executed from within the Oracle Database. There are many fantastic consequences of this fact, many of which are explored in Bryn Llewellyn's Why Use PL/SQL? whitepaper. But this also can mean that developers see the database as the natural repository for the original source code , and this is a bad mistake to make. It's not the sort of mistake any JavaScript or Java or php developer would ever make, because that code is not compiled into the database (well, you can  compile Java into the database, but that's not where 99.99% of all Java code lives). But it's a mistake that apparently too many Oracle Database developers make. So here's the bottom line: Store each PL/SQL program unit in its own file . Use a source code control system to manage those files. Compile them into the database as needed for development and testing. In other words: you should never kee...
16 comments
Read more