I did the challenge in a different way, but I couldn't win anyway, and I actually saw several people winning with much longer time than I did. In one of the times it reached 0.0095 and still I didn't win. 0.0173 a couple of times, this really frustrated me as there didn't seem to be a time pattern, and while ones with much longer times get it. But it was all worth the challenge. 😉 Congratulations Micah and everyone.
Things get dicey once you get down to a really short amount of time left! I noticed that as my bot shaved down time closer to 0, my results were as consistent with me "winning".
@@MicahDanielSmith I had to go forcing more and more since with times, as the ones presented in the video were not enough, I was forcing more and more to close to zero, but it was not good enough, but it was worth the try.
A great challenge ! Thanks for explaining how you solved the challenge, another excellent video! - every step explained clearly and in a way that promoteds good practices moving forward. I too started out capturing the auction time remaining and extracting the number and using the while-loop, but then ended up comparing using string and checking for "1 second" shaving off some time. I also placed the bid at the very last second. I also didn't realise that you could submit any bid value, I captured the last bid converted to a number, incremented by $6, converted back to a string then submitted (place bid then confirmed) - final bid time was 0.01987! and I saved a lot of $$$$
Nice approach to solve this problem. I did not included the final result capturing step through bot itself, captured result manually. I will include one more step to my bot for the same :)
Nice Rahul! Awesome to hear that you got this one sorted out. Capturing the GUID will help with some stuff we plan to release next week and beyond...Worst case you could always go back and re-run your bot though. Keep up the great work on your builds!
I think whats really cool about this challenge is that if you want to use Web Automation, you can...if you want to use Browser: Run JavaScript, you can...if you want to use Recorder, you can...all will ultimately give you a similar outcome...and it really depends on your own comfort level in JS/which packages you want to use.
I did the challenge in a different way, but I couldn't win anyway, and I actually saw several people winning with much longer time than I did. In one of the times it reached 0.0095 and still I didn't win. 0.0173 a couple of times, this really frustrated me as there didn't seem to be a time pattern, and while ones with much longer times get it. But it was all worth the challenge. 😉 Congratulations Micah and everyone.
Things get dicey once you get down to a really short amount of time left! I noticed that as my bot shaved down time closer to 0, my results were as consistent with me "winning".
@@MicahDanielSmith I had to go forcing more and more since with times, as the ones presented in the video were not enough, I was forcing more and more to close to zero, but it was not good enough, but it was worth the try.
A great challenge ! Thanks for explaining how you solved the challenge, another excellent video! - every step explained clearly and in a way that promoteds good practices moving forward. I too started out capturing the auction time remaining and extracting the number and using the while-loop, but then ended up comparing using string and checking for "1 second" shaving off some time. I also placed the bid at the very last second. I also didn't realise that you could submit any bid value, I captured the last bid converted to a number, incremented by $6, converted back to a string then submitted (place bid then confirmed) - final bid time was 0.01987! and I saved a lot of $$$$
Nice David! Glad to hear you were able to explore some different approaches!
Awesome challenge, thanks Micah!
Nice approach to solve this problem. I did not included the final result capturing step through bot itself, captured result manually. I will include one more step to my bot for the same :)
Nice Rahul! Awesome to hear that you got this one sorted out. Capturing the GUID will help with some stuff we plan to release next week and beyond...Worst case you could always go back and re-run your bot though. Keep up the great work on your builds!
@@MicahDanielSmith Thank you.
Looking forward to next challange 😀
Web automation package would be more efficient I felt then record capture as AA introduced web automation particularly for Chrome applications
I think whats really cool about this challenge is that if you want to use Web Automation, you can...if you want to use Browser: Run JavaScript, you can...if you want to use Recorder, you can...all will ultimately give you a similar outcome...and it really depends on your own comfort level in JS/which packages you want to use.