3 ms·

-

by x5n1 10y ago

smt88 10y ago
Original parent comment which has now been removed: > In software and programming it matters little if you cheat. It works or it's shit. It's easy to tell the difference. And it's pretty easy to fire interns or juniors, etc. Not only that but you don't really learn how to do jobs anyhow. Every single sentence in your comment is ludicrously false. > In software and programming it matters little if you cheat. What if you steal software from your old employer? What if you hack a competitor? What if you base your entire project on something that you can't legally use, and then you're sued? Outside the corporate/legal world, there are still areas where cheating is very harmful. Violating open-source licenses, pretending someone else's work is your own, etc. The open-source world works (when it does work) because of transparency and something like the honor system. Cheating matters a lot in software. > It works or it's shit. That is just complete, utter nonsense. There is a huge spectrum from "good" to "shit", and "working" begins near the "shit" end. > It's easy to tell the difference. If it were easy to tell the difference, you could just throw a junior developer into a management role. Lots of juniors have the people skills and organization skills to manage a small project, but they don't have the experience to know which practices are OK in the long-run and which practices aren't. Object-oriented programming is a great example. Many programmers in the FP camp think all OO programs are shit. Many of them took years to come to that conclusion. If it's so easy and clear-cut, why is there little agreement on what makes good software and what doesn't? > And it's pretty easy to fire interns or juniors, etc. Not in the US and most other developed countries. Firing people is risky and expensive. I worked for a company that was sued by an ex employee for a completely bullshit reason, and the company lost $400k in legal fees that they could never recover because the employee didn't have that kind of cash. > Not only that but you don't really learn how to do jobs anyhow. You don't learn how to write code for a living, but you do learn time management and people skills, which are much more important anyway. Most coding work at most companies only requires an average worker. Would it be better to have people with amazing skills doing 100% of the work? Yes, but there aren't enough of them. What differentiates all those average people is whether they work well on a team, how well they manage their time, and how well they learn. All those things are learned in college, and all of them are undermined by cheating.
- deleted 10y ago
  [deleted]

by x5n1 10y ago

smt88 10y ago

Original parent comment which has now been removed: > In software and programming it matters little if you cheat. It works or it's shit. It's easy to tell the difference. And it's pretty easy to fire interns or juniors, etc. Not only that but you don't really learn how to do jobs anyhow. Every single sentence in your comment is ludicrously false. > In software and programming it matters little if you cheat. What if you steal software from your old employer? What if you hack a competitor? What if you base your entire project on something that you can't legally use, and then you're sued? Outside the corporate/legal world, there are still areas where cheating is very harmful. Violating open-source licenses, pretending someone else's work is your own, etc. The open-source world works (when it does work) because of transparency and something like the honor system. Cheating matters a lot in software. > It works or it's shit. That is just complete, utter nonsense. There is a huge spectrum from "good" to "shit", and "working" begins near the "shit" end. > It's easy to tell the difference. If it were easy to tell the difference, you could just throw a junior developer into a management role. Lots of juniors have the people skills and organization skills to manage a small project, but they don't have the experience to know which practices are OK in the long-run and which practices aren't. Object-oriented programming is a great example. Many programmers in the FP camp think all OO programs are shit. Many of them took years to come to that conclusion. If it's so easy and clear-cut, why is there little agreement on what makes good software and what doesn't? > And it's pretty easy to fire interns or juniors, etc. Not in the US and most other developed countries. Firing people is risky and expensive. I worked for a company that was sued by an ex employee for a completely bullshit reason, and the company lost $400k in legal fees that they could never recover because the employee didn't have that kind of cash. > Not only that but you don't really learn how to do jobs anyhow. You don't learn how to write code for a living, but you do learn time management and people skills, which are much more important anyway. Most coding work at most companies only requires an average worker. Would it be better to have people with amazing skills doing 100% of the work? Yes, but there aren't enough of them. What differentiates all those average people is whether they work well on a team, how well they manage their time, and how well they learn. All those things are learned in college, and all of them are undermined by cheating.

deleted 10y ago
[deleted]