In the age of any website getting hacked, take your steps carefully. But then dont make a business of this discovery, but assist. go ahead inform them by phone call, keep logs of your conversation.
Radical: There is policy followed, do not use code from the internet, just write your own code.
Forgetting the above, I just want to know the psychology part, on why would someone keep taking libraries from the internet, after being repeatedly said not to do so
But that's just a question of due diligence. Anyone who pulls random code from unknown sources with no evidence of testing or competence gets what they deserve.
Yes, there are people who seem never to write code, and there are others who seem endlessly to re-invent the wheel to no good purpose.
I guess I just don't understand what you're asking. So I'll give up.
Correct..Using an IDE for coloring, matching, highlighting okay. But using an IDE such as DreamWeaver and rely on its coding structure and when asked to hand code, wonder what the syntax of the mysql query statement should be, is not very welcoming. If this is the case, they cannot properly debug a code written by someone.
You either generally know the syntax of a particular programming language or you don't. There's nothing wrong with looking up the details of a particular function. Sometimes when I'm really busy, I find its easier to look up the details of a function than change my mental focus or train of thought. When that happens, I usually have a favorite book or website that details the language. Also, you don't need a fancy IDE for syntax coloring/matching/highlighting. A very simple text editor tends to be alot faster and easier to use.
I asked someone to hand code. This guy was so used to Dreamweaver, that he could not just remember certain code, like mysql query.
But on the DMW, he was fine, clicking away, getting stuffs done.
In that case it is their manager's responsibility to ensure they have access to the IDE. The important thing is how effective the combination of programmer + hardware + software + other working conditions is. I don't see that considering a coder in isolation is terribly useful.
It's the interviewer's job to decide what they're testing for. Some developers need an IDE - that does not make them bad developers.
An interviewer should ask
How can we help you show us why
you'd be good for this job?
Stupid tricks don't help you determine if someone can do a job. Tiny, trivial programming tasks don't tell you if someone can do the job, but can (sometimes) tell you if someone can't do the job.
Interviewing is hard, there are no short cuts. You need someone who is smart, will get things done, can interact usefully with others, and adds value. Sometimes using an IDE is the best way to accomplish that - why ignore someone just because they don't work the way you do?