5 ms·
First: The thinking and problem solving required in programming is not taught enough at universities in North America, nor overseas. Second: Being groomed to d
by j45 15y ago
First: The thinking and problem solving required in programming is not taught enough at universities in North America, nor overseas.
Second: Being groomed to do specwork is the big problem of most institutions.
Third: Many developers thinking they don't need to learn anymore. Or, that they are done learning and ready to pursue a job/career. This is as evident in NA as it is overseas. Constant self-learning and self-development as a programmer is something that simply doesn't happen enough. Overseas, and in North America.
Fourth: The cultural differences. Done doesn't always mean done and it's entirely a societal/cultural thing. It's helpful have to define done as 'tested and ready to launch', etc.
Fifth: Outsourcers: Paying weekly helps a lot in a land where people get paid monthly, if on time at all..
Sixth: No sense on hating on overseas developers taking jobs. IT's the people paying the bills in NA that decided to take away all those jobs. And I guess they pay the price in the long run for better, or worse.
Seventh: Job, let alone career opportunities in India seem to suck. Every job posting gets hundreds, if not thousands of applications. Imagine trying to pick out the quality, let alone trying to stand out.
Disclaimer: I've outsourced to India. I've hired developers newly moved to North America from the Indian Subcontinent and had good luck and bad luck, like any employee.
I have been told I share some heritage in with the Indian subcontinent a in the past few generations. I'm not an apologist or out to offend. We all can do better and we should all be supporting each other to become the best we can be.
- marshallp 15y agoedit: I was replying to DarkShikari, so adjust accordingly I'd argue whether copying is a bad thing. Copying or getting others to do your work is what great businesspeople and managers do. The system of cheating you describe above might be actually creating a great stream of entrepreneurs/networkers. If they could channel that talent to pfoductive use, like getting 3d printers or robots in their hands, or selling through telephones, it could be a huge resource for everyone. On a related note, everyone disparages Nigerian scammers. Yet these are highly entrepreneurial individuals that western companies should be hiring as salespeople.
- mcl 15y agoThere are very few times I've felt the absence of a downvote button for my profile on HN but this is one. We don't need 4-year professional courses to teach people who are yet to enter the workforce how to cheat. Plagiarism doesn't require boot camps for undergrads to start practicing it as a valued skill, it needs an attitude adjustment to stop them from feeling guilty. It takes very little time to find a source and then rip it off and put your own label on it. But for those who don't derive an odd sense of accomplishment out of it, a continuous barrage of peer pressure does the trick.
- talmand 15y agoJust wow. A great manager does not get others to do their work. They lead or, let's see what's another word I know, "manage" other people doing their own work assigned to them. The system of cheating described can only create a stream of entrepreneurs/networkers who will ultimately have to cheat to attempt to succeed but the real world doesn't support that in the long run. They cannot be a good resource if they don't know how to actually work. I agree, Nigerian scammers would make great salespeople for industries that specialize in stealing from people.
- marshallp 15y agoI think part of the problem is we in the programming/engineering communities have a high notion of doing things right/ethics etc. However, in the real world, where money changes hands and fortunes are made it's the cheaters who get ahead/make things happen. Do you think most successful politicians, used car dealers, industry titans are not cheaters. Did Bill Gates or Steve Jobs ever cheat? (yes, all the time). The question is, who do you want to hire as your salesperson when you're struggling and have to pay rent. Mr. Ethical (cs nerd) or Mr. Cutthroat (nigerian scammer/used car salesman)?
- moonchrome 15y agoI agree that being unethical can give you an advantage over others in some cases, but ethics (or lack of) is not the issue here, it's the fact that these people are completely useless. Most of the formal education is pro forma anyway and won't give you enough knowledge to be useful in a production environment - if you choose to cheat at that level then you aren't Mr. Cutthroat you are Mr. Deadweight and your only hope of survival in any company is a dysfunctional corporate environment.
- scott_s 15y agoThe thinking and problem solving required in programming is not taught enough at universities in North America, nor overseas. Having been an undergrad, grad student, TA and instructor in two Computer Science departments in the US, I have to disagree. Good CS programs stress problem solving, and I think the US does indeed have good CS programs.
- j45 15y agoI won't disagree with you either. Nor will I reply with my academic credentials. There are exceptions to every norm. I have hired CS undergrads, graduates, TA's and instructors as employees. I do believe, based on what I've seen, that not enough institutions teach problem solving in general enough of a way to be applicable to building applications. Understanding how all the pieces of algorithms, propositional logic, technologies come together in a solution that means something to the end user is something that our CS education fails in many ways on in too many programs. Instead of strategic, spatial thinking, we are taught to focus on the same algorithms over and over in a dozen or two languages. That teaches us coding, not programming, let alone software development. Too many just learn to recognize the design patterns, let their eyes glaze over and get it done. I'm not knocking education, I had some of my greatest memories and years and experiences in Academia. It just didn't prepare me for the real working world of finding the dots, and connecting them in the way that doesn't douse or kill the business. I didn't learn to communicate with different business units in CS. I didn't learn to help people communicate what they need in a clearer enough way. I wasn't taught to market or sell my ideas to the other stakeholders in my workplace, and instead consider just having fits of rage relating to Dilbert or XSCD (?) cartoons. This is all the responsibility of my formal education; to help prepare me for the real world, and it didn't. I was given a limited set of tools to interact and interface with the real working world. But man, I sure know what an O(n) function looks like. Understanding how those details work, fit, and come together to amplify an organizations' competitive advantage, instead of dousing it in cold water is something we know far too many programmers, CS grads included, really, truly, suck at. CS grads have to go and learn that in the real world. I wasn't taught when to use agile (when the outcome is unknown) and when to let waterfall in a little (when you're doing something very familiar, standard and predictable to reach your goal). A system is really the data. No software system has any meaning, purpose, value, or impact without the data it works on. Teaching a data-centric and an experience centric approach to software development, in addition to what is already taught is critical, and I'm afraid it's simply not happening enough from the false positives from the people I've tried to hire in my business.
- eli_gottlieb 15y agoReal thinking and problem solving tends to contradict "constant ... self-development", which often (not necessarily from you but from many) seems to be a code-phrase for "learning every new fad framework that comes along." Example: web development is so damned faddish that after almost 4 years of its prominence, I have only now settled on picking one damned framework and learning it (Play 2.0 in Scala). I fully expect my newly-acquired "skill" to become obsolete within about a year. This is not fundamental problem-solving. Hell, I would say that the over-reliance on "frameworks" and "web-applications" to build all modern software on the "thin client" paradigm is itself a fundamental problem that requires more serious thought and problem-solving than most people seem willing to put in. Hypothesis: Despite the high cost of doing so, backwards compatibility must sometimes be broken.
- mquander 15y agoI think your criticism is of a matter so small that it can barely be seen. Some self-developmental things to learn that will almost never be obsolete in one year (or ten years:) - Patterns and ideas in languages that you haven't been exposed to before (e.g. continuations, or pattern matching, or actors, or dependent types, or STM, or...) - All about time-tested tools and protocols or software or media or files or hardware that you work with or on, of which there is no shortage. - Interesting data structures and algorithms, and related math. It all feeds into fundamental problem-solving, you can work in a way such that you are learning it as you go along, and it's more than a lifetime's worth.
- j45 15y agoIs web development really that faddish? With the phenomenal modern "web" frameworks (2005 onwards) available in all "web" languages that are equally as old (mid to late 90's), there are some common qualities emerging, wouldn't you say? I mean, it is if we're looking to others for validation of what toolset we're and how we're doing it -- both are largely matters of preference.
- eli_gottlieb 15y agoThere are definitely some common qualities by now, but nobody seems to actually treat the common qualities as principles, as things unto themselves. "We want 3 years in Ruby on Rails." "I've done Django for 5." "Nope."