I recently read this blog comparing the speeds of different functions that JS has in comparison to for loops and for each loops. It was a pretty interesting read, and for loops out performed everything else in terms of pure speed. The nuiances of efficiency and speed goes a little deeper.
As the the amount of data we consume and needs to be stored increases an innate issue arises in the storage of said data. I recently read an article talking about sql and nosql and how data storage via either platform has it’s pros and cons; nosql seems to be a growing idea - if there can be a unified language like “Sql” to query the data. I don’t fully understand how nosql works, but it seems to be relatively cheaper to implement then SQL. To scale up cost effiency is a big factor for a lot of companies who can’t afford sql.
When presented with a problem how do you solve it? Sometimes it’s difficult to come up with an efficent solution on the spot, what’s best is to drum up the most direct solution you can find - brute force and work backwards from there. You may have to think outside the box of what the question is really asking - what are the input values? what is the expected output?
I recently came across this ted talk attached here it brought up a really interesting topic on our data driven society and the loss of personal privacy. What we think of privacy now a days is screening individuals who can see your profile, but this is just a facade. Your data is virtually public once it goes into the internet.
I recently read an article about bringing a Web standard for passwords. The general gist of the article was that and I quote “The FIDO Alliance and W3C have launched a Web Authentication standard that makes it easier to offer truly unique encryption credentials for each site. “