BAZINGA!
195 karma · joined May 5, 2016
BAZINGA!
Essentially the difference is people sometimes complained of losing a lot of data because no cloud backups and no iOS version hence i'm doing web+android+ios. Also a lot of people wanted to be able to track doing habits multiple times per day or track some specific metric (30x pushups) which I've chosen to implement. Small things like that but they add up.
Years before I ever read Thinking Fast and Slow I clicked on to the fact that humans are predisposed to making exceedingly poor decisions. This is such a fun example.
I almost want to start a side-project based on collecting these...
Also... nothing can quite prepare you for how shot your nerves can be. It definitely pays to run it through many times as you can with a timer so that you are at least confident in your pacing.
Other than that it's quite fun.
It can be pretty handy to you to include your twitter handle in the top right corner so you get some follows throughout the presentation from people who were interested. At the end link off to 'you can find the slides for this presentation here bit.ly/soloyolo' etc.
I put together http://www.debug.coach/ because a guy I used to work with had better debugging skills than anybody and I noticed it was because he always knew the right questions to ask.
It works really nice with Rails because of how easy Rails makes it return a piece of javascript to the page (this is called SJR) so there is some magic included for making form submissions work which is part of the Rails turbolinks gem. The javascript that the server returns to the page essentially calls Turbolinks.visit("/url-form-submission-would-redirect-to-after-completion") so that the expected navigation takes place. It's quite clever. I think you would have to replicate that in the Java world to get the full experience. This SO answer alludes to how you might replicate SJR https://stackoverflow.com/questions/26750738/java-spring-ret...
So I think out of the box you can expect clicking links to work (and that alone provides a great speedup), but ajax form submissions will require some work. If you look at some articles on how form submissions with turbolinks make use of SJR you could likely figure it out and implement it. It's overall not a very complicated mechanism.
I suppose Rails .erb templating engine also has some helpers which the form submission side of turbolinks relies on. Namely it includes a data attribute data-remote and that's the thing turbolinks hooks into to prevent the default behavior of the form submission and and instead fire the ajax request. In theory so long as your forms include that it will work if you have the SJR stuff in place on your back-end.
You could definitely roll full support for it.
Could there be a bug in a library/3rd party code? Could there be a possible race condition?
I remember recently hitting a bug in a 3rd party library in a Jar provided by Oracle in WebLogic to do with an incorrect implementation of the W3C DOM API causing XML validation to fail whenever attributes were present. Of course the J-Unit tests provide a different Jar and thus a different (correct) implementation and no bug. Took ages to track down.
e.g I wanna try it but i'm TOFU