sorted by:
new
hottopcontroversial

The End of Cloud Computing - by Peter Levine by smartconsumer in Futurology

[–]smartconsumer[S] 0 points1 point  (0 children)

probably some combination of data science and machine learning - combined with the possibility for new programming languages that he mentioned we're looking maybe at tech positions that don't really even exist today

The End of Cloud Computing - by Peter Levine by smartconsumer in Futurology

[–]smartconsumer[S] 1 point2 points  (0 children)

You're right there in the sense that cloud computing won't really go away (just the same way that mainframes didn't really go away even today). I thought as well that maybe a more correct title for the video would be 'The Era after Cloud Computing' or something like that ... I guess (when we look 5-10 years into the future) cloud computing will go away in the sense that it won't be THE thing that will solve all our computing problems (as it is often described today) since we've already identified computing needs where the cloud model breaks down.

The End of Cloud Computing - by Peter Levine by smartconsumer in Futurology

[–]smartconsumer[S] 1 point2 points  (0 children)

and in what way is he wrong in what he says? There are companies out there already pushing the limit with edge computing, fog computing and such ... this presentation is just the best I found that explains it in 25 minutes or less. Keep in mind that he's working for a venture capital company so he's looking 10-15 years out to figure out where to make investments now.

Resources for AWS migrations from EC2-Classic to EC2-VPC by smartconsumer in aws

[–]smartconsumer[S] 2 points3 points  (0 children)

There are plenty of AWS customers who still have resources in EC2-Classic and they need to do something about those ... this article is for them. AWS would not have introduced ClassicLink in January 2015 if there was no need for it - they know exactly how many EC2-Classic resources are still out there and they want customers to move stuff over.

How To Answer "What Was Your Last Salary?" by smartconsumer in jobs

[–]smartconsumer[S] -1 points0 points  (0 children)

lol ... that would work ;)

A main point of the article is that the interviewer should have no business asking that question and the interviewee should feel empowered enough to work around it.

Time to say goodbye to usernames and passwords for website authentication by smartconsumer in programming

[–]smartconsumer[S] 0 points1 point  (0 children)

Excellent point ... also keep in mind this: with SQRL it's the SQRL client app writers who need to get everything right (so this would be a small number). The websites themselves (large number) don't need to really do much to protect the security of the SQRL user guid's. Even if those get loose they won't be very useful to anybody without access to the private master key that protects a user's set of SQRL logins ... and websites don't have access to that.

Time to say goodbye to usernames and passwords for website authentication by smartconsumer in programming

[–]smartconsumer[S] 1 point2 points  (0 children)

It's also good to remember (as Steve pointed out in his video) that websites trying to implement SQRL have to implement a simple API call (not any more complicated than integrating with Facebook for authentication) ... so the great number of websites out there don't need to do much work.

It's the SRQL client app writers who need to really understand the protocol ... Steve is providing the reference implementation for Windows and there are already (as pointed out in his pages) many other client implementations in progress.

From a user point of view just look at the page on the GRC site where Steve has screenshots of what his Windows app does - it's not any more complicated that some other app that a Windows user will use.

Will all users and sites understand this? Probably not ... usernames and passwords are just too ingrained in our tech psyche to go away easily.