Comments URL: https://news.ycombinator.com/item?id=47186603

Points: 5

# Comments: 0

I have noticed though that experience become a liability. If you wrote JavaScript for IE 6, a lot of the optimizations and things one did to make sure things worked in IE 6 are no longer necessary. One should be ready to let go of things as soon as they aren't necessary anymore. Always keep learning and know why you do the things you do with code.

This is really bad advice, because much about learning programming is about an individual effort. It has little if anything to do with the school.

> If you find a person with an MS who can't pass a simple programming test

You actually need more than a simple programming test that solves a single problem. You need to see enough code to have some architecture, designed by the candidate. Interviews are too short for this so experience whether at some other company or open source, or just if skilled people can vouch for you goes a long way.

The thing is, more education will enable a good developer to be even better. It's doesn't seem to help a struggling developer in any shape or form. Unfortunately sometimes I get the impression that people stay in school to address a problem that can't be addressed with more classroom time and end up doubling down on a field that maybe isn't right for them.

At the very least try to intern early on and or successfully help a popular open source project before graduate school.

I like Noogle so much I might write up a quick chrome extension that turns Google into Noogle everywhere.

https://news.ycombinator.com/item?id=4499435

https://aboutmybrowser.com/

http://www.browser-details.com/

One problem with storing passwords is that there is no good reason to. The other security issue is that people reuse passwords. So everyone should be creating hashes instead of encrypting passwords, but encrypting text, and transmitting it securely is still secure. This API didn't do that, it did a lot of things wrong, but these comments are all pretty ignorant as well.

It's just one inane comment after another in this thread.

Mercurial is an application you use to version control your source. I'm not sure I understand why any python developer would care if Mercurial was written in python 2 as long as it worked. Maybe if someone was writing a Mercurial plugin or patching Mercurial they would care.

The post gave no indication how Cricketer was storing the passwords. They may very well be stored encrypted.

You can send plain text passwords back if you've encrypted them, you just have to decrypt them first. There's no point at all in returning the results of encrypting a password if the clients don't know how to decrypt those results. Given that the API uses plain text HTTP, I doubt that the passwords are encrypted.

What the passwords are not stored as however, are hashes. A hash is not the same as text that was encrypted. A hash is a difficult to reverse unique identifier for bit of text.

Having said all this, it is funny to see your post, and all its replies making fun of security incompetency while also being incompetent in themselves.

It's nice they make user friendly phones, but I don't think your logic works out like that.