in reply to Offering a helping hand
My example: I have colleague who belives in complete freedom in programming. As a result, her programs have strange indent, naming variables does not make any sense and same database field has name abbreviated differently in different scripts (I have to read her programs and add features sometimes), and she strongly believes that 'use strict' is wrong because it breakes her "correctly working" code.
My advice: is easier to learn correct way, than un-learn wrong way and re-learn correct after.
You have unique opportunity to set some rules/coding guidelines, do not miss it. Let's be concerned about expressing individuality AFTER achieving mastery.
Update: To former Visual Basic user, you need excellent visual debugger, othervise his first impression will be "perl sucks, VB is better". You are right, there is visual debugger for perl, check Open Perl @ sourceforge.net. Like Visual Basic, only for free. Now your student is hooked in.
pmas
To make errors is human. But to make million errors per second, you need a computer.
|
|---|