so fascinating.. suns swallowing up other suns .. galaxies swallowing up other galaxies!! the size of these celestial objects is immense.. so hard to get my head around
also if answers to those questions alone has given you access to your account it is most certainly implemented poorly.
Typically access to the account would come in a 2nd factor form like clicking on a reset password link from an email account that is yours and previously configured for such service. Only then would you be allowed to provide a new password to recover the account. Brute force protections like ensuring only a finite amount of failed attempts are necessary.
The pupose of the “security question” is simple.. if a user needs to recover their password then the next best way to verify authenticity of the password reset request is to verify they know the answer to a few pieces of information they have previously shared with the service. In the age of mobile devices and 2FA, this becomes a lot less relevant but is still a very viable alternative because it’s accessible and difficult to crack if done right.
we use kubernetes, helm and gitlab.. runtime configuration lives in each repo next to code - values.yaml, dev.yaml, test.yaml, prod.yaml to store applications runtime configuration -- each environment is host to 40+ redundant services.. its working quite well but has required a pretty big upfront investment... surprised there was much discussion about monitoring- prometheus and grafana work well for that
You need to pick something you can sink your teeth into but unfortunately that doesn't satisfy your first requirement (limited amounts of time). Learning things of value normally takes time and lots of dedication.
I worked for AMD in the x86 64bit multicore expansion days (2006ish) There really has been much since then except the ATI acquisition. Selling to Chinese manufacturers sound like a last ditch effort unfortunately.
Having the optional clauses laid out is really nice for founders... And I like the table that spells out all of the parameters of the grants—very employee friendly.
Doesn't sound too far off from Kinvey and Parse except for the fact that MBaaS services have been around a lot longer and have much more robust mobile and web SDKs.
My wife's a nurse and she said if the test comes out high or low they always do a blood draw to double check. So this doesn't seem that ground breaking of a study.
I moved to Boston from Austin when Kinvey got into TechStars (2011). At the time Austin was a "fun" place to live but a hard place to start a venture-backed startup. Boston has been a great place to grow our team. Our first five engineering hires were awesome and we continue to find great talent and support from the startup network here.
I'm the author of the blog post.. Thanks for taking the time to read it and comment.
You're right, it was a bit of a stretch to label Clippy as tech support. However he was introduced for the purposes of help to the customer, which is the essence of the blog post.
The main take away for the post is that it is important for organizations and its leaders to view customer support as an opportunity to engage their customers and improve their product.