I spent five years teaching at the University level. The beginning of the end of my academic career was receiving an e-mail from a student explaining one of my (programming) assignments and asking if they could write this one too. To me this was an obvious case of VERY incorrectly choosing the "to" address for an e-mail.
I immediately contacted my department head and was ready to apply the school's academic dishonesty policy, which would lead to--at least--failure of the course. It didn't happen. The student came up with a lame excuse, I was chided for harassing the student, and it was all swept under the rug. I was tempted to resign in protest, but kept with it for two more years before quietly leaving academics.
I enjoy teaching, I think I'm good at it and my students tended to agree. Unfortunately, I can't make myself teach in the current educational system here in the US.
I only taught for 2 years as a graduate teaching assistant, but we were told in training to never accuse anyone of cheating ever. It opened the university up to being sued, and made everyone's life more complicated.
I guess this particular part has never greatly bothered me about academia, though plenty of things are quite broken and bother me.
I mainly value whatever education takes place, not the formalities, so if someone who doesn't deserve it gets a degree, who cares? I can see that for people who care about the value of the pieces of paper, it's important to keep unqualified people from getting them. I just can't bring myself to care that much about that, though. To me the important question is whether people who want to learn are able to; not whether people who don't want to learn slip through or don't slip through.
The much bigger failing in my mind isn't that cheaters aren't sufficiently punished, but that motivated students who want to learn things other than exactly what they're assigned are given virtually no assistance, and often actively discouraged (the side-projects-are-bad, keep-your-head-down-and-do-what-you're-told mentality).
It matters more when the credential is used in licensing a difficult and socially important function like medical care, though. I think people were undestandably up in arms a while back about the institutions which were giving out fake degrees.
Different perspective though, from an academics point of view that does make an effort to reach out to students and teach them well this cheating would be disheartening.
I can see that, but I'm an academic myself, and somehow it doesn't bother me much (it does bother many of my colleagues).
I guess I'm most strongly motivated by providing assistance and resources to people who want to learn, so whatever happens with the people who don't want to learn doesn't bother me that much. I'll enforce whatever rules I have to, to the extent the institution provides me a means to do so (and requires me to), but it just isn't a big motivator for me.
I would prefer the proportion of students who are there to learn to be higher (it'd be a more enjoyable and motivating environment), but I don't think being more of a hardass on cheating is going to solve that problem. It's probably true that there are students who, while tempted to cheat, would be great students if they were scared away from that temptation by vigorous enforcement. My guess is that number is fairly small, though.
I think most of the people who cheat are the kind of student who doesn't really want to be in this major at all, but feels they need to get this degree to get a job. I think vigorous enforcement with those students, even if it successfully stamps out cheating, will just result in a bunch of students grudgingly doing the work because they now have no choice. But that kind of student still isn't that fun to teach, so my motivation to expend more effort than I have to on converting "cheaters" into "grudging teeth-gritters" is pretty low.
Sounds similar the story about a week ago where are professor is being disciplined for recommending that a grad student's degree be revoked, because the student did not meet the requirements.
Robin Hanson from OvercomingBias says it best: School isn't about learning:
I was a lab instructor for one of my favorite professors after excelling in his class. I caught one of his students cheating blatantly (assembly code was nearly identical to another students, just shifted around a bit)
The professor is a good man, and was very upset. It was almost kind of sad, he was angry but it was almost like he could've alternatively started tearing up at any moment. Damn administration didn't do anything about it though, and that very student I caught cheating has since been in several classes with me. Burns me up.
Guess it shouldn't surprise me that the prof. hasn't had any courses for several quarters now. I swear, the good ones don't seem to last. The only one we've got left in the department that cares about the students, I'm not even sure how he manages.
The in keyword has been very controversial as with it comes the deprecation of setfenv and getfenv, which are very useful for sandboxing and other tricks. The inclusion of a standard bit operations library is also a big deal, though Mike Pall (author of LuaJIT and LuaBitOp) has raised some objections.
Indeed. About a week ago, I wrote an extension to load modules in a proxy for hot code loading. It's pretty closely tied to get/setfenv. It's still too new to share, but I'm going to see if I can get it working with 5.2. Requiring the debug library (for debug.[sg]etfenv) will be a dealbreaker for some people.
Give a try on CurdBee (http://curdbee.com) for invoicing and billing. It would fit perfectly for your startup if you are looking for a smart and low cost solution (you can start using it for Free!)
Except for basic editing tasks they aren't really comparable. Pico (or it's clone nano) are basic text editors designed to be easy for beginners to learn and use. Emacs is a text editor that is so extensible (and so extended!) that it's often compared to an operating system.
I used Emacs continuously for two years and vi on-and-off over five years. What do I use now when I need to do a bit of text-editing on a CLI...I use pico or nano. The problem is that I don't use Emacs or vi all the time, and can't remember the key bindings well enough to use them effectively. That's not a problem with pico.
So to answer your question: as long as you're doing relatively small programs (hundreds of lines and only a few files) pico should be fine. You might want to look into nano though, it looks the same but allows syntax highlighting and is more configurable.
Sorry, I have to disagree. It's fine if you need to write a few dozen lines once a week or something, but if you code any more than that, I'd suggest learning a more advanced editor. Don't limit yourself to pico or nano. Try emacs or Vi. It's worth the few weeks to learn (and few years to learn well).
I've used both, though seem to be a bit quicker in Vi - try evim (easy vim) if you're not comfortable with jumping right in.
I immediately contacted my department head and was ready to apply the school's academic dishonesty policy, which would lead to--at least--failure of the course. It didn't happen. The student came up with a lame excuse, I was chided for harassing the student, and it was all swept under the rug. I was tempted to resign in protest, but kept with it for two more years before quietly leaving academics.
I enjoy teaching, I think I'm good at it and my students tended to agree. Unfortunately, I can't make myself teach in the current educational system here in the US.