I would like you to create videos where you also show the mistakes to get to the end. It will be long, but at least we will understand a lot more. Always considering the fact that the R82 version of ElasticXL will certainly still have some bugs. Have a good time and thank you for your videos.
for your question, personally would rather see the 'how to' guide, not the 'let's play and learn'. Both have value, however just like the AI copilot you're mentioning there is a lot of false start information which having yet another such doesn't really help in my experience when trying to show someone (or if you need to quickly pick up on something). That being said, like you, I do a *LOT* of labbing and builds to test or find edge cases or to really understand how the items work. Some may find that useful, if they are completely knew. But from my experience in trying to train others I've found nothing that seems to 'stick' better than have the person build their own (i.e. hands on) following the documentation. i.e. I don't want them to rote follow some process or method but to think critically and ask 'why' 'what if' or 'how' and then build up a lab to test those questions.
Thanks sir 🎉
I would like you to create videos where you also show the mistakes to get to the end. It will be long, but at least we will understand a lot more. Always considering the fact that the R82 version of ElasticXL will certainly still have some bugs. Have a good time and thank you for your videos.
Thanks, quick question, how did you make Co pilot to run on your UC accont?
Check point started to roll it out a few weeks ago for CCSP partners, if you are missing it check with your checkpoint rep :)
for your question, personally would rather see the 'how to' guide, not the 'let's play and learn'. Both have value, however just like the AI copilot you're mentioning there is a lot of false start information which having yet another such doesn't really help in my experience when trying to show someone (or if you need to quickly pick up on something). That being said, like you, I do a *LOT* of labbing and builds to test or find edge cases or to really understand how the items work. Some may find that useful, if they are completely knew. But from my experience in trying to train others I've found nothing that seems to 'stick' better than have the person build their own (i.e. hands on) following the documentation. i.e. I don't want them to rote follow some process or method but to think critically and ask 'why' 'what if' or 'how' and then build up a lab to test those questions.
I think you are right now when the version is new.
So iguess i need to rerecord some videos ;)