True, anyone installing administering software (like MS SQL Server) should be wise enough to ensure that the defaults accounts are secure. However, what if it you are not directly administering it? For instance, lab managment software from Altiris installs the MS SQL engine with a blank SA password (and I don't believe it offers a built-in way to change it). Lots of areas use this software and perhaps failed to realize they were also managing MS SQL server (although on a very junior level).
At least California can't complain about this being a spoiler...even though it may sometimes seem like three years (an not three hours) time difference.
The student enrolled in a class. The class had a contract (a syllabus is a binding contract). Providing the syllabus did indeed mention the honor code, the student is wrong--not the school. Examples like this are ideal for showing our future technology generation the importance of standards and ethics. In short, the student was wrong, the school simply enforced its policy. Georgia Tech is an excellent school with a high reputation. If you want it on your resume, you have to earn it.
(just for the record, I am not a GaTech alumni, student or associate--I am actually associated with a competing school)
Sorry to burst your bubble, but lately Linux and open source aren't "ruling" at the university level.
Sorry, but I have to "repair" this bubble, sort of. It is true that non-MS setups (operating systems, development environments) are not "ruling" at the university level (pretty broad scope of fields) but they are ruling within higher education computational science departments (CS, IST, CIS, etc.).
I work at the director level within an accredited CS program. As we take an active part in the accreditation of other computing departments in the US, we follow the tools used very closely. Due to cost, flexibility, capability, etc. Unix based development environments are the most widely used within these educational areas. Yes, there are MS shops, but they are not in the majority. The use takes many forms (Unix/Linux labs, dual-boot labs, windows labs with ssh/telnet access to a central Unix/Linux server, etc.). But the end result is the same. Most educational and development work is not performed in MS evnironments for these areas. Providing a central server which a student can access from anywhere and develop in C, C++, Java, etc. is ideal).
True, anyone installing administering software (like MS SQL Server) should be wise enough to ensure that the defaults accounts are secure. However, what if it you are not directly administering it? For instance, lab managment software from Altiris installs the MS SQL engine with a blank SA password (and I don't believe it offers a built-in way to change it). Lots of areas use this software and perhaps failed to realize they were also managing MS SQL server (although on a very junior level).
At least California can't complain about this being a spoiler...even though it may sometimes seem like three years (an not three hours) time difference.
The student enrolled in a class. The class had a contract (a syllabus is a binding contract). Providing the syllabus did indeed mention the honor code, the student is wrong--not the school. Examples like this are ideal for showing our future technology generation the importance of standards and ethics. In short, the student was wrong, the school simply enforced its policy. Georgia Tech is an excellent school with a high reputation. If you want it on your resume, you have to earn it.
(just for the record, I am not a GaTech alumni, student or associate--I am actually associated with a competing school)
Sorry to burst your bubble, but lately Linux and open source aren't "ruling" at the university level. Sorry, but I have to "repair" this bubble, sort of. It is true that non-MS setups (operating systems, development environments) are not "ruling" at the university level (pretty broad scope of fields) but they are ruling within higher education computational science departments (CS, IST, CIS, etc.). I work at the director level within an accredited CS program. As we take an active part in the accreditation of other computing departments in the US, we follow the tools used very closely. Due to cost, flexibility, capability, etc. Unix based development environments are the most widely used within these educational areas. Yes, there are MS shops, but they are not in the majority. The use takes many forms (Unix/Linux labs, dual-boot labs, windows labs with ssh/telnet access to a central Unix/Linux server, etc.). But the end result is the same. Most educational and development work is not performed in MS evnironments for these areas. Providing a central server which a student can access from anywhere and develop in C, C++, Java, etc. is ideal).