As a Training Specialist at Red Hat, I work with learners that have a variety of goals with the learning subscription. Often times the most difficult part is how and where to get started.
I would love to hear from learners on what they think the biggest obstacle to getting started is?
I would like to suggest creating "learning paths" that would show the progression of classes as Red Hat intends them. This would also allow for future gamification opportunities.
For example, I had to Google around the RedHat site for a while, trying to find which JBOSS class to start with. While a good clue is to always go with the lower number, that only works when the prefix stays the same.
Another issue, at least for the Java classes, is to better annotate which versions a class covers (i.e. EE 7 vs EE 6). Staying with Java classes, it would also be great to annotate which videos in a EE 6 class have topics that are still relavant to EE 7 if the EE 7 version is not avaiable yet. For example, while the messaging queue implementation was swapped out, the Java code in the project doesn't necessarily chage. I would want then want to view the code videos, but skip the implementation configuration modules.
I would also like to suggest revamping the "Reports" tab so it is more of a "Course History" feature that would allow me to continue my current course.
I would love to hear any academic/medical theories on how you deal with anxiety while watching videos.
I have tried the pomodoro technique but was not very successful.
One thing that could be helpful is when you see something equivalent of (to use RH terms) of a yum dependency tree for courses. Something that always annoyed me about college catalogs. Interested in Course Z, well it has a prerequsite of Y. Okay, look up course Y, it has prerequisites of X and W, and so forth. Might help plan out course progressions if you're doing the RHLS. Just a thought.
In broad/vague terms, I would say the biggest obstacle to any learning is just inertia.
With a Bachelor of Science in Aerospace Engineering and more than 20 prior years experience in Systems Engineering, Software Engineering, and Systems Administration, I was under-employment for a year and unemployed over 6 months, when I applied for a job that required the RHCSA certification _prior_ to hiring me in 2014.
The hard requirement was a great motivation and I was able to keep the momentum going with RCHE in 2015 and other vendor certs that opened other roles in that organization, but when that job ended in 2016 and I found another job that didn't so strictly care about the certs, I found it difficult to keep the momentum going... until I only had enough study weeks left to schedule my RHCSS 3 days away from expiring both my RHCSA/RHCE!
Thanks to you, Kevin, reaching out in my rut, I had a glimmer of hope to get it done.
I think that is the greatest thing about the RHLS, that the subscription model helps keep the momentum going, and I have great hope in the coming year that it will help me achieve the RHCA within the subscription year, as several people have posted their experience on in various forums.
Continuing on the topic of inertia vs momentum, and re-iterating on others' suggested improvements above, I would say you have fairly well laid out the 2 major tracks for developers vs sys-admins (although some of us with a mix of both backgrounds think devops is somewhere in the middle), and also suggesting broad technology/product areas such as data-center, devops, etc. I wonder whether an even more granular set of course intersections might be achieved by drilling down to even more specific job/task descriptions?
Perhaps if there was a way for you to harvest (with opt-in/out) and harness that intel from existing RHCPs title/job-descriptions and choice of CoEs, whether completed or future goals, that would then assist you in advising aspiring candidates with goals towards similar goals?