Slashdot Mirror


"Learn To Code, Get a Job" According To CNN

An anonymous reader writes "CNN is running an opinion article that talks about Michael Bloomberg's taking part in CodeAdacemy's CodeYear program, which aims to teach average people to learn enough to work as a Software Developer by year end. I'm trying to not be elitist in judging this article and those involved, but I'm curious as to what /. thinks of this questionable plan."

688 comments

  1. Whats the big deal? by Anonymous Coward · · Score: 5, Interesting

    How does Code Academy make it any easier to learn to code, Than say documentation or a book? This is hardly a big deal, and they're making silly promises.

    1. Re:Whats the big deal? by jmorris42 · · Score: 5, Insightful

      Exactly. A lame little site with twenty little lessons on Javascript and they have had two slashdot articles already plus a shedload of legacy media coverage just because they snuck Bloomy some preIPO stock or something. Meh.

      --
      Democrat delenda est
    2. Re:Whats the big deal? by Weezul · · Score: 5, Funny

      There is an awful lot of need for javascript lackies so that real coders can do real work. bring em'. slap em' when they do badly.

      --
      The Christian religion has been and still is the principal enemy of moral progress in the world. -- Bertrand Russell
    3. Re:Whats the big deal? by next_ghost · · Score: 5, Insightful

      Pretty much yeah. Learn enough to be a software developer in a year? Not a chance. You might learn some programming language pretty well in a year but there's no way you can learn the essential skills for professional software development - debugging and breaking down even simple problems to elementary tasks. That takes years of practice because it requires your brain to rewire to allow completely new way of thinking. After a year, you won't be qualified even to work as an assistant to a code monkey, much less a real software developer.

    4. Re:Whats the big deal? by omarius · · Score: 5, Insightful

      Elitism: It's what Slashdot's serving for dinner.

    5. Re:Whats the big deal? by Nerdfest · · Score: 5, Funny

      Mmmmmm, Tasty, tasty elitism. They do say that you are what you eat.

    6. Re:Whats the big deal? by Zmobie · · Score: 5, Insightful

      Call it what you will, but the bottom line is there is no way people can learn to be a software developer with this rubbish. It takes most people years to get even CLOSE to learning proper design techniques. Even then, I see people that are Computer Science majors about to graduate that still barely grasp the concept of object oriented design, let alone anything like logic or functional programming. Hell I have been programming for 8+ years and even when I finally got into the business world I am STILL learning a fair bit. Foundation is everything, and you're not going to lay a solid one for software development in a years time unless that person is a damn prodigy to begin with.

    7. Re:Whats the big deal? by russotto · · Score: 4, Insightful

      Elitism: It's what Slashdot's serving for dinner.

      The recognition that some people are better than others at certain tasks is not elitism, it is merely recognition of reality.

      Elitism is the idea that those better people ought to rule over the other ones.

    8. Re:Whats the big deal? by omarius · · Score: 1

      Yes?

      > There is an awful lot of need for javascript lackies so that real coders can do real work.

      If the preceding comments aren't suggesting, "The people who participate in CodeAcademy won't ever amount to anything, unlike *us*," then I guess I need to read with less beer in me.

    9. Re:Whats the big deal? by bfandreas · · Score: 4, Interesting

      I do remember the dot com bust. Before that everybody and his uncle claimed to be a coder after having read HTML for Dummies and Java for Dummies. It was terrible.

      Why did they do it? Because there was gold in the hills. Proper coding takes a special kind of structured thinking. You've got a goal, you've got requirements and you need to break it down into subproblems of subproblems while not forgetting the overall goal. Not everybody is cut out to be a lawyer. Not everybody is cut out to be an artisan. Not everybody is cut out to be a business owner. Not everybody is cut out to be a coder.
      And coders are not all the same. Some thrive in the front end and are very very good anticipating how users willl use the system(which is never how they told you). Others are very good in layers that involve logic. Others are optimization wizards. Others are very good when it comes to communicating with interface owners. And so on.

      I really, really hate it when news outlets publish that there is gold in the hills when there isn't. Everybody rushes out and most of those that rush out will never make it.

      --
      20 minutes into the future
    10. Re:Whats the big deal? by Grishnakh · · Score: 4, Insightful

      You don't need people who know proper design techniques, just monkeys who can spew crappy code. And this isn't just for low-level positions either; you can get a bunch of them together and have them write totally brain-dead standards like CSS! Then they can do things like completely omit something as simple as a simple, direct way of centering something instead of having to use some weird hack with margins.

    11. Re:Whats the big deal? by Zmobie · · Score: 2

      Well sure you can throw morons at it and get something that resembles the original intent of the code, but debugging, maintaining, expanding or anything else that a real software developer might want to do becomes a god forsaken nightmare of transparent code, non-meaningful variable names and not a damn one of them knows how to document.

      If that is what a business settles for, alright have fun. When the real development companies with real developers start wrecking them in the market they might rethink their hiring strategy, because these days it is all about the maintenance of software.

    12. Re:Whats the big deal? by jo42 · · Score: 0

      Outsource it to India or China -- they'll do it for fewer dinars and add more crap to the crApp code.

      People in the US should get into the financial 'service' industry -- everyone knows that's where all the real money is.

    13. Re:Whats the big deal? by Anonymous Coward · · Score: 1

      I think you need MORE beer in you to even attempt believing these people aren't being elitist.

      The simple fact is, many of the commenters on this thread think that what they do is untouchable by a layman going to classes for a few weeks. On the other hand, they browse wikipedia and groklaw, and then feel comfortable looking down on every profession from sales to law to enforcement to management as "unskilled hacks".

      Face it, people, you love being unique, and you love being great at something, but what you do to buy your bread doesn't require more schooling or intelligence than what a lot of others do.

    14. Re:Whats the big deal? by shentino · · Score: 4, Insightful

      Elitism I don't mind so much.

      It's the exclusiveness, keeping others down.

      Someone on top should be reaching down with a hand, not shoving down with a boot.

    15. Re:Whats the big deal? by Grishnakh · · Score: 5, Informative

      It's what much of the industry has settled for. Just look at any CSS code. Or try designing a website with CSS. I have a little website on the side that I recently did some CSS/Javascript/jQuery/PHP work on, reusing some other code I found and making massive changes to it. As I have lots of experience with assembly, C, C++, and Perl, I usually don't have much trouble learning new languages. On this project, the PHP was easy. The Javascript and jQuery, also not very hard, though not quite as easy as the PHP. HTML wasn't hard of course. But the CSS, for making everything look right, and also doing some simple animations? Holy shit, what a nightmare! I've never seen anything so horribly designed in my life. Doing anything meaningful with it is basically a big hack.

    16. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      I guess I'm a pussy.

    17. Re:Whats the big deal? by DNS-and-BIND · · Score: 0

      What, they shouldn't? Just imagine how much better America would be if the smart people were in charge.

      --
      Shutting down free speech with violence isn't fighting fascism. It IS fascism!
    18. Re:Whats the big deal? by Anonymous Coward · · Score: 1

      Just you have difficulty doing something doesn't mean that everyone does and vise versa. I taught an intelligent friend how to code by working a big project with him and showing him how to break it into manageable chunks. We hired him as a lacky to clean up our lab. He was bored so i recruited him to help me with one of my projects. After about a year of working with him, The company promoted him to the position and I moved to a different area as a senior position. He has since worked at a other companies as well.

      I think most people could fill a web developer position fairly easily in a year. A person with aptitude for the subject could do much more.

    19. Re:Whats the big deal? by j35ter · · Score: 0

      better than being a dick, you insensitive clod!

      --
      Delta-Mike November Bravo Tango
    20. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      Bullshit. In a year you could easily learn enough to be a decent Jr. Developer. I know because I did it. Spent a few months learning HTML, a few months learning classic ASP and voila! Landed a job as a Jr. Software Developer. A year later was fairly proficient in C# and several years later, JAVA. Of course the requisite javascript, CSS, XML, SQL all learned along the way and OTJ. My employers have been continually impressed. I'm not ripping anyone off.

    21. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      Well, at least it's better than tables.

    22. Re:Whats the big deal? by tftp · · Score: 1

      If the preceding comments aren't suggesting, "The people who participate in CodeAcademy won't ever amount to anything, unlike *us*," then I guess I need to read with less beer in me.

      They are elitist, in a way. However it's not that bad. Out of 100 graduates of Code Academy 90 will be lowly bit pushers, barely able to put together a "Hello, World" in the original BASIC.

      However the other 10 will join the elite. There is no artificial "glass ceiling" that would forever tag all CA graduates as losers. As matter of fact, I knew someone who was a machinist of a TBM. One day he decided that he wants to become a programmer. A few months later I learn that he got a job at a bank to write MS Office macros (and they needed them by the ton.) Today he has a solid 15-year career in software.

      Perhaps VBA is not as exciting as Ada or assembly (considering their typical uses) but it's a good job; and if you can code in one language you can code in all of them, with little learning. Most languages are conceptually alike, with a few exceptions (Forth, LISP, etc.) Even BF is only hard to read because of its alphabet. Underneath it's just like anything else. Even computed GOTOs of FORTRAN are harder to deal with.

    23. Re:Whats the big deal? by Grishnakh · · Score: 2

      I really wonder about that. At least tables had a "center" property, but the morons who made CSS deleted that for some idiotic reason.

    24. Re:Whats the big deal? by Crudely_Indecent · · Score: 5, Informative

      CSS...Doing anything meaningful with it is basically a big hack.

      You can thank the browser vendors for that. Many of my design decisions are based on what it's going to take to make it look right in ALL browsers. What works right in one browser, will probably look horrible on others. Mind you, I wrote those sentences to be non-specific - in reality, all but one of the current browsers function in roughly the same manner where CSS is concerned. You can guess which one.

      Now, if LESS could become the standard...

      --


      "Lame" - Galaxar
    25. Re:Whats the big deal? by justforgetme · · Score: 1

      IIRC all elements are supposed to honor the text-align property of their parent (+inheritance) and
      a non specified div(eg:div inside a div that does not inherit text-align) is always centered.

      --
      -- no sig today
    26. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      No not really. CSS was a bit of a hack as a language. I've seen worse. Have you ever seen IBM's Job Control Language (JCL)? Compared to JCL, CSS is positively sublime. Now to be fair, JCL positively is a train wreck. As hacks go, its an absolute hack. In most languages, you have parts that when created, work with other parts of the language. Not so JCL. A single piece works as an add on to one other piece. If you want to do something similar somewhere else, you need something else over there (or there is nothing else over there). Go ahead and check wikipedia for JCL. The examples they give are *very* user friendly (try not to gag). If you cant to get better with CSS, check out the CSS Zen Garden.

    27. Re:Whats the big deal? by justforgetme · · Score: 1

      I get what you are meaning. CSS does have some design flaws especially when it comes to big projects that go through a couple of design evolutions without blank-sheeting the older designs. But I would hardy say that a skilled Dev would find big trouble, unless you put a gun on his head and demand solutions immediately.
      Css does have some advantages for:
      1) small projects (because it makes styling several specific things dumb easy)
      2) for very carefully designed projects that adhere to -almost- all RFCs.

      The problem I get most, having done many CSS implementations, is that when an -idiot- photoshop monkey gets involved, you usually can kiss #2 goodbye... I still can't believe that the barrier to call yourself a Designer in the Internet busyness is knowing PS.

      --
      -- no sig today
    28. Re:Whats the big deal? by justforgetme · · Score: 4, Informative

      Never heard of less but it looks very very interesting, will give it a try in one of my projects.
      Actually I was hoping I would stumble upon something like this eventually.
      Writing good CSS for dynamic websites can become very cumbersome programmable elements....
      (thinks of Facebook's 18MB of css...)

      --
      -- no sig today
    29. Re:Whats the big deal? by DocHoncho · · Score: 1

      Well to be fair, they didn't exactly delete it... they obfusticated it and then no-one bothered to implement it. That being said, I guess it amounts to deleting it, doesn't it?

      I've spent some time in the HTML trenches and my take on the whole thing is to hell with XHTML, use the original HTML properties when they make sense and the CSS rules everywhere else. Then again, I was lucky (relatively speaking) I was working on an intranet project (my idiot boss insisted on IE9, even though no-one used it so I targeted Chrome, Opera, Firefox, and put in IE kludges when he noticed the site wasn't working right in his useless fucking excuse of a browser)

      Did I mention I'm no longer employed at that company? Funny that. Bunch of useless gits, the lot of em.

      --
      Celebrity worship is a poor substitute for Deity worship and costs more to boot.
    30. Re:Whats the big deal? by j35ter · · Score: 1

      you obviously never talked o a cop, salesman or manager in private, you insensitive clod, otherwise you'd know how wrong you are!

      --
      Delta-Mike November Bravo Tango
    31. Re:Whats the big deal? by j35ter · · Score: 1

      You sound so Christian, you insensitive clod!

      --
      Delta-Mike November Bravo Tango
    32. Re:Whats the big deal? by Grishnakh · · Score: 2

      Holy crap, I just took one look at LESS and already I like the sound of it. They mentioned another glaring item missing from CSS: variables. WTF were those idiots thinking; I have to specify the exact same RGB color codes over and over, instead of just specifying them once as variables. The only problem is that it's yet more stuff for the user to download and run on the browser. Pretty soon we'll be downloading 10MB of Javascript just to visit a simple website. This needs to be built into the browser.

    33. Re:Whats the big deal? by shentino · · Score: 1

      There's nothing wrong with being rich as long as you don't try to keep other people poor.

    34. Re:Whats the big deal? by TheP4st · · Score: 1

      reply to remove accidental troll mod

      --
      "I have downloaded hundreds and hundreds of records, why would I care if somebody downloads ours?" Robin Pecknold
    35. Re:Whats the big deal? by hairyfeet · · Score: 2

      Well I'd say this BS is just part of the greater lie which is "education will fix the economy" like you can take millions of 104 IQ workers, wave a magical education wand, and BAM! Suddenly they are all engineers. In the end we have to face the fact that we have millions of low skilled workers and no low skilled jobs that can actually feed and house a person in the USA, much less a family like in the days of the factory. Did you know we lost 42,400 factories since 2001? That's NOT a typo folks, that's millions of your fellow Americans that most likely will never work at anywhere close to that pay again and will frankly be lucky, depending on where they are, not to end up in a tent.

      We are just gonna have to face the fact we can't educate our way out of losses like that, nor can tax breaks to so called "job creators' make up for anywhere near those kinds of numbers. what do we do with all these people? put them in camps? I'd argue the only reason we didn't have our own Arab spring is the dems throwing benefits at the unemployed but we simply can't keep that up without rampant inflation.

      I have a feeling though as it wears on we'll see more total horseshit ideas like this simply because politicians don't want to bite the bullet and face the facts that our years of giving tax breaks for offshoring and running the whole country on credit has run us into the ground and there is NO way to get out that isn't gonna hurt everybody, 1% and 99% alike.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    36. Re:Whats the big deal? by nbauman · · Score: 4, Interesting

      I'm a science nerd, and I've learned a little bit of computer programming over the years.

      Learn to code, get a job? Ridiculous.

      I programmed some scientific formulas in FORTRAN in college.

      I wrote a program in Business BASIC to replace my bookkeeping system. (It was more trouble than paper. I went back to paper.)

      During the DOS days, I programmed elaborate batch files to zip and save my backup files on floppy disks. I wrote elaborate macros for XyWrite and WordPerfect, which worked pretty well. I wrote Lotus 123 macros to finally automate my bookkeeping system.

      When the Internet came, I created my own web site in HTML.

      Even during the hottest computer bubbles, I've never heard anybody say, "We're desperate! We need somebody who knows a little bit of HTML!" Or any other program you could pick up in a week of all-nighters.

      I looked into computer programming because it would have been fun (and some people were getting really rich). But I couldn't get a job with my introductory skills.

      I figure that it would have taken me at least six months to a year to learn some programming-related skills well enough to earn my keep as you trained me.

      If you paid my expenses for a year, gave me the hardware I needed, gave me access to people who knew how to teach computer concepts and guide me in self-instruction, surrounded me with people who were obsessed with doing the same thing, and we spent all our time working on computers, talking about computers, meeting smart computer people, and helping each other with our problems (with an occasional break for a party) -- I think I would have been a competent programmer at the end. I might even have been good. Maybe very good.

      That sounds a lot like what a college is supposed to do. The main difference is that in the U.S., you pay your own (exhorbitant) college expenses, and your own living expenses besides. If you want to make a mid-career transition, you have to spend your retirement fund. That's in contrast to many other countries. Maybe that's why Linus Torvalds came from Finland. Maybe that's why German workers are making twice as much as U.S. workers.

      (NYC Mayor Bloomberg is really hypocritical. He's talking up these low-budget old-fashioned online textbooks at the same time that he's raising tuition and cutting staff salaries at the City University of New York, which is NYC's real engine of innovation, science, technology, engineering, high-tech industry, economic development, all that good stuff http://en.wikipedia.org/wiki/List_of_Nobel_laureates_affiliated_with_the_City_University_of_New_York . His MBA-style educational fads are also destroying the public education system. He's destroying the neighborhood public library. Lesson for Bloomberg: When you've got something working very well, don't destroy it.)

      Fortunately I have science skills in other areas (biomedical) that were also fun, where I could advance my skills and make a living. Unfortunately, I'll never have the satisfaction of writing a really good computer program. But I did learn how the cell works, and the cell nucleus, the cell membrane,
      DNA, and what causes cancer. I've met Nobel laureates and cancer researchers. That's a good life too.

      And there are more girls in biology.

    37. Re:Whats the big deal? by j35ter · · Score: 0

      To be rich in a world of limited resources, you have to make sure that *you* get the wealth instead of the poor bastard; so, to keep being rich you have to steal from the poor, you insensitive clod! :)

      --
      Delta-Mike November Bravo Tango
    38. Re:Whats the big deal? by TimMD909 · · Score: 5, Funny

      "...in reality, all but one of the current browsers function in roughly the same manner where CSS is concerned. You can guess which one."

      A shout out for http://en.wikipedia.org/wiki/Lynx_(web_browser)!

    39. Re:Whats the big deal? by xtracto · · Score: 1

      Oh come on men. We already had a wave of "unskilled programmers" doing software some time ago with the introduciton of Visual Basic. That did not play very well (or maybe it did, for all the *real* programmers that had to fix the things initially written in VB).

      Sure, you can learn "to code" (the minimum would be to understand what is an INSTRUCTION, IF and WHILE), but stuff like unti testing, source control, algorithms and design patterns (among others) is what makes a real valuable developper.

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    40. Re:Whats the big deal? by narcc · · Score: 2

      my idiot boss insisted on IE9, even though no-one used it so I targeted Chrome, Opera, Firefox

      ...

      Did I mention I'm no longer employed at that company?

      Gee, I wonder why...

    41. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      These people would not be using proper design techniques. They'd literally be taking someone else's design and doing a direct implementation, probably by putting together mostly pre-existing modules and writing very little "actual" code themselves.

    42. Re:Whats the big deal? by ajo_arctus · · Score: 5, Insightful

      Your problem with CSS appears to be that you aren't familiar enough with it to use it effectively. That's expected, and the same would be true for any sufficiently complicated system. Of course CSS has its faults, and of course there are alternative options that might have worked better, but it doesn't matter, because CSS works and is good enough. That is all that was required of it, and it is why it is used. As it happens, I'm not aware of any other layout system that gives you the power of CSS and HTML yet remains simple.

      Maybe it's easier for me, because I started programming web-centric software at about the time CSS arrived, so I've lived through the evolution and it seems perfectly natural to me. That said, I have the same problem moving to any new language -- it takes me at least a few months of messing around on little side projects before I'm comfortable enough to take on a real project, and then at least another 6 months before I feel I am truly proficient. You seem to want to skip all of that and go straight to mastery, and are blaming the system/technology because you can't.

    43. Re:Whats the big deal? by Bloomy · · Score: 1

      Exactly. A lame little site with twenty little lessons on Javascript and they have had two slashdot articles already plus a shedload of legacy media coverage just because they snuck Bloomy some preIPO stock or something. Meh.

      The opportunity to be a 133t h4x0r in 20 lessons was too good to pass up.

    44. Re:Whats the big deal? by sourcerror · · Score: 1

      Those "monkeys" will got thrown out by HR without blinking during prescreening. It's definitely a scam*, even if the organizers have the best intentions.

      * judged by how it's advertised, and what the outcome is

    45. Re:Whats the big deal? by St.Creed · · Score: 1

      Skilled Devs can program anything with Turing machines, if they have to. That doesn't mean it should be the default.

      Point is, CSS is a programming language, designed by people who thought it wasn't. So we're left without variables, constants and other items that would make life much easier all around. You could use XSLT and XML to style everything, but that solution has its own problems.

      --
      Therefore, by the (faulty) logic you're using, you're just a cow with a keyboard - osu-neko (2604)
    46. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      I first read that as Tactical Ballistic Missile, thanks for the wiki link.

    47. Re:Whats the big deal? by podmf · · Score: 3, Insightful

      Your problem with CSS appears to be that you aren't familiar enough with it to use it effectively. That's expected, and the same would be true for any sufficiently complicated system.

      Mod my parent up. The vast majority of the anti-CSS comments here appear to come from hubris-sufferers who couldn't be bothered to research the language or the browsers properly. Truth is, practically all serious problems and divergencies come from one family of browsers (we all know which). If you understand how to put them into their standards modes and how to control their ridiculous hasLayout property, all of the problems described so far go away instantly.

    48. Re:Whats the big deal? by pitzG · · Score: 2

      Its a huge problem out there, and the problem is largely the creation of the employers who have eliminated (or outsourced) all of the entry-level positions, and merely expected CS grads to go from being new grads, to being people with 5-8 years of experience, delivering production code the first day on the job (they call this, "hitting the ground running"). Some ethical grads basically go into an interview where this is the expectation, and politely explain that it takes time to familiarize oneself with the environment at hand, coding practices, and the overall schemas in use for the system. The less-than-ethical grads go in with an attitude that they can literally do anything, churn out code the first day on the job, quality or applicability be damned. Guess who gets the job? And guess what type of candidate has basically been locked out of the CS job market for much of the past decade? See why we have a problem? Bring back professionalism to the 'profession', with senior employees mentoring the newbies, proper salaries so the new employees don't have to subsist on Krap Dinner living 5 to an appartment, and workplaces with proper offices, not cube farms -- and the quality and quantity of innovation and code is certain to increase.

    49. Re:Whats the big deal? by pitzG · · Score: 1

      Yeah it does seem unlikely that Torvalds could have achieved what he achieved, if he was growing up in the United States. For starters, your typical Stanford attendee is looking at $50k/year in tuition and living expenses (at least), which means that they're coming out of school with $200k in debt. Torvalds could sit around, as a grad student, coding Linux, as he had the comfort of knowing that if his project failed, he could easily move into industry and get a job as a proprietary programmer, computer scientist, software engineer, etc. Contemporary graduates, OTOH, often don't even receive replies from employers to their job applications and a few years out of the workforce working on a personal project is basically the kiss of death to a programming career (under that $200k mountain of debt!). If we want more startups, and more guys like Torvalds to start projects, then the entire culture has to be overhauled, including, but not limited to, providing career stability for domestic CS and IT graduates. Government policy needs to be oriented towards pushing salaries up for IT and programming professionals, not suppressing them through H-1B and other guest labour scam programs. Firms need to be encouraged to provide healthy pay packages for new grads especially, and housing prices need to be affordable so that the younger crowd of IT people and engineers more broadly can afford to tinker, can afford to create things in their garages. Interested High school students need to be given opportunities to come into IT/engineering/manufacturing workplaces on summer jobs -- much like Steve Jobs and Wozniak were able to do at HP in the 1970s -- giving them inspiration to create what became Apple computer! Anything short of the above, and quite frankly, I fear the US will have squandered the future of its past leadership position in IT to countries and to companies that 'get it'.

    50. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      I'm sure I'm much better than you at understanding what goes on inside your brain. Right down to the chemical level. So, just send me all of your medical records, and I'll give you your first task. ...Don't worry. This will be fun!

    51. Re:Whats the big deal? by Hognoxious · · Score: 1

      I really, really hate it when news outlets publish that there is gold in the hills when there isn't. Everybody rushes out and most of those that rush out will never make it.

      An old proverb says that the only people who make money in a goldrush are the ones selling shovels.

      Maybe the ones who run saloons, gambling houses and other, ummm, entertainments too. In fact, forget the gambling. And the saloons.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    52. Re:Whats the big deal? by Hognoxious · · Score: 1

      Just you have difficulty doing something doesn't mean that everyone does and vise versa.

      True. For example, some people have a fucking clue about how to write Latin.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    53. Re:Whats the big deal? by TaoPhoenix · · Score: 1

      Wait, in 2012 is it finally safe to say that CSS is confusing and not the L33T new thing of 2003? I certainly would never be a developer, but I amuse myself with a cute little homepage with my favorite link and draft maybe-blog fragments. I mostly understand tables.

      But then various people told me years ago that "CSS is the future!" I took one look at it and it looked like cuneform to me.

      --
      My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
    54. Re:Whats the big deal? by joss · · Score: 2

      Amen brother.

      I have a CS/AI degree, 20 years experience in C/C++/java/Lisp/etc .. but css, save me. Complex css menus that work in ie6+, fuck me.. that made my brain hurt worse than coding efficient but stable parallel matrix inversion in a mix of OCCAM/C on a mix of sun workstations and transputers or any other hairy crap I've encountered.

      You do hear a lot of elitist distain for web monkeys, but I'm wondering how many of those people have truly got their hands dirty in webdev. Sure, php is mostly derp but it has pitfalls just as nasty as c++, while css hackery is just plain awful. Then there's the language proliferation, one has to deal with at least: html/css/javascript + 1 server language + sql + the platform issues. There's a lot of details for devils to lurk in.

      --
      http://rareformnewmedia.com/
    55. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      I looked at that using NoScript. It *was* a lot less...

      Why should a style specification require JavaScript?

    56. Re:Whats the big deal? by skovnymfe · · Score: 1

      As soon as you build it into a browser, the browser vendor has to maintain it. Then you never know which version is installed or whether it's even supported in , paving the way for the kind of clusterfuck that javascript already is.

    57. Re:Whats the big deal? by skovnymfe · · Score: 1

      I meant to write CSS, not javascript. But I suppose we can blame javascript too.

    58. Re:Whats the big deal? by JoeMerchant · · Score: 1

      Call it what you will, but the bottom line is there is no way people can learn to be a software developer with this rubbish. It takes most people years to get even CLOSE to learning proper design techniques.

      Sure, all you say is true, but... can they fill a need? Can they scratch an itch and get paid for it? They don't have to get Linux kernel patches accepted on the first submission, maybe the marketing guys just want this button on the website to bounce like that one on LOL Catz does - unlike kernel patches, you can actually get paid for that.

      I've lost count of the number of times I set something up to be so drop-dead simple that my customer should have been able to tweak it to meet their needs without recalling me for another 4 hours of paid coding time - and they almost never do tweak it, they call me back, sometimes because they've had a new idea for me to implement, sometimes just to explain to them again how to press F1 for help and read the paragraph on how to X.

      If coding skool teeches the kiddiez how to not be intimidated by komputerz, step up with some examples of what they can do, and get hired - what else do you expect?

    59. Re:Whats the big deal? by JoeMerchant · · Score: 1

      Thankfully, all my "obsolete" web pages that I coded back in 1997 still render the same on these new elite browsers, even if half the tags are deprecated now.

    60. Re:Whats the big deal? by JoeMerchant · · Score: 1

      It's what much of the industry has settled for. ... Holy shit, what a nightmare! I've never seen anything so horribly designed in my life.

      Aren't we concerned about keeping unemployment down? I mean, if a team of 10 elite coders earning $130K/year each can maintain a corporate code base, isn't it really better for the national economy, and the IT sector in general, if the same job is done by 100 monkeys each making $26K/year?

    61. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      You had me at "more girls".

    62. Re:Whats the big deal? by JoeMerchant · · Score: 1

      Elitism: It's what Slashdot's serving for dinner.

      The recognition that some people are better than others at certain tasks is not elitism, it is merely recognition of reality.

      Elitism is the idea that those better people ought to rule over the other ones.

      If I think that coders who know architecture, security, testability, and portability principles should be the ones who are advanced into management instead of the frat boys who made a website, am I being an elitist, or just unrealistic?

    63. Re:Whats the big deal? by JoeMerchant · · Score: 1

      And there are more girls in biology.

      Not in the medical device industry, at least not the R&D branch... go into animal research (you know, cutting them open, inserting all kinds of invasive instrumentation in their brain, heart, liver, and what have you, running an experiment, and then killing them with an injection of KCl) that's where the girls are. There, and marketing.

    64. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      And there are more girls in biology.

      If there's one line that got you your "+5, interesting" it must have been that one.

    65. Re:Whats the big deal? by next_ghost · · Score: 1

      It's not about coding being difficult, on the contrary. Coding is so simple to pick up that most people get the "I'm the best coder in the world" mentality early on. But the real problem is what comes afterwards. You have to write (and especially READ) several million lines of code. You have to run into every single beginner mistake to understand that it's a mistake and figure out how to do it right next time. Each mistake has to literally bite you in the ass or you won't notice it's there. A year is not enough by a long shot.

    66. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      As a developer with 12+ years experience you took the words right out of my mouth. I too lived through the very development of html, css, and everything in between. It doesn't just work, it is designed to achieve a specific outcome with the least work possible (assuming you use it correctly).

      Desktop programming which I also do, is an entirely different model and the two should not be expected to function, work, or be used/approached in the same manner. This is one of many reasons why I HATE ASP .NET because it is absolute garbage and misuses everything css/dhtml was designed to work as.

    67. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      For what's worth, LESS is awesome. As a poster up the the thread said, most of the web stack is OK, but CSS is a fucking nightmare. Now that I've got LESS (and Twitter's Bootsrap for that matter) I'm actually starting to feel slightly productive doing web development. It gives you variables! You can calculate gaps and offsets and sizes based on logical relationships, so that things don't completely fuck up as soon as you change something by a pixel.

    68. Re:Whats the big deal? by next_ghost · · Score: 1

      So let me ask you this: What's your biggest past coding mistake that you're aware of and how long did it take you to stop making it?

    69. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      pitzG, have you met my good friend Mr Paragraph?

    70. Re:Whats the big deal? by mjr167 · · Score: 1

      I didn't get the impression the CNN piece was implying you would be a professional software developer, just able to do some basic script type stuff, etc which would be useful in daily life. For example, I'm not a contractor, I can hang a shelf on a wall and patch drywall. It is valuable to know how to read and write even if you aren't writing publications. Non-professional photographers know how to take pictures. Knowing basic coding skills is useful, even if you don't write software professionally. It would let you write small stuff to help you with day to day tasks. Normal people should know how software and computers work. It shouldn't be a black box filled with magic smoke.

    71. Re:Whats the big deal? by ThinkWeak · · Score: 1

      When I was in school, there were any number of students signed up in coding classes because "there was money in computers." Numerous Comm, Poli-Sci, and English majors were attending. That being said, I do know of quite a few individuals in my current company that were hired into tech positions with English or Communication backgrounds, but have zero tech skills.

      They can talk their way into tech positions, but end up causing a lot more problems once they're there. I'm all for people learning new skills, but take the time to learn them. It's great when they openly admit they have no idea what they are doing. By great, I mean that it's nice knowing I shouldn't have to worry about my job - which is fixing the problems they cause.

    72. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      I disagree. I am fairly familiar with CSS, I work with it every day, while I would not consider myself an expert.

      The problem is that it is missing key components that would make life so much easier. The biggest issue, is that everything is or. Unlike in most positioning systems, horizontal and vertical are coupled. Something is either floated or it is absolute.

      It would make so many things infinitely easier if you could specify a specific width, a specific horizontal position, and then omit a vertical position so that it would float down the page naturally. Or vice versa.

      Just one example of something that is intuitively useful after a day in CSS that was just not thought of.

    73. Re:Whats the big deal? by Zmobie · · Score: 1

      That is not what they are touting though. A person doing that is a code monkey not a software engineer.

    74. Re:Whats the big deal? by Aeros · · Score: 1

      but...they SAY you can learn to code in only 3 weeks! Sounds like a hell of a deal! Why has it taken most of us years to learn?

    75. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      Perhaps if it didn't require javascript to work, then maybe so.

    76. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      I already recommended it to someone. I think it looks like a great way to get your feet wet. Most people find programming scary and those books you are thinking about will likely scare them away. This guys starts them off nice and slow with a gui. It isn't designed for people like us, but rather people who find the terminal frighting.

    77. Re:Whats the big deal? by justforgetme · · Score: 1

      very cumbersome programmable elements....

      oh... I forgot a word there

      very cumbersome without programmable elements....

      --
      -- no sig today
    78. Re:Whats the big deal? by Zmobie · · Score: 1

      While I do see your point, the bottom line is that is progress. Industry automation and streamlining is a big part of an engineers job. Granted we do have a lot of low income workings losing jobs, but that is the nature of the beast and the only way to fix it is encouraging those workers to get educated or move to fields with higher demand.

      As much as I hate to admit it, we can't slow down country progress just because that keeps unemployment down. There are others ways to keep those people working in general with at least comparable wages and such without saying "slow down, your removing the need for my job!" Government subsidies, loans, grants for education are exactly what that is geared towards. It comes down to we need a mix of getting these people that are out of a job benefits, while encouraging them to train in fields with more demand.

      Some could argue maybe they "like" their job, and while that might be true for some, a lot of low skill/wage works do it because it is a paycheck and nothing else. They would much rather be doing something else but either are too lazy to find a way into it or are in the unlucky bunch that don't actually have inroads to a job they would like to do.

    79. Re:Whats the big deal? by Zmobie · · Score: 1

      Too many typos, god it is early in the morning....

    80. Re:Whats the big deal? by ShavedOrangutan · · Score: 1

      Even then, I see people that are Computer Science majors about to graduate that still barely grasp the concept of object oriented design

      Object Oriented Design isn't part of a CS program. Unfortunately.

      --
      Godaddy is a scam and a ripoff.
    81. Re:Whats the big deal? by jedidiah · · Score: 1

      > The simple fact is, many of the commenters on this thread think that what they do is untouchable by a layman going to classes for a few weeks.

      That's true of most disciplines actually. This even includes things like "skilled trades" that require no special post-secondary education.

      There's just this pervasive tendency to try and devalue ANY skill or professional service. A side effect perhaps of the corporate tendency to devalue everyone. It's not merely limited to computing.

      Perhaps there's just a high enough incidence of Aspergers within programmers that some of us will dare to state what everyone else keeps under their breath.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    82. Re:Whats the big deal? by Zaphod+The+42nd · · Score: 1

      "Learn to code, get a job" is misleading. But the idea that the everyman should have a basic understand of at least what programming IS and some of the basics of how it works and how it does what it does can be very beneficial, being so surrounded by software. Its unrealistic for everybody to write their own shell scripts, but we can at least teach people enough so they aren't totally in the dark. Then they'll have more patience with us when they run into a bug, instead of wondering why programming "takes so darn long, since all it is is just typing."

      --
      GCS/MU/P d- s:- a-- C++++$ UL++ P+ L++ E+ W++ N o K- w--- O M+ V- PS+++ PE Y+ PGP t+ 5- X R++ tv+ b++ DI++ D++ G+ e++ h-
    83. Re:Whats the big deal? by tehcyder · · Score: 1

      Elitism: It's what Slashdot's serving for dinner.

      The recognition that some people are better than others at certain tasks is not elitism, it is merely recognition of reality.

      Elitism is the idea that those better people ought to rule over the other ones.

      Elitism is also the belief that what you do is uniquely brilliant and that ordinary mortals are incapable of following in your footsteps. It's not political, it's more of a psychological or moral outlook.

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    84. Re:Whats the big deal? by tehcyder · · Score: 1

      There's nothing wrong with being rich as long as you don't try to keep other people poor.

      But you can only have really rich people if you also have really poor people. Whereas if you aim for everyone just being comfortably off you get a fairer and more pleasant society.

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    85. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      What's with "nerds" nowadays?

      Do you really have to include a Wikipedia link for Lynx? This is just sad.

    86. Re:Whats the big deal? by rock_climbing_guy · · Score: 1

      Douglas Crockford says that Cross Site Scripting is abbreviated XSS, because CSS would be confused with "Crappy Style Sheets".

      --
      Wh47 d1d j00 541, 31337 15n't t3h r0xor5 ne m0r3???
    87. Re:Whats the big deal? by Grishnakh · · Score: 1

      It looks like a good idea at first, but in practice you end up spending endless hours tweaking stuff trying to get it to go where you want it to because it's so broken.

      It's a good idea in theory, but in practice it's a horrible implementation. That "LESS" thing that someone else pointed to in this thread looks like a good improvement, however, as it lets you use variables, perform simple computations, write things in a way that the hierarchy is more clear, etc., things that were stupidly left out of the original. CSS looks like a classic case of design-by-committee. Notice that (if I understand properly) ALL the other web technologies out there that work with it are not: PHP was basically written by some guy that wanted a way of easily scripting backend stuff on a webserver; Javascript was written by some company; HTML was descended from SGML which some guys at a university made; but CSS appears to have been written entirely by a standards committee, rather than being adopted by one later as is the case with most other standards.

    88. Re:Whats the big deal? by Grishnakh · · Score: 1

      No, you just have the standards committee adopt it as a standard, and then all the browsers build it in however they want (probably by rewriting their CSS-parsing engine, which is much faster and less resource-consuming than parsing less.js in the Javascript engine and applying this to the page's CSS after-the-fact). Isn't that the way most other standards get into place? They're not normally written by the standards committees, they're just adopted by them. CSS appears to be a big exception to that for some odd reason, and it shows.

      As for Javascript, I've heard a lot of complaints about it, but I've never heard much about different incompatible versions in different browsers. It'd be pretty hard for us to have modern webpages without it being built into browsers.

    89. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      If if have a senior engineer and/or a solid project manager the junior position doesn't and shouldn't know all of the complex structures. They should be able to perform the task explained to them. I think 1 year is plenty of time, I'm working with two guys I was able to train and get paychecks for after 8 months. Are they going to write their own framework? No. Are they going to create functions that serve the purpose of my design, then be able to integrate them to complete the design? Yes. They have and continue to do so.

    90. Re:Whats the big deal? by eddy+the+lip · · Score: 1

      I'm a science nerd, and I've learned a little bit of computer programming over the years.

      ...

      I figure that it would have taken me at least six months to a year to learn some programming-related skills well enough to earn my keep as you trained me.

      I think this is something that's key in the whole "Learn to X in 24hrs!" thing. You've gone through the process of learning a field. Anyone that has has a proper appreciation of what it means to know something.

      I'm all for more people getting their feet wet coding, getting a feel for the basics. They might find a life-long passion, or they might just gain a better appreciation for a bit of technology that will affect the rest of their lives. Anyone that has had to really learn something, though, knows that it takes more than a few weeks to get an understanding deep enough to be professionally useful, regardless of the profession.

      This initiative is at best misleading, filled with false hope and eventual disappointment.

      --

      This is the voice of World Control. I bring you Peace.

    91. Re:Whats the big deal? by Slashdot+Parent · · Score: 1

      CSS itself is great, and Javascript is a great language, in my opinion. It's the implementations on all of the browsers that are a nightmare.

      I don't know how anybody can keep straight which magic incantation works on which version of which browser, but more power to you guys. It's not something that I find to be worth killing brain cells over, though. I'd rather just drink a few beers.

      --
      They don't grade fathers, but if your daughter's a stripper, you fucked up. --Chris Rock
    92. Re:Whats the big deal? by Slashdot+Parent · · Score: 1

      I don't know how anybody keeps straight which CSS and Javascript magic incantations work on which version of which browser.

      I'm not even joking when I say that I think that CSS and Javascript are both great technologies, but only if you confine yourself to reading the specifications. Once you try to actually do anything with them, you have just unleashed a massive platform-dependent shitstorm on yourself.

      --
      They don't grade fathers, but if your daughter's a stripper, you fucked up. --Chris Rock
    93. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      I do remember the dot com bust. Before that everybody and his uncle claimed to be a coder after having read HTML for Dummies and Java for Dummies. It was terrible.

      I'm still cleaning up code that was crapped out during that timeframe. Heaven forfend it happen again.

    94. Re:Whats the big deal? by scot4875 · · Score: 1

      Just look at any CSS code.

      CSS isn't code -- it's not even markup. Do you know what code is?

      But the CSS, for making everything look right, and also doing some simple animations?

      Change the x/y offsets and change the animation frame? You know, the same way it's done in every environment?

      CSS is pretty damn simple, but if you have better ideas on how to style block elements, I'm sure people would be happy to hear them.

      --Jeremy

      --
      Jesus was a liberal
    95. Re:Whats the big deal? by Grishnakh · · Score: 1

      CSS isn't code -- it's not even markup. Do you know what code is?

      Go here; there's many mentions of "CSS code".

      Go here to learn what "code" is. Obviously, you have no idea.

      "Code" doesn't exclusively mean "Turing-complete programming languange".

      Change the x/y offsets

      x/y offsets? Like in pixels? I thought the whole point of markup code (there's that word again!) was to eliminate the need for tying layout directly to the resolution of the output device. Do you see PDF or PostScript code specifying positions in pixels? Certainly not.

    96. Re:Whats the big deal? by LowerTheBar · · Score: 1

      I have been in a position where I had a number of poorly trained "code-monkies" doing a bunch of brain dead type of simple coding...unfortunately what typically happens is I spend all of my time explaining what needs to happen, writing lengthy, dummed down documents to explain simple processes, reviewing/correcting code, rewritting large sections of poorly developed code... basically if I did it myself, it would have been much quicker and I would have more time to do what really needs to be done. All in all, I have had bad experiences in situations like this

    97. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      As it happens, I'm not aware of any other layout system that gives you the power of CSS and HTML yet remains simple

      PostScript or TeX. Both lower level then CSS, but very simple to use and vastly more powerful/useful/versatile then CSS. Some of the function libraries built upon Postscript or TeX are on the other hand very complicated and hard to use (especially if you would like to expand their scope).

    98. Re:Whats the big deal? by Ouchie · · Score: 1

      I have tried to explain the value of understanding how to code and the software development process even if you are not planing on becomming a software engineer. I liken it to the benefit of anyone going into business having a basic understanding of accounting and the legal process. While it may not be your job to engineer system wide solutions, an understanding of code can make you more efficient at your job.

      My employers have always been amazed how I can obtain levels of productivity above and beyond that of my prececessors. I do most of this by using C#, VB or VBA and an indepth knowledge of Logic. I leverage the common tool most offices have (MS office) to shave time off every function of my day.

      My success comes from the fact that I am a coder, although I don't market myself as one. I grew up in the information age my first computer was the IBM PC (1984). I started coding as a child using basic and quicky moved to Fortran, Cobal and beyond. I view computers as a resource not a tool. A tool has a function, a resource is raw and can be leveraged using tools to perform many functions. I don't see a computer for what it does, I try to ask what can it do?

      Technophobia plagues our society even today, 40 years into the computer age. The thing that shocks me is the number of people who assume that computers are for someone else, the smart and techie. I think this is what this program is trying to teach. Maybe you'll never become a software engineer but you can still learn to code and create value even in a basic office job. A few years down the road from the learning experiance you may find yourself as a software engineer, or maybe just a manager like me.

      --
      "Of all the things I've lost, I miss my mind the most." ~Ozzy Osborne
    99. Re:Whats the big deal? by hairyfeet · · Score: 1

      But you sir are falling for the same bullshit that every man CAN be educated to a level high enough to constantly earn a seat in a game of IQ musical chairs and I'm arguing that is not the case. What do you do with those that simply can't be educated beyond a D level position when you've outsourced or brought in illegals for everything lower than a B class job? Put them in camps? Before you could put them to work in a factory or in construction where if they had a strong back they could feed their family, not anymore. And i'd argue that unlike previous technological advances, which created more jobs than it cost the machines and third world labor simply make most of these people useless to society as a whole.

      So what do you do? A man isn't gonna just go crawl off into a corner and die you know, what you'll get is a rampant increase in crime as the legal ways to stay afloat simply won't exist. look at IT where you have 300 guys going out for the same job simply because you can get an Indian with a half a dozen degrees for under $20k a year. Our throwaway society is soon gonna be overloaded with throwaway people simply because they don't have the mental capacity to become doctors and lawyers and most of the low skilled jobs are either overseas or are being done by illegals making a couple of bucks an hour under the table, so what do you do? you DO realize if the fed broadcast the ACTUAL numbers, the ones where you count those that have run out of benefits, we are talking 30% unemployment is some places? Do we build shantytowns like the third world countries? What?

      Because I'd argue you have MAYBE 30% that can be educated to a C level MAYBE half of those can be educated to B level and MAYBE one tenth of those can go up to A level, and then you have to factor in the rampant inflation of education making it so many will NEVER be able to pay back their loans or get out of debt. Mark my words the next bubble to pop WILL be the education bubble, with millions defaulting simply because there weren't any jobs that would pay well enough to eat AND pay off their massive loans. Hell you have doctors filing for bankruptcy at never before heard of numbers simply because the cost of insurance and the hundreds of thousands in student loans means they simply can't dig their way out of the red.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    100. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      If the U.S. had dropped refrigerators instead of bombs Vietnam could have been a token capitalism instead of a token communism.

      The ultra right wing line is that they made it themselves, the prospect of dropped refrigerators scares them on an existential level.

    101. Re:Whats the big deal? by nbauman · · Score: 1

      I guess it depends on the field. There are a lot of women in cell biology. The easy pickup line is, "What protein are you studying?"

      I must admit that I can count the number of women engineers I've met on my fingers.

    102. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      You are slow?

    103. Re:Whats the big deal? by Zmobie · · Score: 1

      I can agree that we should want people to have an understanding of basic programming, but it requires some decent logic skills. Anyone who "wonders why programming take so darn long, since all it is is just typing" probably won't learn jack from anything related to programming because if they thought it was that simple why the hell are so many people jealous of the kind of money programmers can make when they logical should be able to do the same if programming is just typing.

      The inherent issue is most people don't CARE about learning the basics of programming, they just want to make money off of a skill that not everyone is suited to develop. I can't generalize everyone that isn't a programming as being guilty of this, but a large portion of them are this way. Hell, I have IT guys that still wonder how the hell software engineers do it. Even some other engineering disciplines I have had people straight up say, programming is too hard (granted not a huge number, but still a decent few).

    104. Re:Whats the big deal? by Zmobie · · Score: 1

      No it is more the idea that everyone that wants to better themselves will do it. In the majority of cases it is not that a person simply cannot be educated beyond the D level you refer to, it is that they don't want to try hard enough. I agree that there are some people in a shitty ass situation where they have no way of bettering themselves and there may be a good number of them, but there are a lot more that just want the benefits without putting in the effort. I am part of the young generation right now and I still see shit loads of people act exactly that way and it fucking disgusts me. There are real people that need help and these other jobs and what not, but you have the bad eggs ruining it for them.

      To address your other issues, your beef is more with societal norms and large scale business practice than anything. Education can help a great many people with their problems, no not all people but there is no end all be all solution. The rest of it is issues that educators can't really control. As many studies have already shown, people with the higher level of education generally are not way smarter than everyone else, they are just more committed to getting the higher education levels.

      And while education costs are rising, if you do some research and look into a field that you like and that at least has some real application you can fight that massive debt off for the 20 years it takes for the government to automatically forgive those loans (there are also hardship deferment programs that actually work and are used for this reason too). I disagree that the "education bubble" will bust. Hell you can even look at historic trends to discredit that assumption because college enrollment and generally education numbers tend to go up significantly in the middle of and shortly after any kind of recession. We never did hit the levels of the great depression or anything like what most of the politicians want you to believe (and they want you to believe the other party is responsible for it, hint hint, both sides are full of shit).

      Bottom line is lots of people can get an education IF they try and IF they actually go to something worthwhile, not this bullshit that these fucks are peddling. The rest, is just a societal rant and honestly, kind of off-topic.

    105. Re:Whats the big deal? by Lord+Juan · · Score: 1

      I am going to try this about right now O.o

    106. Re:Whats the big deal? by dierdorf · · Score: 1

      I hate to disagree with all the "it can't be done" mockers here, but IT CAN BE DONE. IBM used to have a program for turning non-tech employees into programmers -- secretaries, factory workers, etc. We even had an accounting manager once. We did it in FOUR MONTHS. It was sixteen weeks, 16 hours a day, 7 days a week. It wasn't all class time, of course, but with the homework and reading assignments every day that's what the time investment boiled down to. Our motto was "Wave goodbye to your friends and families and tell them you'll see them in four months." We actually had several students who rented an apartment and literally moved out of their homes for the duration.

      There was no pressure -- every Friday we gave a test, and if you passed it you got to show up on Monday. Otherwise it was back to the assembly line or whatever. We got used to rounding up students from the rest rooms where they had been barfing while waiting for their tests to be graded.

      IF AND WHEN they graduated, they were given the EXACT same job as a new college graduate with a 4.0 in CS from MIT, and whoever did a better job got promoted first. I taught this class twice -- well, I taught 1/2 of each class; we had two instructors. That's 15-20 hours of lecture a week from each of us, so the load on the instructors wasn't exactly light, either!

      After one class had wound up, I can remember getting a call from a friend who was the manager of a programming department.

      "Did you just stick me with this 'Susan Smith'?"

      "Yeah. She's great. A real star. What's the problem?"

      "Do you have any idea what you did to me? I have to come up with a salary plan for her to triple her salary within a year! You want to try to get that past HR?"

      (I lost touch with her about four years later, but 'Susan Smith', ex-minimum-wage employee with a GED, was already making more than I was.)

      BTW, we were teaching C, not any of this wimpy new stuff.

      If you calculate the hours, in those four months the students actually received a full four years of computer science instruction and homework. They just didn't get any of the history and foreign language and stuff that a college would have made them take.

      I will agree that we were cherry-picking intelligent and VERY highly motivated students, but I call BS on anybody who says the job is impossible.

      --
      -- John Dierdorf, Austin TX
    107. Re:Whats the big deal? by Zmobie · · Score: 1

      That is by far an exception and not a rule or standard by any measure. Most of the people that did succeed with that program were borderline prodigies I bet, and could likely do that same thing with another accelerated program, but that is less than even the top .5% of most people. Fuck, just getting a college degree you are in a small percentage. Getting one in engineering even more miniscule of a percentile. Being able to get one in engineering in less than a year of training you're talking a TINY amount, some of which probably already are software engineers.

      It might be possible, but those are some EXTREME circumstances and this CodeAcademy shit is nothing even close to something like that. Your average Joe Blow will go exactly no where with this sort of program.

    108. Re:Whats the big deal? by CAPSLOCK2000 · · Score: 1

      For every linked-list ever written in C there are a thousand JavaScript implementations of the Like+1-button. You don't need to be star-programmer to land yourself a good job as a website-developer.

    109. Re:Whats the big deal? by bfandreas · · Score: 1

      So say you.

      But I prefer my gold rush with Blackjack. And Hookers.
      In fact, forget about the gold rush.

      --
      20 minutes into the future
    110. Re:Whats the big deal? by pitzG · · Score: 1

      I did insert paragraphs, Slashdot deleted them for some reason.

    111. Re:Whats the big deal? by skovnymfe · · Score: 1

      I meant to write CSS, not javascript, which I did post somewhere in this thread... but it must've gotten lost. Blame /. for not letting me edit my posts.

    112. Re:Whats the big deal? by Crudely_Indecent · · Score: 1

      it doesn't. You can use less to define your CSS, then use less to compile it for deployment as traditional CSS.

      --


      "Lame" - Galaxar
    113. Re:Whats the big deal? by Anonymous Coward · · Score: 0

      Well said, Zmobie, I share your sentiment; actually, more than that. I had a decade of (now legacy) program'ing that I
      learned (painfully..) via reference sources, untold hours of trail & error..including some limited professional instruction.
      You just "don't get that" in typical college courses..let alone H.S... a**2

  2. Lean? by poet · · Score: 4, Funny

    Don't we want all of our code lean?

    --
    Get your PostgreSQL here: http://www.commandprompt.com/
    1. Re:Lean? by sunderland56 · · Score: 5, Funny

      No, it says lean-to code. As in coding while in a lean-to.

      Maybe CNN should lean to speak English?

    2. Re:Lean? by Anonymous Coward · · Score: 0

      Maybe it means to not sit up straight while coding?

    3. Re:Lean? by stephanruby · · Score: 5, Funny

      Lean to spel, get a job as a slasdot editor!

    4. Re:Lean? by hawguy · · Score: 4, Insightful

      Don't we want all of our code lean?

      Not really - I've run into too many coders that think "lean" code is the same as "terse code". They skip comments, compress loops into a single line or use all sorts of other tricks to compress code into a single line, etc. Anything they can do to make their code "lean". Which of course, makes their code write-only.

    5. Re:Lean? by Anonymous Coward · · Score: 1

      I don't know but they certainly didn't lean to spell!

    6. Re:Lean? by brumby · · Score: 1

      No, they mean 'lean-to' code. As in the software equivalent of getting a builder to build you a house and after 12 months finding you've got a lean-to that will hold a few boxes.
      I'm sure we've all had to work on systems like that.

    7. Re:Lean? by Ethanol-fueled · · Score: 5, Funny
      It's a reference to Lean manufacturing, with the idea that anything more than a few lines of rudimentary Javascript is not value-added and therefore unnecessary for customer satisfaction.

      I can see the job interviews now:

      What's your alma mater?
      Codecademy.
      What projects have you worked on in the past?
      At my last gig, I wrote a program to determine if a number was even or odd...in only ten lines!
      Wow! So what can you bring to FizzBuzz industries as a software engineer?
      Fizzbuzz.
      Hired.

    8. Re:Lean? by todrules · · Score: 1

      Maybe the next article should read: "Lean to proofread. Get a job."

    9. Re:Lean? by locopuyo · · Score: 0

      Skip comments? Good code shouldn't have comments.

    10. Re:Lean? by ACDChook · · Score: 1

      And what is CodeAdacemy??

    11. Re:Lean? by anubi · · Score: 5, Insightful

      Yes.

      The code produced will the architectural equivalent of a "lean-to".

      Its like practicing medicine after a first-aid course. Practicing law after watching Judge Judy.

      These are the "handymen" of the IT industry.

      Relax, guys.

      These guys will get the moneymeisters to invest, as they will promise and deliver an inexpensive job.

      Once the moneymeister has money invested, he will be easier to talk to as he will now have a vested interest in his investment actually being viable.

      You know the story: Haircuts, $1.00. Across the street: We fix bad haircuts, $10.00.

      But it gets better. The guy didn't need service at all until he got the buck job.

      --
      "Prove all things; hold fast that which is good." [KJV: I Thessalonians 5:21]

    12. Re:Lean? by Surt · · Score: 2

      Comments, like pretty much everything, are a tool that can be used well, or poorly.

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
    13. Re:Lean? by jhoegl · · Score: 5, Funny

      Slashdots sandards are hi for that positron!

    14. Re:Lean? by locopuyo · · Score: 0

      If your code needs comments it is because you have poorly named objects and methods or are trying to do too much in a single method. You recommend reading Clean Code. Then you will lean comments are bad.

    15. Re:Lean? by Anonymous Coward · · Score: 0

      Obsfucation is a lesson in what not to do even though you can.

      It's nearly 10 years since I learned this lesson, but I haven't forgotten it. From the time I wrote a mandelbrot set viewer in as many languages as I could find (limited in zoom by floating point accuracy in said language) and having learned under my own steam the ins and outs of the linux kernel and the function of most of the programs I used in debian. I proceeded to invest my time in other interests and thus forgot more than most people (indeed most CS students) lean about software in their lives.

      For the record the Zsh implementation was probably the most interesting. Mostly for the suprise that it could be done in shell script. At that point I wasn't comfortable enough with regex to do it in perl with regex rather than simple arithmetic (shortcutting) or the complex number module (simpler syntax as you'd expect, but lengthy execution time). I Challenge a reader to creat a mandelbrot generator in perl using regex and logic (I'll allow multiplication, but preferably only using "x"). If anybody actually does I bet his name is Ton.

      For the record the typo of learn above is deliberate.

    16. Re:Lean? by Surt · · Score: 1

      Yes, this is the philosophy commonly known as self-documenting code. Comments are exactly for when that philosophy breaks down.

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
    17. Re:Lean? by cdrudge · · Score: 2

      Comments? What are those?

    18. Re:Lean? by Nerdfest · · Score: 2

      Sadly, 10 lines would probably give them a leg up on some of the people I've seen in the industry. I really don't think it can get any worse. Anyone that will stick through a year-long "teach yourself to code" series may actually have more skill than someone who stayed in a training program that they paid for.

    19. Re:Lean? by Ethanol-fueled · · Score: 1

      I Challenge a reader to creat a mandelbrot generator...

      How do I creat a mandelbro generator? Is creat that shit that bodybuilders take to make their muscles ripped? OR those folks who have an IQ of fifty?

      If anybody actually does I bet his name is Ton.

      Legendary dutch classical musician Ton Koopman? Wow!

    20. Re:Lean? by Zmobie · · Score: 1

      That is only a half truth, there are a fair number of instances where comments are needed so that someone can understand why a design decision was made. Not only that, but even when the code is fairly easy to follow comments make it much faster to properly comprehend what is supposed to go on in a code block. Plus what about when there is a bug in the code? Or a design oversight even? In many real programming instances you will not be the only one working on that code, and therefore documentation keeps the bloat monster at bay. You should also remember that a large majority of large scale software ends up implementing cheap hacks for temporary fixes. Sure, it would be great if the project I was working on had a ridiculously large timetable and unlimited amounts of money to fund it so that any problem I found could be properly fixed every time, but the bottom line is code architecture is NEVER perfect. Also considering the fact that the majority of a software engineers time is spent maintaining code, documents are necessary, but I can agree need to be used properly and not above or beside everything.

    21. Re:Lean? by j35ter · · Score: 1

      You sir are an insensitive clod!

      --
      Delta-Mike November Bravo Tango
    22. Re:Lean? by Anonymous Coward · · Score: 0

      Ru make funly of me brecause I'm Japanrese!

    23. Re:Lean? by daktari · · Score: 1

      if($sense == $nonsense){
      // comment here
      };

      --
      A fool sees not the same tree that a wise man sees. -- Willam Blake
    24. Re:Lean? by russotto · · Score: 1

      Not really - I've run into too many coders that think "lean" code is the same as "terse code". They skip comments, compress loops into a single line or use all sorts of other tricks to compress code into a single line, etc. Anything they can do to make their code "lean". Which of course, makes their code write-only.

      I love those guys. My specialty is reading such code. Granted, sometimes it's easier to compile it and read the resulting assembler listing...

    25. Re:Lean? by tragedy · · Score: 2

      That's a ridiculous statement. That might work for some things, but not others, and sometimes you can be easily mislead about intent by really small errors. What if you're trying to program some sort of complex biology formula. Do you really expect everyone who ever reviews the code to be able to just look at it and tell both what it's supposed to do and if there are any errors just based on the names of the objects? Putting that kind of information in the comments is a solid engineering practice. You can also have that information in accompanying documentation, but you should still have comments to at least provide a reference to the documentation.

    26. Re:Lean? by Anonymous Coward · · Score: 0

      What happens in languages that don't have objects and methods? What happens when there is an extremely complicated section and the solution is non-obvious without comprehending the whole thing? What happens when reality strikes and not everyone is as perfect as you?

    27. Re:Lean? by MobileTatsu-NJG · · Score: 2

      CTRL + a then CTRL + i?

      --

      "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

    28. Re:Lean? by Anonymous Coward · · Score: 1

      Write-only code is the best.

      "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." --Brian Kernighan

    29. Re:Lean? by Glonoinha · · Score: 4, Insightful

      Hackers write code. Professional software engineers deliver business solutions.
      For the beginning professional software engineers out there, here's a tip : comment your code (and comment it correctly.)

      Code tell you what.
      Comments tell you why.

      --
      Glonoinha the MebiByte Slayer
    30. Re:Lean? by Anonymous Coward · · Score: 0

      Lean to proofread, get +5 funny.

    31. Re:Lean? by Tablizer · · Score: 1

      As in coding while in a lean-to.

      Well, that's the 3rd-world conditions most coding happens in these days. Chairs are only for management.

    32. Re:Lean? by Anonymous Coward · · Score: 0

      10 a$ = inkey$
      20 if a$ = "1" goto 90
      30 if a$ = "2" goto 100
      40 if a$ = "3" goto 90
      50 if a$ = "4" goto 100
      60 if a$ = "5" goto 90
      70 print "Input too high!"
      80 end
      90 print "Odd! not"
      100 print "Even!"

      I would have to do some thorough testing before knowing if it's free of syntax errors.

    33. Re:Lean? by Monchanger · · Score: 4, Funny

      Comments? What are those?

      It's the random fluff you put in your code so you can increase the linecount and show your eight bosses how productive you've been.

    34. Re:Lean? by AK+Marc · · Score: 2

      A sort is a sort. Coding a sort should be obvious as to what it is (a sort) as well as the type. But even self-documenting code won't tell you *why* one sort was chosen over another. Maybe there was a design meeting and memory was more important than cycles (or vice versa) and based on that, a particular sort was chosen. Going in with no knowledge of the process should still result in understanding the code, and an absence of comments will make that harder.

      The code shouldn't "need" comments, but the comments, even if not needed, should improve the understanding of the code.

    35. Re:Lean? by Concerned+Onlooker · · Score: 2

      "Is creat that shit that bodybuilders take to make their muscles ripped? OR those folks who have an IQ of fifty?"

      No, it's actually an assembly instruction. It's a tougher challenge than you think.

      --
      http://www.rootstrikers.org/
    36. Re:Lean? by scdeimos · · Score: 1

      I see you've never worked on anything that generates documentation from comments.

    37. Re:Lean? by Anonymous Coward · · Score: 0

      >>I love those guys. My specialty is reading such code. Granted, sometimes it's easier to compile it and read the resulting assembler listing...

      Don't laugh. I've had to do that, and rearrange some of the assembler instructions. Ugh. Do NOT miss that job.

    38. Re:Lean? by Anonymous Coward · · Score: 0

      if they can't read the code then maybe they aren't the right person to be reading the code. i barely comment my code, nor do I care if anyone else does. honestly i prefer to look at code without the comments, they get in my way and make it harder to read the code. i don't need 99% of the comments. although, on occasion i do add comments, but they're usually sarcastic in nature and more of a rant than anything useful.

    39. Re:Lean? by The+Pirou · · Score: 1

      Comments make it easier to differentiate changes for the purposes of maintaining the integrity of the author's source code for GPL. They might get in the way of you reading code quickly, but at least you could identify non-native material.

    40. Re:Lean? by Ryanrule · · Score: 1

      Regex says go to hell.

    41. Re:Lean? by TheGratefulNet · · Score: 1

      one day I was tripping and my code would not compile, but my comments did.

      program didn't crash, but exited rather quickly for some reason.

      --

      --
      "It is now safe to switch off your computer."
    42. Re:Lean? by _0x783czar · · Score: 2

      That's an interesting take. There may be some truth to that. Maybe their skills aren't there yet, but if they're willing to slug out for a whole year in a free programming course it could reflect something of their personality. That's gotta be worth something. As a Networking professor of mine said (to paraphrase him): "skills can be taught but habits are the key". Sure there's waaaaay more to computer programming, but it is possible that something like this could produce a few good "diamonds in the ruff".

      --
      ~theCzar
    43. Re:Lean? by Anonymous Coward · · Score: 0

      Hahahaha!!

    44. Re:Lean? by Surt · · Score: 1

      That's exactly right. Comments are easily abused, but even you admit there's the 1% that you need. Mastering the art of the 1% comment makes for a top tier developer.

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
    45. Re:Lean? by j35ter · · Score: 1

      I worked with psychos who thought that everybody could read their code ... they were very wrong. And of course, they never commented. In the end it was easier to rewrite their crap than take the time to analyze it. Commenting is an important part of the development process itself, you insensitive clod!

      --
      Delta-Mike November Bravo Tango
    46. Re:Lean? by j35ter · · Score: 1

      Great, you are a genius, you insensitive clod! Most coders who will have to work after you will curse you for thinking that everyone thinks in the same lanes as you do. I for one, had a photo of my non-commenting predecessor printed out and were regularly shooting it with a soft air gun. Others who also worked with his code did so as well.

      --
      Delta-Mike November Bravo Tango
    47. Re:Lean? by Anonymous Coward · · Score: 0

      LOL.but, should'nt that be just 1 line. fired

    48. Re:Lean? by ajo_arctus · · Score: 1

      If you have a developer doing that, at least it shows they are thinking about the problem. In my experience, that self awareness is a good sign -- they are likely to continue improving the code they write, and I wouldn't be surprised to find that in another 12 months to find that they were writing compact AND maintainable code.

      If you were to go back and look at the code you wrote years ago, when you were just starting out, would it be easily maintainable now? I doubt it. My early code certainly wouldn't. It makes me cringe just thinking about some of the hacks I did to compact my code down (often times involving bit fields...). Ugh.

    49. Re:Lean? by Anonymous Coward · · Score: 0

      The thing you just wrote. ;)

      Oh, in software? Dammed if I know.

    50. Re:Lean? by narcc · · Score: 1

      What happens in languages that don't have objects and methods?

      Good code gets written.

    51. Re:Lean? by Rockoon · · Score: 1

      Dont forget to comment the fields in data structures, telling both what and why.

      --
      "His name was James Damore."
    52. Re:Lean? by Anonymous Coward · · Score: 0

      For the beginning professional software monkeys out there, here's a tip: When maintaining code, ignore the comments.

      The code is what runs.
      Nobody ever fixes comment bugs.

    53. Re:Lean? by Anonymous Coward · · Score: 0

      Whenever I hear a debate about commenting code, it always reminds me about something I was told back when I was a student - "I don't put comments in my code; my variable names are so descriptive that I can't afford the space"

    54. Re:Lean? by Anonymous Coward · · Score: 0

      They skip comments, compress loops into a single line or use all sorts of other tricks to compress code into a single line

      So you know how to have fun, but you avoid it for other people's sake? Strange.

      Loop unwinding is the shiznat!

    55. Re:Lean? by Anonymous Coward · · Score: 0

      Pffft, "ins and outs of the linux kernel"?

      Still not Dan Aloni. When you see the Linux kernel, and think to yourself "Hey, this would make a great driver for Windows!", come see me.

    56. Re:Lean? by kaizokuace · · Score: 1

      but fat tastes so good.

      --
      Balderdash!
    57. Re:Lean? by mhelander · · Score: 1

      if($sense == $it_is_a_little_bit_complicated){ // explain why here
      };

    58. Re:Lean? by kaizokuace · · Score: 1

      maybe if you add a 'c' in front it will be better. Clean code is what I think I like when I think of lean code. Everything very organized and easy to read, not too verbose. No sloppy code tacked on here and there. Everything designed. I think having design sense is useful even in engineering. Design is not just about how something looks. It is about how something works and is used. How the way something looks can be part of or effect how it works. Everything man touches can be considered from a design standpoint. I may be thinking about too many other things and am off topic from lean coding. Also, I like typography and good looking code can look pretty. (is that a little perverted?)

      --
      Balderdash!
    59. Re:Lean? by Anonymous Coward · · Score: 0

      It works well for meanings and intentions that are simple enough to express in names of objects, methods and variables, and on that level code should be self-documenting. Not everything is that simple, however. If you need an algorithm with more than basic complexity then you are not doing anyone a favor who has to maintain the code, solve a production problem perhaps, by requiring them to reverse engineer the high-level view required to understand what is going on from the details. A bug in such code can easily give a wrong impression of the intended working, and the one solving it under time pressure has to figure out from an inconsistent message what was intended. Comments can be lifesavers.

      Earlier this week I used a comment to document why I chose for a certain way to implement a function and not for an alternative way that could easily seem more obvious on first sight, but had subtle problems. How can self-documenting code ever explain what you have not done?

    60. Re:Lean? by JoeMerchant · · Score: 1

      No, it says lean-to code. As in coding while in a lean-to.

      I thought it was an analogy for making code like a lean-to, you know, slapped together with whatever material is at hand, resulting in a small, uncomfortable, difficult to improve structure that is poor protection from the elements at best, and likely to blow over in a stiff wind.

    61. Re:Lean? by JoeMerchant · · Score: 1

      Hackers write code. Professional software engineers deliver business solutions.
      For the beginning professional software engineers out there, here's a tip : comment your code (and comment it correctly.)

      Code tell you what.
      Comments tell you why.

      For those attempting to "Level up" - Comments tell you why, but the story should be short and to the point. This is not a comment on how to comment, it is a comment on how to code. If the code needs a lot of explanation, it probably needs rethinking. If the code's comments are significantly larger than the specification they are fulfilling, there is something wrong. If the specification is incomplete or not present, you are not doing professional software engineering.

    62. Re:Lean? by ImprovOmega · · Score: 1

      Ye gods. If it's more than one line you have a problem. More to the point if they actually use a function to do this you have a problem. If they don't know to avoid a MOD in the code you have another problem (unless they can explain to you how the optimizer will fix it anyway and it's just more readable as a MOD operation).

      #define IsOdd(num) ((num)&1)

    63. Re:Lean? by Anonymous Coward · · Score: 0

      In my experience comments spend too much time telling what it is doing instead of why. Most comments are out of date and poorly written anyway.

      In other words, they are line noise and a hindrance.

      Give me the general contract for a method/class/function/whatever and document anything out of the ordinary. Other than that, if your code can't be used as the rest of the comments you are writing bad code.

    64. Re:Lean? by donscarletti · · Score: 1

      I agree with what you mean, but I also think that a huge problem in converting "hackers" to "professional software engineers" as you call it is that most of professional software engineering's most passionate proponents have a habit of writing really pompous sounding things like "Professional software engineers deliver business solutions". My suggestion would be to go straight for the ego:

      To all you smart, brave and handsome young hackers fighting the battle out there, not only does writing legible code with appropriate comments lets others know how smart you are. If there is a small, easily fixable edge-case, but the other programmers can't read your code, they will think that you wrote it completely wrong and rewrite it with their own implementation, which might not be as good as yours. If your code is legible, they can make a one line change, without smearing it up with grubby fingers, take a few quick gasps at your greatness and move on to messing up someone else's code.

      --
      When Argumentum ad Hominem falls short, try Argumentum ad Matrem
    65. Re:Lean? by Anonymous Coward · · Score: 0

      You are correct,comments are mostly to document unreadable code.

      Of course unreadable can mean two things.

      1. The code is crap in which case that programmer should never have been hired.
      2. The code is good but the maintainer(ie you) doesn't know enough to read it, in which case you should never have been hired.

      There is a reason languages with training wheels exist(java, C#, VB, PHP), it is so companies can "save money" by not hiring competent programmers, yet still get something out the door,

    66. Re:Lean? by Anonymous Coward · · Score: 0

      Professional software engineers use meaningless buzzwords and "deliver" bloated, slow, and buggy business solutions.

  3. We think it's sort of a dupe by Anonymous Coward · · Score: 2, Informative
  4. BT,TD,GTTS by Todd+Knarr · · Score: 5, Insightful

    You can get a job as a software developer in the same sense as a lot of people could go through HTML For Dummies and get jobs as Web Developers. That's great when companies are hungry for anyone even minimally qualified, but it's not going to do much for keeping your job when they start having to actually work with and maintain your work product.

    1. Re:BT,TD,GTTS by CrudPuppy · · Score: 4, Insightful

      This is exactly it. IMHO, coding is equal parts art, ingenuity, and science. Writing great code is no different than trying to write a great trilogy of fiction. Anyone can write garbage, but it takes a mastery of the language itself, and that mastery is just a means to an end--creating something great.

      --
      A year spent in artificial intelligence is enough to make one believe in God.
    2. Re:BT,TD,GTTS by Anonymous Coward · · Score: 5, Insightful

      Give a bunch of random people the science, and you'll find people who had the art and ingenuity but didn't know it.

    3. Re:BT,TD,GTTS by Ethanol-fueled · · Score: 2

      The barrier of entry is also pretty low because all one needs to learn programming is a computer(and everybody has one of those), lots of time, and the internet. The signal-to-noise ratio of homeschooled coders' skill levels is probably pretty high, but it also means that the good ones are given the opportunity to rise to the top. You can get some kid who writes "hello world" out of curiosity, then moves on to crude GUI applications, then goes on to make thousands of dollars a month coding for the RBN and lurking obscure IRC fora.

      Becoming a hardware savant, in contrast; requires an oscilloscope, multimeter, one or more DC power supplies, a signal generator, and countless dollars spent on components and boards. Who the hell has access to all of that at the high-school level?

    4. Re:BT,TD,GTTS by Anonymous Coward · · Score: 0

      Self taught programmer here. I think the article stating, that just by learning to "code" the average Joe can earn more is misleading and based on a faulty premise. The article mentions that "...each employee who understands how to code is valued at about $500,000 to $1 million toward the total acquisition price", referring to tech. company acquisitions, and the impressive "value" of each developer acquired by the company. This value is mainly the sum of a) high levels of business specific knowledge, b) years of experience with the systems used, and c) significant technical skills. Knowing how to churn out a few lines of code unlikely to be worth anything in monetary terms in the real world (although can be beneficial in other ways).

    5. Re:BT,TD,GTTS by Ravon+Rodriguez · · Score: 1

      Give a bunch of random people the science, and you'll find people who had the art and ingenuity but didn't know it.

      This. Along the same line, not everyone who goes to college has what it takes to graduate, and not everyone who graduates with a computer science degree has what it takes to be a coder. But you will never know unless you try.

      --
      Jesus loves me, he loves me a bunch, because he always puts Jiffy in my lunch.
    6. Re:BT,TD,GTTS by rwven · · Score: 1

      The problem is, only about 1 in 100 of the people with the science, also have the art and ingenuity. There are "programmers" everywhere. I typically have to interview about 30+ people who "technically" meet job requirements before I hire someone who is genuinely a good programmer.... I still shake my head and wonder how someone can claim 5-10 years of experience in a language and still know so little about it...or programming theory in general.

    7. Re:BT,TD,GTTS by Alex+Belits · · Score: 1

      But you will never know unless you try.

      You won't know even after you will try. However people who will be stuck maintaining your "code" definitely will.

      --
      Contrary to the popular belief, there indeed is no God.
    8. Re:BT,TD,GTTS by Todd+Knarr · · Score: 1

      Thing is, almost everybody's got what it takes to be a coder. But that's just a fraction of what it takes to be a programmer. Just like most people can nail 2x4s together but that's a far cry from being an architect or even a cabinet-maker. The rest can't be taught, it can only be learned. Most people are just unable or unwilling to learn it because learning it's work.

    9. Re:BT,TD,GTTS by Anonymous Coward · · Score: 0

      I'm a non-professional programmer (paid for code, but no high-level training) , and I signed up for the course simply out of interest. I don't think this is going to get me a job, but as far as I'm concerned, providing something like this to the general public will help people get a foot in the door, and at the very least allow them to get a feel for what writing code is, and whether they enjoy it.

      I don't think that anyone is seriously suggesting that one can take this course and get a job as a programmer - that seems a liitle naive.

    10. Re:BT,TD,GTTS by Anonymous Coward · · Score: 0

      Over 20 years of experience in software development I noticed that people with brains do not have to have an appropriate formal schooling. In fact majority of PhDs in so called computer science are completely useless and disturb more than help. Not sure why coding is considered an art - it may be some ingredients of art are part of coding experience for best of us yet majority of software production is an engineering process and it would be better for quality of software if it was considered as such. What I wanted to say especially in response to GP is that these newbies wil be sorted out and good ones may stay and produce good stuff (untill somebody finds out that they cost 10 times more than unknown group of experienced geniuses in Zamunda). Give them a chance and see I'd say.

    11. Re:BT,TD,GTTS by TheTurtlesMoves · · Score: 1

      My high school did have all that. Even after i could ask at the departments to use theirs at the local uni. If there is a will there's a way. Don't forget that pc sampling scopes in the 100MHz range are pretty cheap now days. Sure a 500MHz scope is expensive but that is not needed for quite a lot of things.

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
    12. Re:BT,TD,GTTS by Splab · · Score: 1

      I am all for general public learning and getting jobs writing code. I make my living fixing other peoples mistakes.

    13. Re:BT,TD,GTTS by kaizokuace · · Score: 1

      but a really good cabinet maker and a so-so cabinet maker are 2 different things. The difference is how much they enjoy it. Are you someone who assembles cabinets? Or are you a wood worker. One of them involves getting joy from wood (that's what she said btw).

      --
      Balderdash!
    14. Re:BT,TD,GTTS by Anonymous Coward · · Score: 0

      Clearly you've never actually read the Lord of the Rings books!

  5. Well Duh! by WebMasterP · · Score: 0

    Just like everyone can learn to dunk, everyone can learn to develop!

  6. Lean to Code at the Code Adacemy by Anonymous Coward · · Score: 1

    Perhaps we should be learning to spell first?

  7. Lean to spell, samzenpus by EmagGeek · · Score: 1

    That about says it.

  8. That's all we need by multiben · · Score: 5, Insightful

    One of my pet hates is working with programmers who are doing it only because they need a job. Don't get me wrong, I wouldn't be here if I didn't get paid, but programmers without passion for what they do write lousy and uninspired software. People with passion are unlikely to end up in such a scheme, so I don't really see a big benefit.

    1. Re:That's all we need by Darinbob · · Score: 1

      It's like when you visit the dentist who hates being a dentist...

    2. Re:That's all we need by sidthegeek · · Score: 1

      This is true for most professions.

    3. Re:That's all we need by Anonymous Coward · · Score: 2, Insightful

      I used to love my job. The passion is gone. If I didnt get paid for it I would probably still do it. But very rarely.

      But *most* people can program. Sorry to let you down like this. 99% of the time these days you are just googling and gluing libraries together. It is a *rare* thing to use comp sci skills to do things. Working with cheap overseas labor has taught me this. No one cares about quality. They care about cost.

      Every once and awhile I whip out the ol mojo and write some seriously cool code. But most of my co-workers dont get it. So I dumb it down. After working with ego maniacs, loosers, crappy coders, and so on over the years you dont care anymore.

    4. Re:That's all we need by Anonymous Coward · · Score: 0

      I think we'd all like people to be passionate about their job, but then they wouldn't call it a job now would they?

      I think the article has a larger point to make than just the "learn to code and get a job" part, a child born today is touched by technology in every facet of their lives from second 1. As a matter of education policy, it makes sense to try and promote a basic understanding of that technology for us to stimulate the ideas economy and the greater world around us.

    5. Re:That's all we need by Shajenko42 · · Score: 4, Funny

      Little Shop of Horrors teaches us that going to a dentist who loves being a dentist isn't necessarily a good thing...

    6. Re:That's all we need by Anonymous Coward · · Score: 0

      Add a zero to the end of my salary and see just how passionate I can get!

    7. Re:That's all we need by MightyYar · · Score: 4, Funny

      Sadists become dentists, programming is for the masochists.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    8. Re:That's all we need by jackbird · · Score: 4, Insightful

      *most* people can program

      I dare you to do a week of first-line desktop support *anywhere* and come out with that belief intact.

      Lots of people set their thermostat above the temperature they want just so they can turn it down when it gets too hot, even when they fully understand how a heater works.

    9. Re:That's all we need by Strudelkugel · · Score: 1

      To be good at any type of knowledge or artisan work, a person has to have some level of personal curiosity or interest in what the job involves. My guess is that most of the people who attend this event are doing because they want/need a job. The kind of person I would be interested in hiring would already be doing some programming in his or her free time. There will be a few people who attend who will discover that programming is something they really enjoy, but that group will be a small minority. OTOH, many others will find they dislike programming and will stay away from it.

      Hopefully someone is going to track the results over time. Maybe a few of the attendees with initiative will create a database app to do just that.

      --
      Imagine how much harder physics would be if electrons had feelings! -Feynman, maybe
    10. Re:That's all we need by Anonymous Coward · · Score: 0

      Welcome to the world young man! Someone not being happy or passionate at ANY job will do it lousy and be uninspired. What makes programming any different? The grumpy single mom on the phone at the doctors office makes everyone angry too customers and coworkers included.

      Programming is not a hard trade to get into, the tools of the trade are free and everywhere. You can test and practice the skill at NO cost other than having a computer and a desire. Your idea of a "good programmer" is subjective. Based on the cross section of programmers I read comments from on slashdot, everyone here is an outstanding programmer and everyone else is not.

    11. Re:That's all we need by Surt · · Score: 1

      I don't understand the problem with the heater. If you like turning a heater down when it gets too hot, what's the better solution?

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
    12. Re:That's all we need by EasyRhino · · Score: 1

      Variety is the spice of life. Some of the most productive programmers I know were simply doing it because it was a "good" career. Passion and excitement are not pre-requisites for recognizing and pursuing excellence.

    13. Re:That's all we need by Anonymous Coward · · Score: 0

      whats not to love about dentistry? you get to numb people up, drill away dirty teeth and tell people what they should be doing with their mouths.

    14. Re:That's all we need by Anonymous Coward · · Score: 0

      Mmmm yes. I have a gigantic passion for writing banking software.

    15. Re:That's all we need by Anonymous Coward · · Score: 0

      Well to be fair, it depends on the exact PID algorithm in use by the thermostat. If you've got a crappy one, you might be better off turning the temperature above the desired setting and then adjusting it manually once it reaches the temp. you like.

      I once had a horribly-designed thermostat which was prone to extreme ringing effects when the room temperature approached the desired setting.

      Then again, I'm a physicist and understand this shit.

    16. Re:That's all we need by guspasho · · Score: 2

      Judging by my experience as a regular software user, lousy and uninspired software is exactly what companies want.

    17. Re:That's all we need by anubi · · Score: 2

      Why did you post AC?

      I think you have good insight into the situation today.

      If I had mod points today, you would have got one. Instead, all the appreciation I can give you is a reply..

      I can surely understand your situation. I'm in the same boat.

      Its like being an artist when what employers want are house painters, evaluated by how many square feet per second they can paint.

      Not on whether or not the paint was properly applied.

      Let the sucker customer deal with the inevitable peeling that will happen next year. All that is important is the check cleared, and sufficient ambiguities are in place so a lawsuit won't hold.

      --
      "Prove all things; hold fast that which is good." [KJV: I Thessalonians 5:21]

    18. Re:That's all we need by pla · · Score: 4, Insightful

      But *most* people can program.

      Aahahahahahahaahaha...
      Heh. Ahem, sorry.
      <snrrrrrrrk>

      To tell you the truth, I honestly don't know if most people could eventually learn to program well. I know that most people can, with time and effort, learn to write very, very simple programs - programs most of us would consider easy homework assignments from CSC101.

      But most people hate hate hate everything that makes good programmers good programmers. They hate the tediousness, the methodicalness, the breaking-things-down-into-tiny-steps, the 8+ hours of keeping your brain in an alpha state. What "real" programmers view as fun and almost a form of meditation, the average Joe views as nothing short of self-imposed torture.

      So yeah, maybe everyone could learn to program. But I have absolutely no concern that any time in my lifetime, "most" people will want to program even if they could learn to do it.

    19. Re:That's all we need by j35ter · · Score: 2

      Hey, that is called PID regulation, you insensitive clod!

      --
      Delta-Mike November Bravo Tango
    20. Re:That's all we need by c0lo · · Score: 2

      Sorry to let you down like this. 99% of the time these days you are just googling and gluing libraries together.

      Nothing wrong with gluing if you know what you are gluing actually fits what you are trying to achieve.

      It is a *rare* thing to use comp sci skills to do things.

      Nothing wrong with this either (CompSci != SoftEng). Sure, it helps for SoftEng to have CompSci knowledge, but is not absolutely necessary.

      Working with cheap overseas labor has taught me this. No one cares about quality. They care about cost.

      Agreed.

      Every once and awhile I whip out the ol mojo and write some seriously cool code. But most of my co-workers dont get it.

      Is it CompSci that helps the coolness? (i.e. algorithm complexity? scientific performance assessment and optimization? Even only a new scripting language or some automatic code generation?) Or is it cool because of the architecture/design (pertaining to SoftEng)?

      So I dumb it down. After working with ego maniacs, loosers, crappy coders, and so on over the years you dont care anymore.

      If you don't care on the quality of the code you wrote, why are you complaining about quality? I mean, the lack of quality is hugely due to the "That's good enough" attitude, that's exactly what they use as an argument when caring about cost. If you give it to them the way they want, what do you expect: a loud cracking whip made of shit?

      --
      Questions raise, answers kill. Raise questions to stay alive.
    21. Re:That's all we need by Anonymous Coward · · Score: 0

      I have been first line. I have also taught most shitty programmers to be better. Being a programmer is not hard. Being 'ok' is just a matter of being methodical. You can teach that. What you can not teach is being good at it.

      You analogy is silly. People who are calling into a help desk usually *do not care* how the f your stuff really works. They just want what you sold them. Oh and to be 'easy' to use. They dont want to follow your instructions like a computer. They want *you* to fix it that is why they called you. How about this. I buy a 200k car it doesnt start. Do you think I want to go thru a punchdown list and spend my time 'fixing' a car? No I just want it to start, and preferably you come over and get it to work. That is human nature. We are impatient, lazy, and usually gloss over many things (if we can get away with it).

      Your heater thing is silly too. As people who make the thermostats realize this is just human behavior and have a 'turn off/on timeout time' (usually 2-3 mins in houses which also helps with borderline conditions).

      I can tell you are a mediocre programmer by your comment. You think you are better than others. You are this way only because you pay more attention. That is a skill that can be taught (have done it many times). Being an 'ok' programmer is just a matter of PAYING attention. When you are surrounded by 'not so good at it' people you start to think you are better than others. But they can be taught. But if you act like an ass and look down on them they will *never* listen to you. "If a guy's close to you, you can't slight 'im. You can't slight that guy. A real grievance can be resolved; differences can be resolved. But an imaginary hurt, a slight - that motherfucker gonna hate you 'til the day he dies." -- hoffa Why do I tell you this? You could and probably should help those around you be better. You do that and you will transcend from 'ok' to 'good'. Just a small tip once and awhile, a 'hey I found a better tool', this is an interesting way to do this 'let me show you a better way and why what you did will not scale'.

      The only ones I have never been able to teach are the ones who start with 'I can not learn this' or dudes like you who think they already know it all.

      But do what you will. Like I said I lost my passion years ago. I can be replaced by 5 guys from india. They as a group will outcode most people who post here. They will also cost half as much as what I charge. That is what businesses want. They want cheap. Not good. As with most things you get what you pay for.

      Manage a few groups from India and you will see what I see.

    22. Re:That's all we need by Macgrrl · · Score: 1

      I expect is depends on which end...

      --
      Sara
      Designer, Gamer, Macgrrl in an XP World
    23. Re:That's all we need by Anonymous Coward · · Score: 0

      I dunno. I've seen enough code to think that the original authors sadist, preying on the testers and eventual maintainers.

      Of course, Hanlon's Razor may be involved as well.

    24. Re:That's all we need by Anonymous Coward · · Score: 0

      But *most* people can program.

      Aahahahahahahaahaha...

      Heh. Ahem, sorry.

      <snrrrrrrrk>

      To tell you the truth, I honestly don't know if most people could eventually learn to program well. I know that most people can, with time and effort, learn to write very, very simple programs - programs most of us would consider easy homework assignments from CSC101.

      But most people hate hate hate everything that makes good programmers good programmers. They hate the tediousness, the methodicalness, the breaking-things-down-into-tiny-steps, the 8+ hours of keeping your brain in an alpha state. What "real" programmers view as fun and almost a form of meditation, the average Joe views as nothing short of self-imposed torture.

      So yeah, maybe everyone could learn to program. But I have absolutely no concern that any time in my lifetime, "most" people will want to program even if they could learn to do it.

      From one of those people who thought I liked thoroughness and small step by step process building, I have to agree. After working with a project team for a while I found that certain aspects were boring as hell to me. Not everyone would love it and if you don't like it you get sloppy. I am not a programmer and sorry to say I would likely make a p### poor one.

    25. Re:That's all we need by Tablizer · · Score: 1

      Most people could perhaps also build a car from scratch, but I wouldn't want to own such a car.

    26. Re:That's all we need by Tablizer · · Score: 1

      That is what businesses want. They want cheap. Not good. As with most things you get what you pay for.

      I'd qualify that a bit. Businesses just don't know how to tell the difference between good and ordinary. In that circumstance you go with what you know you can measure: price.
       

    27. Re:That's all we need by MrCrassic · · Score: 1


      But most people hate hate hate everything that makes good programmers good programmers. They hate the tediousness, the methodicalness, the breaking-things-down-into-tiny-steps, the 8+ hours of keeping your brain in an alpha state. What "real" programmers view as fun and almost a form of meditation, the average Joe views as nothing short of self-imposed torture. Everyone loves and wishes they could sing, dance or draw. But will everyone love the hours and hours and hours and HOURS of training that goes into becoming a singer, dancer or "professional artist," only to find out that you have to work really, really, REALLY hard to get noticed because a lot of people can sing, dance AND draw? If you're a singer, you get paid like shit and will probably have to work two or three jobs to make rent and side money in hopes that an A&R guy discovers your talent, submits your demo, really pushes for the exec to drop an advance for you, all of which will probably be eaten up by "overhead" and will leave you broke anyway. If you're a dancer, you'll probably mess up your feet and be practicing just about ALL the time. If you're an artist, you're struggling almost everyday...even if your stuff makes gallery.

      Nobody loves real work except those that love the work.

    28. Re:That's all we need by AK+Marc · · Score: 1

      Don't forget the users. Coders hate users as well...

    29. Re:That's all we need by pla · · Score: 1

      Nobody loves real work except those that love the work.

      I can't tell if you meant that as agreeing with me or counterpoint, but I agree with you completely - You really have to love any of those things to master them.

      I would even argue that "artists" have it even harder, because for programmers, you merely need to love it to make a living at it; for any of the arts, you need to not only love doing it, but either count as a genius at your craft or get very, very lucky.

      That said, I don't think that I could ever make an even halfway competent artist, not even if society so valued them as to hire any hack "draper" for a six-figure salary. With years of study, i could possibly manage technical illustration. But art? I just don't think even a lifetime of study would turn me into an Escher, nevermind a Rembrandt.

    30. Re:That's all we need by metalix · · Score: 1

      Lots of people set their thermostat above the temperature they want just so they can turn it down when it gets too hot, even when they fully understand how a heater works.

      I set it to 85 so it would heat up faster!

    31. Re:That's all we need by rwven · · Score: 1

      You definitely lost me at "most people can program." Bull. Only a truly uninspired artificial coder would actually believe that.

      And caring about quality....? They sure do. They quickly learn that caring about quality and cost are one and the same. It easily costs an order of magnitude more to repair and maintain a low quality system. A small extra cost in the beginning to offset a massive cost later is an easy, and common, lesson to learn.

      And for the record, I can't remember the last time I "googled and glued" any code together. I've been doing this for a long time, and I'm more excited about it now than ever before. Maybe you're just in a crummy job and it's time for a change...?

    32. Re:That's all we need by jackbird · · Score: 1

      We have a winner!

    33. Re:That's all we need by hcs_$reboot · · Score: 1

      Indeed, we need that. We need an important person, someone like Mr Bloomberg, to spend a year learning how to program, and in the end, realize
      - that it was not as easy as expected
      - what is our (real programmers) daily work like

      This is what the political circle lacks anyway. Having a basic idea of what is our life, our real problems and constraints, in the real and concrete professional world.

      --
      Slashdot, fix the reply notifications... You won't get away with it...
    34. Re:That's all we need by jackbird · · Score: 1

      I can tell you are a mediocre programmer by your comment. You think you are better than others. You are this way only because you pay more attention. That is a skill that can be taught (have done it many times).

      I don't claim to be a programmer. I do a bit of scripting to get my job done. I sometimes try to teach others in my niche a little bit of scripting to help them get their jobs done. Usually those people (who are already comfortable using computers in ways that don't feature a "like" button) learn just fine.

      I also have a side job fixing people's PCs. I don't look down on my clients - they're often wonderful to interact with and extremely competent in their areas of expertise. Many people seem to have some kind of phobic reaction to computers, though, that causes them to completely suspend their otherwise clearly well-developed critical thinking skills (Really? You're a big-city heart surgeon and you gave a ransomware company your credit card number?)

      This is what I mean when I disagree that most people can program. Most *habitual computer users* can program. Most *people* can't give decent driving directions.

    35. Re:That's all we need by sjwt · · Score: 2

      I believe he is referring to those who think setting it higher means it will hit the required temp faster! I have known a lot of ppl who do that, they will turn an oven onto 220, so it will get to 180 quicker.. a reverse cycle air con onto 25, so it will get to 22 quicker.. I even know someone at my work who turns the toaster onto max, sits their watching it and then manually pops it every 10 seconds after a minute to see if its ready!

      --
      You have 5 Moderator Points!
      Which Helpless Linux zealot/MS basher do you want to mod down today?
    36. Re:That's all we need by TheGratefulNet · · Score: 1

      Sadists become dentists, programming is for the masochists.

      conversation heard between them:

      "go ahead, try to crash my program."

      "no."

      --

      --
      "It is now safe to switch off your computer."
    37. Re:That's all we need by Anonymous Coward · · Score: 0

      It makes perfect sense if the room that's temp you care about isn't the one with the thermostat in it, or has bad air circulation. If my bedroom is too cold and has poor circulation, while the thermostat is in the livingroom, then the heat will keep shutting off as soon as the livingroom warms up. Takes forever to warm up the hypothetical bedroom this way.

    38. Re:That's all we need by Anonymous Coward · · Score: 0

      Lots of people set their thermostat above the temperature they want just so they can turn it down when it gets too hot

      My thermostat is an analog knob that goes between "Lo" and "Hi", and has the middle section labeled "Comfort Zone". It lies and is a total piece of shit. I wish I could replace it with a Nest, but it's a high-voltage control line, and we're in a rental so we can't replace the heater.

    39. Re:That's all we need by dokc · · Score: 1

      It's not true that *most* people can program. You maybe wanted to say that *most* people (related to programming) can write code which can be compiled, but only the real programmers can write and maintain useful code.
      Real life example: my company bought HW platform and software from some other company. We now have to maintain the code where in one critical file there is a line like:
      SOME_MIN_VALUE = some_global_pointer->element.min;
      SOME_MIN_VALUE is of course, a normal variable.
      For me the one who wrote that line deserves to go to the programmers hell!

      --
      In love, war and slashdot discussions, everything is allowed.
    40. Re:That's all we need by Anonymous Coward · · Score: 0

      They need the Breville toaster available at amazon with the lift and look feature!

    41. Re:That's all we need by Anonymous Coward · · Score: 0

      I know those people, too. Actually quite often I find myself being one of these. This behaviour is explained quite easily: it's a stupid machine. With the higher \delta\theta an oven set to 220 does indeed reach 180 quicker. Nobody has told us, yet, that there is some intelligence in our machines today, that takes care of these optimizations for us. It is actually hard to tell which machines are "smart" and which aren't. Knowing to code makes this even more problematic b/c people think they get a better sense of how smart their new possessions are. Yet the toaster example is a little over the top, I feel.

    42. Re:That's all we need by rmstar · · Score: 1

      *most* people can program

      That does not reflect my experience. I taught some programming courses and I would say about half of the people didn't really get loops. I would say it wasn't my fault, because when I took this sort of course, I saw the same thing. Most people can't understand and code a loop.

      I never really understood this. These were smart people that could and did achieve interesting things in life. Put program? Nope.

    43. Re:That's all we need by Anonymous Coward · · Score: 0

      I think that's true about just about any field. I'm a lawyer myself, not a programmer, but I like computers and would like to learn at least the basics of programming. Not because I would necessarily want to *work* as a programmer but because I want to have fun doing it. That's why I signed up for that course. I think a lot of the people who sign up will have similar reasons, even if the hype says learn to code and get a job.

    44. Re:That's all we need by O'Nazareth · · Score: 1

      Are not the PID regulator supposed to stop the heater before it gets too hot?

    45. Re:That's all we need by Anonymous Coward · · Score: 0

      You must be talking C not F right? Most residential ovens won't go below 225-250F. FYI setting it to a higher temp will heat the oven quicker. Why? The oven will turn the element on for a longer duration if the temp is set higher. It is controlled by a thermocouple, meaning when it starts it will pour the electricity on to the element 100%. In this case it will keep the heating element on longer at 100% because it thinks it needs to get to a much higher temp. If the temp set low it will heat at 100% for a short time then reduce the power as it eases toward the temp it wants.

    46. Re:That's all we need by Anonymous Coward · · Score: 0

      My god, my new favourite quote.

    47. Re:That's all we need by umghhh · · Score: 1

      It is of course nice and good when people do what they really like but big part of any software job is engineering and no science or art etc. Inspired people gave us great software because they were good engineers not because they were inspired.

    48. Re:That's all we need by narcc · · Score: 1

      That does not reflect my experience. I taught some programming courses and I would say about half of the people didn't really get loops.

      Same here. I noticed the same thing years ago as an undergraduate. Even having taught computer programming for years now, I still don't understand the mental block people get when it comes to loops.

      They can answer questions about loops. They can look at an example of a loop and tell me what the output will be. I'll be damned if they can write one, or even say "I should use a loop" after determining that some bit of code should iterate. It's like they have all the knowledge they need, but just can't seem to bring themselves to put it into practice.

      If anyone here has a real problem understanding loops, or clearly remembers when they did, can you offer some insight?

    49. Re:That's all we need by Terrasque · · Score: 1

      I dare you to do a week of first-line desktop support *anywhere* and come out with that belief intact.

      Amen. After a few years of tech support I'm pleasantly surprised when people manage to open a door without burning down the builidng.

      Overheard conversation :

      "Is on the modem green? .. Are there any lights on the modem? .. Could you turn on the modem? .. Yes, I do think that will make a difference..."

      No, that's not a joke, or even an exaggeration. Those people are out there, and ther's a LOT of them.
      People who have disabled the network card and refuse to enable it again (a little knowledge...);
      people who don't mention that their pet rabbit have gnawed over the wires, and honestly can't understand why that would be a problem;
      people who answer "yes" to every diagnostic question, hoping it goes faster that way somehow; people that still have the modem in the car, unboxed, and refuse to fetch it, because they just want it to work and we should fix it.. over the phone.. somehow..

      --
      It's The Golden Rule: "He who has the gold makes the rules."
    50. Re:That's all we need by Rockoon · · Score: 1

      It's not true that *most* people can program. You maybe wanted to say that *most* people (related to programming) can write code which can be compiled, but only the real programmers can write and maintain useful code.

      In the world of app stores, I believe that writing maintainable code is becoming less and less important. There will never be another version of nearly every app in the store, because its just as easy for a user to pick up someone elses works-just-like-it as it is to pick up version 2.0 of yours. No loyalty is the new markets.

      --
      "His name was James Damore."
    51. Re:That's all we need by Xest · · Score: 1

      Actually I have no problem with that, god only knows we could do with a bunch of Javascript and HTML lackeys. Where I have a problem with it is when they expect to be paid as much as the talented developers putting together the massively more complicated backend system behind it and the like.

      The other problem is that if these people blag their way into a job as the first man in on the dev team then you get a situation where these people through nothing other than being in the right place at the right time not only get paid too much, but are then responsible for hiring other devs, often turning away great people for people like them, because they don't know any better. That's not too big a problem for talented devs, as not every company is like that, and the companies who know what the hell they're doing will quickly pick up those devs because there is a shortage of such skills, but it is why there's so much bad code in the world, why massive security breaches are so common.

    52. Re:That's all we need by Anonymous Coward · · Score: 0

      And sadomasochists make dental web apps.

    53. Re:That's all we need by Splab · · Score: 1

      Interesting, my experience is programmers with a passion tend to solve the parts of the program they really want to work with and leave the boring trivial parts to others - and often they do so going on a tangent.

      At my current job I have a coworker who really really loves the newest shiniest stuff out there - there isn't a month where he isn't trying to push version 2.0 of some new framework he read about on twitterbook.

      Oh, and generally, "inspired" code means you have found some clever way of doing something; often with no comments and absolutely no help to anyone but you...

    54. Re:That's all we need by kaizokuace · · Score: 1

      Why not just set the oven to the desired temp? What's the rush? I'm sure if you are baking you shouldn't be in any kind of rush. Isn't it nicer to use the feature the device gives you instead of trying to hack it to override it's functions?

      --
      Balderdash!
    55. Re:That's all we need by kaizokuace · · Score: 1

      I am an artist. The aspects of programming you described, I feel, are what makes it an art. This is why I decided to start learning programming. Art isn't about technical skill. Yes technical skill helps to be able to communicate clearly your ideas and thoughts. But art is about sharing or displaying your thoughts, emotions, intentions. I mean, yea there is a very mechanical aspect to programming but software design is the art part of it. It involves decision making. Those decisions are not cut and dry and can be varied on style and express your character as a developer. Art is just the use of a medium to communicate. In this regard, a lot of things can be considered art. Also, just because other people wouldn't follow this line of thinking doesn't mean it's not valid. A lot of people put their opinion behind defining what art is. They usually try to define art subjectively and pass that definition off as objectivity. Anyway, the part of your comment about using alpha state for 8+ hrs. Do you have more info on this?

      --
      Balderdash!
    56. Re:That's all we need by JoeMerchant · · Score: 1

      One of my pet hates are coders who love the art so much that they relentlessly strive for the next level of coding nirvana, re-factoring things that work perfectly well in the name of flexability, extensability, and support for things that may or may not ever come to pass.

      You can increase the complexity of code to fulfill a specification by an order of magnitude by adding "API layers" to take a simple one-to-one problem and providing a many-to-many solution.

      It's cool that you can think at that level of abstraction, but don't force us to all learn your made up language in the name of supporting things that aren't really there...

    57. Re:That's all we need by JoeMerchant · · Score: 1

      Judging by my experience as a regular software user, lousy and uninspired software is exactly what companies want.

      Its all they want to pay for.

    58. Re:That's all we need by Anonymous Coward · · Score: 0

      But *most* people can program.

      Yes, and *most* people can apply band-aids to cuts and scrapes. That doesn't mean that you want them walking into the OR when you need a liver transplant.

      One of the big problems with present-day software is that too much of it was implemented in a "*most* people" way. Then it breaks under strain, can't talk to other systems, and/or gets hacked as a security exploit.

    59. Re:That's all we need by Anonymous Coward · · Score: 0

      Not everyone can even learn the mechanics of programming, how can one expect everyone to be an adequate programmer? We have one guy who came to us with previous experience (not sure what, we don't even know who hired him honestly). In the two and a half years(!) he has been working he has not become better at all. He still types lines of code like his fingers are spasming on or around the space bar. Indentation is a black art to him, one that he tries to fight the text editor over and frequently loses leaving columns and blocks unaligned. Pairing with him the other week it took him 45 seconds of verbally working out a condition to see which of the two branches to follow. The condition was something like:

      if (nav_menu == true && items > 0)

      He sat there reading the words out loud and highlighting them with his mouse over and over.

      Why is he still there? You can't be fired for being bad at your job here it seems. He's been "talked to" dozens of times and has to have one-on-one meetings with his manager every week.

      Maintenance nightmare. Both him and his code.

    60. Re:That's all we need by pla · · Score: 2

      Anyway, the part of your comment about using alpha state for 8+ hrs. Do you have more info on this?

      Oddly enough, I don't - I have no idea whether or not anyone has ever studied that specifically. I have done research (as the "number cruncher" for the psych chair's group at my uni) on attention to a sustained task, and we found that the "pool" model of attention amounts to complete BS; but unfortunately we didn't have the gear to do any brain-wave measuring at the time.

      But speaking from personal experience, a good coding session very clearly takes me (and, I expect, most programmers) into a deep alpha state - I lose almost all awareness of my surroundings (even my own body, things like hunger), and enter a world composed of thought and patterns of logic; the monitor provides mere feedback of what I "want" to go there. Any sudden external distractions, such as a visitor or the phone ringing, takes me 15-30 seconds to properly respond and usually makes me somewhat annoyed/irritable at the interruption of my thoughts. And I can stay in that state basically as long as I want - Or until I need to pee. :)

      Relating back to your point, I have to wonder if that holds true of any "artist" deep in their work - That would prove quite the twist on the stereotypical alpha=daydreaming, beta=attending model.

    61. Re:That's all we need by roman_mir · · Score: 1

      Oh boy, never thought of myself as a 'sadomasochist'.

    62. Re:That's all we need by donscarletti · · Score: 1

      While most people do not have the skills to write a 3d engine, a high performance distributed database, an operating system or an optimising compiler, but most people are capable of writing simple programs to solve problems in the domain they work in. You'd be amazed what two economists I know can do with Excel + VBA. That doesn't turn them into career programmers, but it does make them into much, much more effective economists.

      --
      When Argumentum ad Hominem falls short, try Argumentum ad Matrem
    63. Re:That's all we need by Anonymous Coward · · Score: 0

      As a programmer *and* artist, doing art also soaks up your attention and focus as you've described. OTOH, I tend to find art much less mentally exhausting, and I'm more specialized in programming. (And I have ADD.) So, take that as you will.

    64. Re:That's all we need by Anonymous Coward · · Score: 0

      If properly tuned for the desired temperature, a temperature regulating PID controller should ideally have zero overshoot.
      That said the smallest overshoot I've ever managed to attain was 0.3C, and I've been tuning ovens for seven years now.

         

  9. seems feasible to me by bugs2squash · · Score: 4, Interesting

    Lots of people learn to code on their own from books, online articles and magazines (I did). Surely even a little guidance could kickstart the process the process for a reasonable and motivated candidate.

    --
    Nullius in verba
    1. Re:seems feasible to me by rwven · · Score: 1

      Main problem with that is that for many people, inspiration comes through actually understanding it and truly maturing your skills. It's a hard process to actually kickstart in the first place, and only a select few can successfully do that. You're not necessarily wrong, but it's not nearly as easy as you make it sound. :-P

    2. Re:seems feasible to me by Anonymous Coward · · Score: 0

      Any statistical evidence?

    3. Re:seems feasible to me by wvmarle · · Score: 1

      I'm one of those. Started to learn coding when I was about 12 years old, on an MSX home computer in BASIC. Did interesting stuff with it in the following years, that was fun.

      Later in college and uni some more serious programming classes, teaching TurboPascal. I've put those skills to good use in my studies later, to operate certain machines. And now playing a lot with Python, and also Java (for Android phones).

      All self-learned, with the use of online resources mainly.

      But to say that I'm a good coder? Well that'd be far fetched. I get things done - but I bet many professional coders will look at my code in horror. I know bits and pieces about OO, again enough to make stuff work.

      I know there is a lot that I don't know - there is much more to programming, especially I have no experience with (and no idea how to go about) projects that involve more than one person. Or anything really big, that is to be deployed on many different systems. I don't have that deep and background knowledge of programming and computers in general. I have once fiddled with IRQs and so - that was really interesting and fun to do. But nothing more. And that are the skills that one doesn't learn from a just-code type of course, or from coding books, that are the extra skills what you do get in university or any proper software development course.

      After all, there is so much more to software development than coding.

    4. Re:seems feasible to me by Rockoon · · Score: 1

      Any statistical evidence?

      You mean evidence like all the programmers that existed before colleges taught any form of compsci?

      --
      "His name was James Damore."
    5. Re:seems feasible to me by narcc · · Score: 1

      Wow, it looks like you'd make a really great hire. You're competent, but not arrogant. You know enough to understand your own limitations, and you seem more than eager to learn.

      After all, there is so much more to software development than coding.

      You're insightful to boot!

      I don't know what you do where you work, but I'll bet you're under-appreciated.

    6. Re:seems feasible to me by Aladrin · · Score: 1

      I'm going to agree with Narc. If you self-taught to code, you CAN become an excellent coder. Right now, you're a bundle of raw talent just waiting to be shaped. With a job and a good mentor, you'd be a great programmer in a year. With just the job, it'd take years, but you'd get there.

      The job is necessary as an external motivator. You need someone telling you what they -must- have, even if you currently think it's impossible or ridiculous. You'll eventually get over that, and that's part of the process, too.

      I have a feeling there are many more people out there just like you that just need the right push, and that's why this is a good initiative. Get them started on the path and they can take it from there. But with no push to get started... Well, they may never find out.

      --
      "If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
    7. Re:seems feasible to me by wvmarle · · Score: 1

      LOL don't flatter me so much :)

      And of course I'm under-appreciated, I'm the boss. With 1/2 staff. And not involved in programming at all (and honestly not sure if I would really want that, if offered a job). I program for fun, to get stuff done, or to make my server behave in a way that's convenient to me.

  10. I've met these people by Anonymous Coward · · Score: 1

    There is something about a good programmer. I can only tell you that it seems that they would program whether they got paid for it or not. If you don't have that desire, you never really become a good programmer. People who think, "hmmm... programming, that pays well" are barking up the wrong tree. They may survive in a forgiving atmosphere. If everyone is really lucky, the move quickly into management where they can't do as much harm.

    1. Re:I've met these people by rwven · · Score: 1

      Almost all the project failures and stumbling I've ever been around have been almost entirely management caused. The only way for bad employees to stop causing problems is for them to be fired. :-P Squeaky wheel gets REPLACED.

      You are totally correct about the desire though. The worst coders are the ones who are just doing it "as a job." If the passion isn't there....you're doing it wrong.

    2. Re:I've met these people by kaizokuace · · Score: 1

      what about populating management with people that cant code for shit but at least know what programmers need or can relate to them a little?

      --
      Balderdash!
  11. This will probably work. by Narcocide · · Score: 5, Insightful

    I've worked with plenty of people who had 5+ years of "experience" who perform at the competency level of a 1st year coder. Especially in very large companies I've found that the day-to-day tasks are usually designed to shield the employees from any apparent consequences of their own incompetence or any risk of becoming competent. Typically, 90% of the job is just being attractive and good-smelling enough that your co-workers can be nice to you without trying hard.

    1. Re:This will probably work. by rwven · · Score: 1

      Wait....you know programmers that smell good?

    2. Re:This will probably work. by Issarlk · · Score: 1

      They are not really programmers.

    3. Re:This will probably work. by Anonymous Coward · · Score: 0

      Totally agree.

    4. Re:This will probably work. by JoeMerchant · · Score: 1

      I've worked with plenty of people who had 5+ years of "experience" who perform at the competency level of a 1st year coder. Especially in very large companies I've found that the day-to-day tasks are usually designed to shield the employees from any apparent consequences of their own incompetence or any risk of becoming competent. Typically, 90% of the job is just being attractive and good-smelling enough that your co-workers can be nice to you without trying hard.

      That's called stability. If you're going to grow a company, you want a stable structure that can hire (and fire) readily available people as needed to support the business' growth and contraction cycles. If you try to build a business out of top 1% best in class superstars, you're going to have one hell of a problem finding them in the first place, retaining them after you do get them, and getting them all to play nice together while you have them.

      So, accepting the premise that, once you grow beyond garage-shop size (say 30 employees) roughly 1/2 of your new-hires are going to have an I.Q. below 100, how are you going to structure your system to get productivity out of them? It's even worse than that, since there are a lot of small businesses out there, and small businesses do tend to let the dolts go when times get hard because they simply can't afford to keep them around, what's available in the labor market is, on average, well below average.

      Not saying that you'll never find a good candidate, just that it's kind of like gold mining in an iron-pyrite rich stream.

    5. Re:This will probably work. by dkf · · Score: 1

      I've worked with plenty of people who had 5+ years of "experience" who perform at the competency level of a 1st year coder.

      Ah, people who have had 6 months of experience over and over again.

      --
      "Little does he know, but there is no 'I' in 'Idiot'!"
  12. 2600 condones this! by Anonymous Coward · · Score: 0

    One year is plenty of time to learn to write crappy code.

  13. It'll be funny by Anonymous Coward · · Score: 1

    It will make for some good comedy when we start getting CV's coming through from all this. Unfortunately, the signal : noise ratio is just going to make it harder for properly qualified candidates to get noticed.

    1. Re:It'll be funny by pitzG · · Score: 1

      You can say that again, but firms like Google/Microsoft/ most other tech firms/Etc. don't bother to even *sample* more than 1% of their resume queues, so adding more noise probably won't make any difference. The sampling rate isn't even high enough to ascertain any statistically relevant or meaningful measure of the quality of the applicant stream. I'm willing to bet that if tech firms were willing to take *all* candidates for their jobs into serious and legitimate consideration, that they would have no problem filling all of the positions they have available. But throwing away 99% of the resumes without even looking at them definitely is highly problematic.

  14. Simple is hard by Anonymous Coward · · Score: 1

    Solving real-world software problems requires a lot more than understanding the syntax of a language or two. Those who complete this course and then try to get jobs will learn that lesson the hard way.

    1. Re:Simple is hard by j35ter · · Score: 2

      No, you insensitive clod! The guys who made the mistake of hiting them will learn the lesson the hard way! :)

      --
      Delta-Mike November Bravo Tango
    2. Re:Simple is hard by Terrasque · · Score: 1

      There's a comment on those "Teach yourself X in Y days" books by Peter Norvig, called "Teach Yourself Programming in Ten Years".

      I suspect most of it is relevant to this thing, too.

      I've been programming for about 15 years now (most of it on hobby basis) and I still learn new things.

      --
      It's The Golden Rule: "He who has the gold makes the rules."
  15. Off by one error by Anonymous Coward · · Score: 2, Insightful

    Average users have a hard enough time even using software competently after a year's time. Let alone creating it.

    Just think about many people still don't know how to find something simple like the control panel in XP after all these years...

    1. Re:Off by one error by Spad · · Score: 1

      That's ~90% lack of caring rather than lack of ability; not that it's a good thing.

      The people who "don't know" where Control Panel is, despite having been directed to it countless times in the past by support staff are the same people whose car tyres are flat, never top up the oil and don't bother to indicate because they "don't care how cars work, as long as they get me to where I want to go".

      If people are going on a course to learn to code, you have to assume that they have at least some interest in doing so.

    2. Re:Off by one error by JoeMerchant · · Score: 1

      Average users have a hard enough time even using software competently after a year's time. Let alone creating it.

      Just think about many people still don't know how to find something simple like the control panel in XP after all these years...

      I made $60 one night for an "emergency tech call" - the guy didn't tell me what was the problem over the phone, just that he needed my help. When I arrived, we talked about status of a few ongoing projects, but the only real reason for me to be there was because his sound output had stopped.

      The volume control was muted (and visible as such in the task bar).

  16. It's oh so much fun by Anonymous Coward · · Score: 1

    trying to fix or maintain code written by some half-ass amateur that got a certification or read a few books and "taught himself to code" in one month. The only thing better is when it's someone from management that does it because "coding is easy".

    1. Re:It's oh so much fun by Anonymous Coward · · Score: 0

      People end up paying my company good money for me to fix and maintain that code. I call it job security

    2. Re:It's oh so much fun by anubi · · Score: 1

      Coding IS easy!

      So is surgery!

      But doing it right, well ... that takes a bit more know-how.

      A lot more.

      --
      "Prove all things; hold fast that which is good." [KJV: I Thessalonians 5:21]

    3. Re:It's oh so much fun by rwven · · Score: 1

      Yeah I just LOVE those moments when a manager offers to help coding so you can meet a deadline. That's happened twice.... I just want to say "don't you DARE." I loved how one of them used his experience writing reports using SQL at a chem company as reasoning why he could do it.

    4. Re:It's oh so much fun by GrantRobertson · · Score: 1

      When I was an IT manager at a hospital, we had a pharmacist as a CIO merely because he once wrote a program in GWBasic to print labels for pill bottles.

  17. Just what we need... by Lumpy · · Score: 4, Insightful

    Someone making promises that are fake but will reinforce uneducated PHB's

    "Why should we pay you more? anyone can become a expert coder by studying at home part time for a year."

    --
    Do not look at laser with remaining good eye.
    1. Re:Just what we need... by stephanruby · · Score: 2

      Learn to write in one year through a free interactive web site, and get a job at CNN. That's what I did!! Even billionaire-politician Michael Bloomberg, my hero, is learning his letters as we speak. Rumor has it, he'll become a proficient Bloomberg journalist by next week.
      - Rushkoff

    2. Re:Just what we need... by j35ter · · Score: 0

      I have seen many experts with 1 year coding experience...mostly from India, you insensitive clod

      --
      Delta-Mike November Bravo Tango
  18. If you can read this, you can get a good job. by stevegee58 · · Score: 3, Insightful

    I remember first semester freshman year. The weed-out EE course was full of bright-faced eager kids convinced they were gonna get a good paying job when they graduated.
    2 weeks later the class size was cut in half when they found out how much work was involved.
    Anyone can learn to write a "Hello World" program but that doesn't make them a software professional.

    1. Re:If you can read this, you can get a good job. by Anonymous Coward · · Score: 0

      Jokes on the ones who stuck it out. The ones who dropped out of engineering got a business degree, and subsequently a job.

    2. Re:If you can read this, you can get a good job. by Anonymous Coward · · Score: 0

      Jokes on the ones who stuck it out. The ones who dropped out of engineering got a business degree, and subsequently a job.

      HAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA

      When the 2008 recession hit, people all around me starting losing their jobs. At the same time not only was I and other engineering friends I had secure in our jobs, but we were hiring new guys non-stop and handing out 10% raises after the yearly evaluations.

      You certainly have potential to earn more money with a business degree than an engineering degree. That said, you also have a potential to crash and burn straight to the unemployment line. Engineering is where the job security is at.

    3. Re:If you can read this, you can get a good job. by bky1701 · · Score: 1

      "Anyone can learn to write a "Hello World" program but that doesn't make them a software professional."

      Of course, neither does an Electrical Engineering weeder class.

    4. Re:If you can read this, you can get a good job. by pitzG · · Score: 1

      Yeah right.. Why is most of my 2002 EE/CS graduating class, from a top quartile university, chronically unemployed for much of the past decade? Employers not even responding in good faith to our applications? While the business guys had very little trouble, comparatively speaking, joining the workforce? I've personally coded assembly for embedded TCP/IP projects, and designed embedded ethernet solutions, yet hundreds of resumes later to prominent firms in the business, and not even a single reply to my applications.

    5. Re:If you can read this, you can get a good job. by Ryanrule · · Score: 1

      Do you live in a big city? Seriously, I act like a major cock at my job, and really CANT be fired, because the demand is so high for people who know a damn thing. This is crazy, but INSOURCING has become a thing. A BIG thing. Execs see this buzzword, and jump on board. Reap the rewards. Suck those motherfuckers dry.

    6. Re:If you can read this, you can get a good job. by pitzG · · Score: 1

      I apply to jobs in big cities. I have a big city address and phone number. But I can't afford to live in a big city anymore. Still, as a top quartile EE/CS grad, I can count the number of responses to my job applications (thousands of them) on my hands over the past decade from tech employers. When I used to apply to jobs on Monster, it wasn't uncommon to see most jobs, even entry-level ones, have 100, 150 other applications submitted. Gave up on that and started targetting recruiters directly. Still no bites. Which leads me to believe that the whole concept that there's any worker shortage is complete bullshit.

    7. Re:If you can read this, you can get a good job. by Alex+Belits · · Score: 1

      Don't go through recruiters. Ever. Craigslist is not just for apartments anymore.
      Whenever possible, try to bypass HR, too.

      --
      Contrary to the popular belief, there indeed is no God.
    8. Re:If you can read this, you can get a good job. by pitzG · · Score: 1

      Of course, I avoid 3rd party recruiters like the plague -- most of them have called me up, promised the world with all their proprietary 'inside contacts', but have delivered practically nothing. But internal recruiters, like HR people, should be talking to folks like me if they're actually looking for talent out there. As for craigslist, I've tried a few times. Didn't seem to get much in the way of professional responses. If they're not willing to pay for a job ad, then just how important is the job really to them? I realize my skillset is more hardware-centric than software (I am an EE after all, and most of my coursework/projects concentrated on the communications/networking side of things, not app programming or Java), but everyone knows that the embedded skillset is somewhat more difficult to learn than applications programming -- so why guys like me aren't being picked up merely for our aptitude is really hard to understand.

    9. Re:If you can read this, you can get a good job. by sydneyfong · · Score: 1

      everyone knows that the embedded skillset is somewhat more difficult to learn than applications programming -- so why guys like me aren't being picked up merely for our aptitude is really hard to understand

      You're saying you had a decade of "free time" and never bothered to learn application programming, despite that's what the industry wants? If I were an employer, why would I want to hire somebody who thinks they're entitled to the job because they "learnt something hard"?

      --
      Don't quote me on this.
    10. Re:If you can read this, you can get a good job. by Anonymous Coward · · Score: 0

      How about if you can make a piece of software that lists your C-tapes?

    11. Re:If you can read this, you can get a good job. by pitzG · · Score: 1

      Where am I supposed to focus my efforts if employers won't even talk to me, respond to my resume, etc.? Give me a few weeks and I'll be up to speed in practically any language or API that is suitably documented. I've written code in many languages, but apparently not the specific fad language of the day. Embedded, BTW, is a superset of applications and systems programming. As for why an employer would want to hire someone like me, well employers need smart people, right? Programming languages can be learned in weeks; aptitude and problem solving ability is far more important in the grand scheme of things. Look, if employers were really needing people, would they really care if it took me a few weeks to learn some the syntax and API's of their language/environment of choice? Or is the whole idea of employers needing people really a big farce, and these articles appearing on CNN websites and elsewhere merely intended as infomercials to curry favour with the public to bring in more guest workers?

    12. Re:If you can read this, you can get a good job. by pitzG · · Score: 1

      I've met the stated qualifications on nearly every job I applied for. The employers are innudated with hundreds of excellent resumes per position though (ie: Google's ratio of >1000 resumes per actual position they hire for!). That is why the whole premise that there is a shortage of coders, or a shortage of engineers (software, hardware, systems, or otherwise), strikes me as ridiculous. Especially with the stagnant salaries. As for why an employer would want to hire employees -- perhaps to get a job done? To move their business forward? Most of the hiring in the past decade has been of guest workers, which is why the industry is in such a state of disaster. The brightest folks are on the sidelines. Remember that in the late 1990s, most good CS schools had severely restricted enrolment quotas, which meant that only the brightest undergrads were even permitted to study CS. When they graduated circa 2001-2005, entry-level opportunities were practically non-existent.

    13. Re:If you can read this, you can get a good job. by Alex+Belits · · Score: 1

      You're saying you had a decade of "free time" and never bothered to learn application programming, despite that's what the industry wants?

      Actually embedded systems developers are more in demand than "application" (Windows desktop and HTTP-connected server-side software) developers.

      --
      Contrary to the popular belief, there indeed is no God.
    14. Re:If you can read this, you can get a good job. by stewbee · · Score: 1

      Time to commiserate. I too am a degree carrying EE and I went to grad school specializing in electromagnetics, but I feel like I am pretty much in the same boat as you. While I started off as an RF circuit designer, I have since gone and done jobs that are mostly programming and algorithm oriented (since 2008). While I have been fortunate enough to not have been unemployed at all (finished all schooling in Dec 2004, started first job in Jan 2005), I have been looking for embedded programming/DSP jobs for the past 4 months and have not had much luck. I certainly try to emphasize my programming and DSP aspects of my experience, but I don't have the "exact" experience they are looking for.

      My favorite rejection so far was for an embedded SW position that required hydraulics knowledge, which was under the "required" portion for experience. I didn't get the job because of this part of the requirements. Never mind that I pretty much all of the other experience they were looking for, and that not many SW people also have had much hydraulics experience, or that hydraulics is an easy enough concept to probably allow for that to be learned through OJT. Sigh!

      tl;dr version: I agree with your assessment. I think that there are too many people applying for the same positions which allow companies to be very selective on who they can bring on, even though I know that I am a better programmer than some of the SW engineers I work with. My current title and previous positions just don't give me a chance to change career paths.

    15. Re:If you can read this, you can get a good job. by donscarletti · · Score: 1

      but everyone knows that the embedded skillset is somewhat more difficult to learn than applications programming

      Interesting statement to make. Most embedded stuff I've worked on has been well under 30k lines of C/ASM, commercial applications generally start in the millions. Not to mention that an application runs in an unknown environment with limited possibility of getting better diagnostic information back than "the program crashed".

      --
      When Argumentum ad Hominem falls short, try Argumentum ad Matrem
  19. Well of course... by Pharmboy · · Score: 4, Insightful

    ...everyone knows that if you will just take a few weeks to learn to program, you can start making 60k or more a year within a month or two.

    Ok, granted, this story wasn't quite THAT bad, and the idea that everyone should take a few weeks to learn what programming IS, the concepts, is probably a good idea. However, the idea that you can learn to be a programmer in one year is foolish. I've never had any formal training, self taught in Perl, javascript, some PHP, and been doing it as a minor part of my job for 15 years, and I'm not a programmer. Having at least moderate skills, to understand what a shell script or batch file is, what HTML code is and does, will help you in your job, but you aren't going to start creating more real programmers with one year, even if that is all they do is learn 24/7 for that year.

    What there is a shortage of is people with MORE than one year of training as a programmer. People who can write good code, instead of the bloated crap that I write to just get the job done. But that isn't what this article is about, it is about promising something that won't happen, that learning a little coding will guarantee you a job. It won't help a forklift driver, someone used to working on an assembly line that is now part of a closed factory, or half the people looking for work now. It will do them personally good to understand a little, but it won't be the cure for our unemployment.

    Unemployment is high right now, not because companies can't find good people, but because companies are afraid to take on the responsibility (and liability) of expanding and hiring until they absolutely have to, due to a messed up political and financial environment.

    --
    Tequila: It's not just for breakfast anymore!
    1. Re:Well of course... by metalix · · Score: 1

      Unemployment is high right now, not because companies can't find good people, but because companies are afraid to take on the responsibility (and liability) of expanding and hiring until they absolutely have to, due to a messed up political and financial environment.

      IT unemployment is low! (I've heard ~2% more recently)

  20. In a year? by scottbomb · · Score: 4, Interesting

    Sorry, but I've been at it for about that long (learning Java) and I'm nowhere near qualified to do it professionally. Sure, I know the syntax and I have a good understanding of OOP but there's a LOT more for me to learn before I can write software people will actually find useful.

    I love programming and I love learning about it. The discouraging part is that there is almost ZERO entry-level work in programming. All the ads I see demand "3-5 years experience", but that's another story.

    1. Re:In a year? by bananaquackmoo · · Score: 3, Informative

      The beautiful thing about programming is that, relative to other professions, it is PAINFULLY simple to get those 3-5 years. Most of the time it doesn't even need to be at a professional workplace, as long as you can demonstrate growth or meaningful contributions. Work on open source projects. Do internships. Make software for yourself. Program robots. Automate your home. Tweak your kernel or window manager. Script some events. Just keep doing it, and in no-time you will have 3-5 years of experience. Heck, an intern where I work programmed his own server monitoring software for his own use, on his own free time, before he had even heard of us, and now the entire company uses it.

    2. Re:In a year? by bananaquackmoo · · Score: 1

      And yes, I know that isn't 3-5 years in a professional environment, but it is at least 3-5 years of programming. Proving you are capable is the first step towards learning how the professionals would do it. For example, I never worked with forms or databases before, nor had used SVN, nor Eclipse, but I knew enough coding they were impressed and hired me.

    3. Re:In a year? by viperidaenz · · Score: 2

      I went from "junior" to "senior" Java Developer in about a year. That was about 3 years ago. I did start self-teaching somewhere in the early 90's though. My entry in to the developer job role was facilitated by getting an "Application Support" role and voicing my aspirations to my manager.

    4. Re:In a year? by Surt · · Score: 1

      You may be looking in the wrong places. Most small companies don't have room to let people start at the bottom. For an entry level position, medium to large companies are a more likely success. Google, for example, is hiring people straight out of college like crazy right now. Apple and facebook are also.

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
    5. Re:In a year? by Anonymous Coward · · Score: 0

      Sorry, but I've been at it for about that long (learning Java) and I'm nowhere near qualified to do it professionally. Sure, I know the syntax and I have a good understanding of OOP but there's a LOT more for me to learn before I can write software people will actually find useful.

      I love programming and I love learning about it. The discouraging part is that there is almost ZERO entry-level work in programming. All the ads I see demand "3-5 years experience", but that's another story.

      I was discouraged by the 3-5 year experience requirement out of college. I was only a computer science minor and had got rejected from jobs that offered 50 to 60 a year. But I was forced to work on mostly my own projects, and continued to learn programming on my own. About a year later I started picking up clients charging the typical consulting rate. For about a year and a half (graduated spring '10) I have been doing all my work from home, and have still been working on my own projects that I am passionate about. This makes all of the difference in the world. My income right now (about 17k a month) is way higher than it would ever be at my age working for the man.

    6. Re:In a year? by scottbomb · · Score: 1

      Great story, thanks for sharing that. I have heard about the freelance work and I guess that's how most get their start?

    7. Re:In a year? by scottbomb · · Score: 1

      Excellent points from all of the above, thanks. Perhaps I've been looking at the experience part from the wrong perspective.

    8. Re:In a year? by Zmobie · · Score: 2

      No not so much. Freelance work that actually pays well is kind of hit or miss unless you do straight contract work (which usually requires about the same or more experience). 17k a month is impressive just doing freelance, but it somewhat depends on how much experience the guy had before graduating.

      Now, I do recommend you do stuff on your own because that is BY FAR the best way to woo an employer or prospective client. My company has been looking through a metric shit ton of new college grads and people that have a decent self made project are thrust WAY up the list. Keep in mind that a lot of companies that do software development consult their developers about prospective employees, and hell my company even has the developers conduct some of the interviews directly.

      Keep at it and in a few years you will probably be able to get a lot more hits and general programming respect. A degree or certs are nice, but those personal projects are what really impress people.

    9. Re:In a year? by Gorobei · · Score: 1

      There are a ton of jobs out there for people without "3-5 years experience," but who do understand how software works. We basically hire anyone who is not a lunatic who is able to answer all questions along the lines of:

      1. What's a hashtable? Time to find/insert/delete? How would you implement one? Issues to consider?
      2. Explain the execution time of strcmp("apples", "apple")
      3. Describe how a couple of sorting algorithms work.
      4. You have X on your resume, please explain it clearly.

      It's scary how many people (even PhDs) can't answer these questions. It's like interviewing a lawyer who is a bit unclear on procedure, but figures his raw talent will win you your case.

    10. Re:In a year? by MrCrassic · · Score: 1

      Yeah...a lot of really good stuff is written by people just like the OP that are just learning. The other good thing about software is that it's an evolving work. Nobody cares if it's bloated or whatever; if it's a cool idea, helps in some way and is acceptable enough to use, people will like it. The other awesome thing is that if you do reach that point, you learn as you improve and everyone benefits!

      It's not like being a doctor where you have to be GOOD right out the gate since people's lives are at stake. Unless, of course, you want to code medical instruments or things for planes...

    11. Re:In a year? by Anonymous Coward · · Score: 0

      Google doesn't even give the 'time of day' to 99% of the applicants in its resume queue. A joke that often goes around is that Google could receive a job application from Linus Torvalds for a Kernel Engineer position and not even get back to him.

      When a firm only samples less than 1% of the talent, statistically, that means that a lot of extremely intelligent/bright people will be passed over.

    12. Re:In a year? by ajo_arctus · · Score: 1

      If somebody gave you a detailed spec for software that they found useful, you'd be surprised at just what you can achieve already. Useful software doesn't have to be highly complicated, it might just be a console app for fetching data from a remote feed and storing it in a database. Useful software is useful. You clearly have the right aspirations, you just need to find the purpose. Once you complete your first project it kind of just snowballs as you grow in confidence and ability.

      And there are plenty of entry level jobs. If you speak to those companies looking for 3-5 years and say you're willing to work on a trial basis to prove yourself, you'd be amazed at how willing they are to give you a job. They will value your eagerness/ambition just as highly as they value 3-5 years experience (which everyone knows actually means nothing anyway).

    13. Re:In a year? by wvmarle · · Score: 1

      Why are you not qualified to do it professionally? The difference between a professional and a hobbyist is that the first gets paid for it. That's all. They're not necessarily better.

      And why would you need to learn so much for writing software that people find useful? With no experience in Java I picked up programming for Android, and within a month I had an app on the Android Market that people find useful. Now I'm not making a penny off of it (free, open source, and no ads), as I did it for fun. But that's not the point here: the point is you don't need years of experience to make something useful. You just have to do it.

    14. Re:In a year? by narcc · · Score: 1

      I have a good understanding of OOP

      You'd be the first. The rest of us still haven't come to any agreement on what even constitutes OOP. Even Alan Kay, who coined the term, regrets it (the mess that often passes for OOP today isn't even close to his original vision.)

      Give Steve Yegee's excellent essay Execution in the Kingdom of Nouns a read.

      You might also want to take a look at some of the discussions on c2 such as this one, and this one

    15. Re:In a year? by Anonymous Coward · · Score: 0

      It's scary how many people (even PhDs) can't answer these questions.

      Hey everybody! Look at ME! I'm super smart compared to those stupid PhD's with their dumb education!

      I'm so smart that I'm in charge of hiring PhD's. See how cool and interesting I am?

      (Does anybody like me yet?)

    16. Re:In a year? by O('_')O_Bush · · Score: 1

      There is a good reason for that. Programming isn't a blue collar profession, you can't expect to walk in to a programming job with language knowledge any more than you can expect to walk into a courtroom as a lawyer with some tax code knowledge.

      At one time, this was because the only people allowed to use computers were scientists/engineers. Now its because all the entry-level tasks can be outsourced or automated for much less than 1/5th the cost of employing a body.

      This is what is particularly deceiving about what CNN/that site claims. Sure, the medical field might be desperate for people, but they want doctors, not nurses. Same goes for the software development field.

      --
      while(1) attack(People.Sandy);
    17. Re:In a year? by JoeMerchant · · Score: 1

      Stop reading the ads - work up some personal contacts and get a trial audition with somebody who needs somebody to do something. You just might surprise yourself with how competent you are.

    18. Re:In a year? by Anonymous Coward · · Score: 0

      ...and in no-time you will have 3-5 years of experience.

      Won't it take 3 to 5 years to get 3 to 5 years of experience?

    19. Re:In a year? by Anarchduke · · Score: 1

      1. its the table my dealer has all his stuff on. you insert the money and delete a baggie? Dont' try and swipe an extra baggie unless you want a complementary bullet.
      2. its like really, really fast man, like a 1/100 of a second or something
      3. yeah, they like, sort stuff, even alphabetically sometimes!
      4. well, the X is a letter in the English language, so if i had a word that contains an X I kinda have to put it in there. but if it bothers you i could substitute "ecks"

      --
      who prays for Satan? Who in 18 centuries has had the humanity to pray for the 1 sinner that needed it most? ~Mark Twain
  21. Who needs coders? by hawguy · · Score: 5, Insightful

    We already have too many coders at my current employer, what we need are software developers that know how to architect a maintainable system.

    1. Re:Who needs coders? by Anonymous Coward · · Score: 0

      Better than having too many architects that don't know the real world cost of their over architected systems.

    2. Re:Who needs coders? by Hognoxious · · Score: 1

      Not at all, I've seen projects with too many architects and usually they have very few implementation issues and ongoing support problems are nonexistent.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    3. Re:Who needs coders? by Anonymous Coward · · Score: 0

      I remember talking with a process engineer in the old days. I asked him what language his company used for their chemical plant. "Pascal" we develope in JRT Pascal.
      "If we need to make things go faster, we just buy more hardware. Its not hard to make a running program fast, but it is hard to make a fast program run."

         

  22. I smell a pile of low cost poor quality cowboys... by Kenja · · Score: 1

    I smell a pile of low cost poor quality cowboys coming onto the market and underbidding the competent contractors. Works for me as my job tends to be cleaning up after someone who vastly exaggerated their abilities and got in too deep on a project they dont understand.

    --

    "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
  23. Here we go... by wbr1 · · Score: 4, Funny

    main ()
    {
    printf )"Hello World! I am now a Software Developer!\n");
    }


    Congratulations, here is your certificate of completion.

    --
    Silence is a state of mime.
    1. Re:Here we go... by Anonymous Coward · · Score: 0

      No certificate for you until you figure out why that won't even compile.

    2. Re:Here we go... by wbr1 · · Score: 5, Funny

      No certificate for you until you figure out why that won't even compile.

      loop until realization(errors)==sarcasm

      --
      Silence is a state of mime.
    3. Re:Here we go... by Anonymous Coward · · Score: 0

      Syntax error in Hello World? Really?

    4. Re:Here we go... by Anonymous Coward · · Score: 3, Funny

      It's because he spelled print wrong, what a putz.

    5. Re:Here we go... by xski · · Score: 1

      If it helps any, I got it.

    6. Re:Here we go... by Anonymous Coward · · Score: 0

      You fail for not knowing what printf() does.

    7. Re:Here we go... by multiben · · Score: 1

      *You* fail for not inferring the joke.

    8. Re:Here we go... by Zmobie · · Score: 1

      I don't know why you're surprised, most people end up with syntax errors when they copy and past working code...

    9. Re:Here we go... by t4ng* · · Score: 2

      Okay, now I can't figure out any more who is being sarcastic, who is sarcastically pretending to not get it, and who is really not getting it! :-D

    10. Re:Here we go... by proverbialcow · · Score: 1

      There are two reasons I can see...the other one is that he forgot to cast main() as type 'int'.

      --
      The only surefire protection against Microsoft infections is abstinence. - The Onion
    11. Re:Here we go... by Anonymous Coward · · Score: 0

      Meh, many compilers are lax enough about the type of main that that would still compile (the main part, I mean. The syntax error won't.)

    12. Re:Here we go... by mevets · · Score: 1

      if (!get(joke)) /**/;

    13. Re:Here we go... by Quince+alPillan · · Score: 2
      I got this! I'm a world class programmer and I deserve the senior programmer position. I'll prove it to you by showing you my certificate that I received from CodeAdacemy!

      g++ certificate.cpp -o certificate.out
      certificate.cpp: In function "int main()":
      certificate.cpp:3:1: error: "printf" was not declared in this scope
      certificate.cpp:3:7: error: expected ";" before ")" token

      Wait, that didn't work. Give me a second.

      ruby certificate.rb
      certificate.rb:3: syntax error, unexpected ')', expecting tASSOC
      printf)"Hello World! I am now a Software Developer\n");
      certificate.rb:3: syntax error, unexpected ')', expecting $end
      printf)"Hello World! I am now a Software Developer\n");

      I don't understand. What do these errors mean? Why isn't my certificate of completion printing? I'm a programmer now, right? Right?

    14. Re:Here we go... by AK+Marc · · Score: 1

      It's slashdot, none of them are getting it.

    15. Re:Here we go... by proverbialcow · · Score: 1

      I thought about that, and you're probably right. But even if it did, the linker might freak out about the lack of type, and/or the absence of argc/argv. And even if the linker was cool enough about it, since he never returns from main(), the program would dump core/crash.

      Congratulations, /.: You've made "went to the library" the coolest thing I've done tonight.

      --
      The only surefire protection against Microsoft infections is abstinence. - The Onion
    16. Re:Here we go... by Anonymous Coward · · Score: 0

      That wont compile, two close parens.

    17. Re:Here we go... by Provocateur · · Score: 1

      yeah, just like that co-worker that wrote on a post-it: It's floopy, not flopy disk. He was certain there was a double-something in there, and he went for it.

      --
      WARNING: Smartphones have side effects--most of them undocumented.
    18. Re:Here we go... by kaizokuace · · Score: 1

      question is, which one is the hipster!

      --
      Balderdash!
    19. Re:Here we go... by dkf · · Score: 1

      I thought about that, and you're probably right. But even if it did, the linker might freak out about the lack of type, and/or the absence of argc/argv. And even if the linker was cool enough about it, since he never returns from main(), the program would dump core/crash.

      If it's C (not C++) it will probably work though the exit code will be thoroughly arbitrary (with the most likely exit code still being success due to probable propagation from the result of the printf call). It depends on the exact details of the ABI.

      Anyone writing such code for real deserves to be forcefully reeducated.

      --
      "Little does he know, but there is no 'I' in 'Idiot'!"
    20. Re:Here we go... by ImprovOmega · · Score: 1

      No, it will often default to void type for main if unspecified, and so will not expect a return value. void main(void) was a VERY common start to programs in my early days with C/C++ (as mentioned before though, this depends on how lax or strict the compiler is). He would also need to #include or it won't know what printf means.

  24. Lean-to by Anonymous Coward · · Score: 3, Insightful

    I've been in this business for 30 years. Most code I've seen does indeed look like it was designed and written like a "lean-to".... and I have great faith that it will continue to do so as long as I live, and long after I'm gone too.

    1. Re:Lean-to by Confusedent · · Score: 0

      Comment was better when I'd read it as, "I've been in this basement for 30 years. Most code I've seen...."

  25. two major points to the article by binarstu · · Score: 5, Insightful

    A major argument of the opinion piece is that having at least a rudimentary understanding of how computers and software actually work is increasingly important, and that learning some programming is a good way to accomplish that. I doubt anyone here would argue with that.

    The second half of the article, while not explicitly saying it, does suggest that if a person spends a little time learning to code they'll magically get an awesome ("high-paying", in the words of the author) job. This is a major oversimplification, at least. The author provides no convincing evidence that this is true, except for a quote from his CEO friend.

    1. Re:two major points to the article by Tom · · Score: 1

      A major argument of the opinion piece is that having at least a rudimentary understanding of how computers and software actually work is increasingly important, and that learning some programming is a good way to accomplish that. I doubt anyone here would argue with that.

      I will.

      A little knowledge is often more dangerous than no knowledge. Anyone who has worked for a boss with a little knowledge about what you do can attest to that. The obvious reason is that the 101 in any field leaves out many of the difficult and complex details. When you take physics 101, things seem fairly simple and straightforward, most of the equations are linear or at most power laws. You are in absolutely no way prepared to understand or even appreciate the complexities of quantum physics.

      I've seen it time and time again - people, especially people with the power to make decisions - with a little knowledge are the worst kind. The guy who knows Access is the one who has the least appreciation for real databases and what a real database admin does. The guy who knows Word values the job of a real secretary, writer or layouter the least. The boss who once wrote a few scripts in Visual Basic does the most damage to the software development team.

      Please don't teach people how to write a little code. That's like telling them the basics of driving. They will end up thinking they can drive, take out a car and kill someone.

      --
      Assorted stuff I do sometimes: Lemuria.org
    2. Re:two major points to the article by JoeMerchant · · Score: 1

      The second half of the article, while not explicitly saying it, does suggest that if a person spends a little time learning to code they'll magically get an awesome ("high-paying", in the words of the author) job. This is a major oversimplification, at least. The author provides no convincing evidence that this is true, except for a quote from his CEO friend.

      Supply and demand - I graduated in 1990 - starting coders were paid $30-35K, by 1995 you'd be lucky to be making $40K. Dot com hit, demand spiked up, kids straight out of my same university with my same degree were getting starting offers in the $70K range. With those offers on the table, supply soon increased, starting pay is more chaotic now, but mostly sinking back to that $30-40K range, even though cost of living is up significantly.

      Magic koding skool koderz may get high-paying jobs for a little while, until there are a bunch of them on the market.

  26. Obligatory "you kids get off my lawn" by devphaeton · · Score: 5, Insightful

    Peter Norvig's "Teach Yourself To Programming In Ten Years" http://norvig.com/21-days.html

    Pretty much sums it up. There have also been many posters so far that have mentioned you can't just "make" someone a programmer. They have to want it, to enjoy it and to already "be" a programmer in mind and spirit. Same goes for the new British thing of forcing gradeschool kids to learn programming. Having it available as an option would be great, but forcing them into it won't give you more programmers, much less good ones. Meanwhile, all the kids that were going to become programmers will still do it whether you encourage them or not. Simple as that.

    Surely the "Lean" up above is a typo, but there is a serious problem of late with Slashdotters and their spelling and grammar abilities. People who learned English as a second or third language get a pass, but for all you up and coming kids who are native speakers, what the fuck?

    (my two hamfisted cents. I'm going back to Skyrim)

    --


    do() || do_not(); // try();
    1. Re:Obligatory "you kids get off my lawn" by Anonymous Coward · · Score: 1

      "Same goes for the new British thing of forcing gradeschool kids to learn programming."
      Why is this bad?

      The Brits, and you too, are also forcing gradeschool kids to learn mathematics.
      Do you think they expect all grade school kids to become mathematicians by this forced learning?

      I am a mathematician. Mandatory training in mathematics at gradeschool level will not make the kids mathematicians.
      Training grade school kids in programming will not make them programmers.

      That said, learning and getting exposure to some basic mathematics and programming is definitely beneficial for their development and whatever their future career will be.

      I don't see the problem by forcing them to learn useful things. That is what school is all about.

    2. Re:Obligatory "you kids get off my lawn" by Anonymous Coward · · Score: 0

      but forcing them into it won't give you more programmers, much less good ones

      In high school I was required to take biology, gym and art. I didn't enjoy any of the classes, and I didn't end up being a scientist, an athlete or an artist. But taking those classes did make me appreciate in some small way both the world around me, and people who excel at those fields.

      At the very least, forcing everyone to take a year or two of programming may make them appreciate the art of programming a little bit more.

    3. Re:Obligatory "you kids get off my lawn" by unity100 · · Score: 1

      mod parent up. i posted.

    4. Re:Obligatory "you kids get off my lawn" by Anonymous Coward · · Score: 0

      I used to get off people's lawns but I took an arrow on the knee

    5. Re:Obligatory "you kids get off my lawn" by Anonymous Coward · · Score: 0

      Obligatory: PHORONIX! PHORONIX! PHORONIX!

      (and some lowercase stuff for a while so that the filter will let me emphasize the line above. :-( )

    6. Re:Obligatory "you kids get off my lawn" by gajop · · Score: 1

      As long as the ratio is maintained I'm ok with it. I've seen many books labelled "Learn how to program in {24, 7} days.", however I've also seen the book "Learn how to become a manager in 1 minute" so I think all is as it should be.

    7. Re:Obligatory "you kids get off my lawn" by devphaeton · · Score: 1

      Lemme guess...someone stole your sweet roll?

      You get +5 Bethesda points, Anonymous Coward.

      --


      do() || do_not(); // try();
    8. Re:Obligatory "you kids get off my lawn" by Hognoxious · · Score: 1

      Peter Norvig's "Teach Yourself To Programming In Ten Years"

      I prefer to teaching me the Englishes.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    9. Re:Obligatory "you kids get off my lawn" by roman_mir · · Score: 1

      People who learned English as a second or third language get a pass

      - why should we get a pass? Fcuk id, no psases for anibady.

    10. Re:Obligatory "you kids get off my lawn" by MindStalker · · Score: 1

      "Same goes for the new British thing of forcing gradeschool kids to learn programming. Having it available as an option would be great, but forcing them into it won't give you more programmers, much less good ones."

      I disagree, programming is much like writing. You can teach a million kids how to write, but only a small handful of them will come out with the ability to write a novel much less a decent essay. Does this mean we shouldn't be teaching kids how to write? My wife knows how to program, she is not a programer by any stretch, but she still uses those abilities on a regular basis to write excel macros and other small automations to get her job done. Programming is the new literacy, eventually everyone will be expected to have some basic programming ability.

    11. Re:Obligatory "you kids get off my lawn" by Anonymous Coward · · Score: 0

      Well I can't speak to the "forcing grade school kids" thing but teaching them programming is a good thing. You won't get more programmers but that's not the point. You don't teach kids maths to get mathmetitians and you don't teach 'em biology to get biologists, not primarily at any rate. You teach them so they is educated; you teach so they can learn to think better and grow.

  27. You know what? by xrayspx · · Score: 1

    /Be/ elitist. Go ahead, it's justifiable.

  28. Dot.com Bust 2.0 by still-a-geek · · Score: 1

    If you want to see dot.com Bust 2.0, this will contribute to it. Do you remember the dot.com era? Most of those people with no technical or coding background who tried to learn how to code in 1 year (or less) and obtained some flea-bag certificate were the first ones to be let go. And yes, there were a lot of them. Without having the fundamentals of data structures, coding style, documentation skills, and good logic and problem solving skills, those new "coders" will have a very short career, if any. Most companies learned their lesson from dot.com 1.0.

    --

    "Happily lived Mankind in the peaceful Valley of Ignorance." -- Hendrik Willem Van Loon
    1. Re:Dot.com Bust 2.0 by Anonymous Coward · · Score: 0

      You sound like one of those guys they kept to clean up the mess? Now that you've got it working reasonably well *and* documented, you are going to be really pissed when you're replaced by the next generation "cert-holders"

    2. Re:Dot.com Bust 2.0 by still-a-geek · · Score: 2

      And you're the guy we probably fired.

      --

      "Happily lived Mankind in the peaceful Valley of Ignorance." -- Hendrik Willem Van Loon
  29. Learn to be a pro.... by JetScootr · · Score: 1

    .....air conditioner repairman in a few interactive web sessions per week for a year? chef at a 5 star greasy spoon? TV sitcom writer ? What professionals (esp unions) would be insulted by such a trivializing of their careers? Computers are the most complex machines every devised. How good could such a 'professional' be? (claimer: I am pro developer)

    --
    Pavlov wouldn't be so famous if he'd used a can opener instead of a bell.
    1. Re:Learn to be a pro.... by Technician · · Score: 1

      Even some "Pro" air conditioner repairman are little more than scrip checklist guys who don't really understand the concepts.

      I am Not an AC guy, but am self taught when I worked in cryptology, we maintained our stuff as much as possible to limit shutting down operations so outsiders can service the systems.

      One boss I had was having trouble with a brand new heat pump install on a house boat. It has a freon/water heat exchanger. Power consumption was high and the winter heat output was low. The factory rep was having a huge problem with the system and thought it had a bad reversing valve.

      I asked to look at it. The "Pro" tried charging the system using gauge pressure forgetting the fact the water heat exchanger was much more effective, so when he had the pressure up to what he expected for an air exchanger, the system was massively overcharged. This flooded the high side coil so very little of it was used for heat transfer.

        I asked permission to adjust the charge before they wrote off the reversing valve and it fixed most of the issue. I told them due to the water heat exchanger resulting in lower pressure, a larger expansion valve orifice could be used to bring system capacity back to normal. An expansion valve about 25% larger (3 ton system now has a 4 ton expansion valve) was installed. This allowed the same volume of freon to be delivered with the lower pressure. The efficiency increased and cut the power consumption with a low run duty cycle.

      Sometimes a tech that understands the theory can do a better job than the "Pro" engineer that doesn't have a solid grasp of the theory.

      Coding is the same. Some people have a grasp of the code language but don't have a good grasp anticipating bugs in the code leaving it open for exploits and glitches.

      A good coder can see potential pitfalls and can program around them reducing faults.

      --
      The truth shall set you free!
  30. Ridiculous Assumption by Nethemas+the+Great · · Score: 0, Flamebait

    It is a ridiculous assumption to believe that the intellectual capacity of an "average" person is sufficient to write software let alone quality software. It is even more ridiculous to believe that you can rewire the "average" human mind inside of a year to be able to think in the logic and manner necessary to express and solve problems through source code. Normal people's brains just don't work that way and is just as unnatural and foreign if not more so than placing a modern day smart phone in the hands of your 90 year old grandma. It is something that takes years of basement dwelling to cultivate.

    --
    Two of my imaginary friends reproduced once ... with negative results.
    1. Re:Ridiculous Assumption by Anonymous Coward · · Score: 0

      And based on the social skills you have evinced in your post, you clearly have spent most of your life in a basement.

    2. Re:Ridiculous Assumption by AK+Marc · · Score: 1

      You are right, but also an ass. The "average" person is incapable of most tasks. Driving a car safely is beyond the capacity of most people, and beyond the patience of the rest. Being an effective lawyer is beyond most people, as you must follow inane arbitrary rules while advocating the innocence of a person who confessed to you they are guilty. "Cooking" (in the sense of combining food into some better food) is beyond most people as well. They can follow a simple recipe, but anything finer than that (following a recipe for ganash or something complex that takes assembly skill, rather than just following), and they will end up with something inedible, and completely unable to improvise (substituting self-rising flour for flour+baking powder when out of baking powder, but letting it sit to rise a little to make up for the difference, or oil/butter/lard substitutions, or icing sugar/sugar granules/caster sugar differences).

  31. Yes and No by erik.erikson · · Score: 1

    We all started somewhere and frankly, if this drives some people to better contribute to themselves and the world or even just find the niche in life they've always wanted to be in, we'll have seen an excellent consequence.

    A year of independent course work is unlikely to be enough to teach the automata theory/set theory/discrete mathematics/et cetera (ad infinitum) that is vital to developing a core understand of what one is interacting with in professional coding much less the various other "softer" disciplines required to know how to write code of a high level of quality. That said, even with many years of university, employment, and success behind me I am continuously learning, expanding, and refining myself. The risk, of course, is that low quality coders could result.

    To counter-balance again, I generally like working on the harder and more interesting problems and this means that team members who are intimidated by those and as a result are happier with their job when doing the work that I do mostly because it needs to get done can be a godsend to my own happiness at work. Developing a mentoring relationship with such individuals has additionally been really gratifying.

  32. At least they'll be sort-of trained by WRX+SKy · · Score: 1, Insightful

    In all honesty, it can't be much worse than the crap our India "consultants" crank out...

    1. Re:At least they'll be sort-of trained by gweihir · · Score: 1

      I.e. of negative worth, because not only have you to start over, you have to get rid of said "crap" before.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  33. What? by Anonymous Coward · · Score: 0

    Learn on me! When you're not strong!!! I'll be your coder!!! I'll help you data mine!

  34. I Support the Left.... by littlewink · · Score: 1

    "But I'm leanin', leanin' to the Right. "

    from the song "Politician" on the album by Cream Wheels of Fire

    Lyrics here

    Listen to it here

  35. That's all we need-Cowboys. by Anonymous Coward · · Score: 0

    Passion? Is that another word for I like to be a cowboy programmer but I don't want to deal with the "lousy and uninspiring" grunt work to maintain it?

  36. worked for me by Anonymous Coward · · Score: 1

    Bought some books, taught myself to touch type, took some advanced computer courses at college and about a year later I got a job as a software developer. Worked 80 hour weeks to keep the job and about three years later finally got really good at it. Sure I was smart, but success is 90% effort, people. I still find that systems are think, fail, retry, rethink, fail again, try again, good enough, refactor, keep trying ... success.

    1. Re:worked for me by JetScootr · · Score: 1

      success = failures + 1; // how to be good at any job.

      --
      Pavlov wouldn't be so famous if he'd used a can opener instead of a bell.
    2. Re:worked for me by rwven · · Score: 1

      You nailed it. Couldn't have said it better myself. In order to be a good programmer, you have to work hard. Very hard. And you really have to love what you do. You have to immerse yourself in the subject with vim and vigor. You have to look at the code from six months ago, or a year ago, and be completely embarrassed that YOU wrote that...as a testament to your growth.

  37. Don't learn to spell, get a job at Slashdot by Anonymous Coward · · Score: 0

    This site is becoming increasingly worthless with each passing day.

    I don't know where you people who staff the place were educated, but you are
    some pathetic examples of "how not to do it".

    And your HTML coding SUCKS, too.

  38. You get no respect... by Anonymous Coward · · Score: 0

    In 2007 when I completed my Master's degree in Computer Science (I returned to get that degree after having been in the field for 20 years), I had a chat with one of my professors. He told me how not long prior to that time the computer science department saw a HUGE influx of students in the intro courses...and very few of them stayed. He said that through discussions with the students, they determined that the influx of students was caused by everyone suddenly wanting to write computer games. The sudden exodus was caused by everyone learning that it actually takes a lot of effort to learn what you need to know to write a decent game.

    People just don't really respect (which is different from understanding) what it takes to develop decent software.

    Many years ago, a company I had engaged in freelance work with for years asked me for a quote on a new product. They did not like my price (which was well below what it was going to cost me). One of the senior management team made sure I got the message that he had a sixth grader that could do the work instead of me. I politely responded that if their six grader could do the work with little to no pay, then they would be total fools not to take advantage of that. I didn't get the job, and four months later guess who called me back because their project had fallen apart? Oh, and guess who was no longer with the company?

    Anyway, software is a crazy field. Forgive me for bastardizing the scriptures, but it is a field where "many are called, but few are chosen"...

    1. Re:You get no respect... by rwven · · Score: 1

      Bingo.

  39. You guys are nuts by Anonymous Coward · · Score: 0

    You guys are nuts. 99% of programming is simple repetitive drudgery. It doesn't take a genius to to make an inventory system, an interactive web page, or any of the projects 99% of you work on. Be honest. You're gluing a few libraries and system calls together to do something that is probably not all that useful anyway.

    1. Re:You guys are nuts by scdeimos · · Score: 1

      Most people can't even do form-to-mail pages correctly so why would you trust them on anything more complex?

    2. Re:You guys are nuts by gweihir · · Score: 1

      You obviously have no clue what you are talking about.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  40. Meanwhile all girls who love animals are now vets. by Anonymous Coward · · Score: 0

    Meanwhile all girls who love animals are now vets.

  41. Silly Promises by turkeyfish · · Score: 1

    Bloomberg is trying to find an excuse for running for a third term. Any excuse no matter how silly or absurd is better than having people focused on the fact that under his leadership as Mayor the city doesn't actually have a program to train students to become programmers or find work in other professions that can then be guaranteed to given them a good shot at a decent job and thereby boost the city's economy.

    Any thinking person might wonder, however, how Bloomberg has the time to learn enough coding skills to help him appreciate what its going to take to actually develop city-wide plans to actually make it easier for coders to find jobs? If this can help in that, its surely worth his time. If nothing materializes in terms of a real jobs program, then this is little more than a publicity stunt. He got himself into this. It will be interesting to see him get himself out.

  42. Anybody can Make an App and a Million Dollars... by esten · · Score: 1

    ...with as much predictability as winning the lotto.

  43. Grab a scalpel learn to be a surgeon in 30 days by Anonymous Coward · · Score: 0

    Subject says it all

  44. Lean Coding by Anonymous Coward · · Score: 0

    Lean coding techniques just in time to program the Raspberry Pi. I like it.

  45. 21 by Anonymous Coward · · Score: 0

    days to learn C - that's how I did it. NOT!!!
    Look everybody, I bold'd some text with my skills!

    But to be fair, some of the code I've seen from India make me
    think this was their approach...

    1. Re:21 by gweihir · · Score: 1

      I second that. Best find so war was a quadratic sorting algorithm to remove dupes from an arbitrary long list in a time-critical application. In Java. That has hash-tables. I spotted this while looking at data-paths for a security review, the double-loop did just look wrong there.

      Offshoring is often just an expensive way to kill a project.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  46. Re:Smells like a load by JWSmythe · · Score: 1

        At least the title and summary are. Two misspellings that could have easily been copy & pasted correctly.

        As the summary says, he's "trying to not be elitist". Well, I'd be willing to bet some of these newbie coders with a year of education can at least spell, when they're hoping to get an audience of hundreds of thousands. It's a good thing he submitted it AC.

    --
    Serious? Seriousness is well above my pay grade.
  47. Does knowning math make you a mathematician by WarJolt · · Score: 1

    I took all the math for a B.S. in Computer Science. I don't consider myself a mathematician.

    The funny thing is that I used to work with a mathematician who thought he was a programmer. It was quite frustrating.

    It takes years for someone to develop the essential skills to work on software development.

    The fact is you can call yourself whatever you want, but I doubt anyone will hire you as a software developer after a year.

    1. Re:Does knowning math make you a mathematician by ThorGod · · Score: 1

      I took all the math for a B.S. in Computer Science. I don't consider myself a mathematician.

      It takes years for someone to develop the essential skills to work on software development.

      I'm glad you admitted that. I've met too many majors in college who didn't *get* that a minor is miles from a major in math.

      I think CS suffers from it's own success. General computing power has become so cheap and effective that 'everyone wants a piece'. It's the invention of the assembly line all over again. Steve Jobs and Bill Gates are this generation's Henry Ford (with license). Many, early-on, wanted to work on Ford's plants and I think we're seeing the same thing with CS. The odd thing is that I could swear we went through this back in the dot com era.

      (Okay, that makes it almost too erie, considering there was a smaller depression that preceded the Great Depression...but just.)

      --
      PS: I don't reply to ACs.
    2. Re:Does knowning math make you a mathematician by Hognoxious · · Score: 1

      that makes it almost too erie

      Huron the right lines, if that makes you feel Superior.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  48. You too can learn to draw... by Anonymous Coward · · Score: 0

    "...I did not expect American adults to take the two or three weeks required to get their heads around programming, much less the months of effort they'd need to become proficient. But I wanted people to at least become aware..."

    So, we just wanted to increase the awareness of what coding is? Oh, that seems like a warm fuzzy...

    But let's see, TWO or THREE weeks? Really? That's interesting. A couple of months to become proficient? Even more. Sounds like a fast track to employment! This will be a great change of pace from that 2 week "learn to draw" course I took via mail a while back. They told me when I mailed my sample in that it was beautiful.

    "All Codecademy needs to do to make bank is connect those of us who complete its courses and are looking for work with the companies paying good money to find us."

    "It took a few centuries after the invention of text for regular people to learn how to read and write. The printing press, which democratized print by reducing the cost of manuscripts, certainly helped."

    Democratization is AWESOME. Who doesn't like it? I mean it worked for the steel worker, auto factory worker, call centers and all, right?

    What do those doctors and lawyers know? Especially the lawyers, they seem to be involved in everything, right? Can't do anything without consulting them first. And all the fancy titles, who needs those?

    "Firms' other strategy, of course, is to import Chinese and Indian programmers, through a costly and often only temporary visa. (That's because, unlike those countries, we don't teach programming to students in the United States.)"

    No, in the typical American fashion, we stand up websites that half-ass teaches people in couple of weeks. Then pretend to certify them so that HR can half-ass do their job. And lower the overall employment cost so that managers can do a half-assed cost / benefit analysis.

    I can't limbo anymore because this fucker set the bar too low.

    -----
    Sit and watch your profession trying to be devalued.

    It's a slap in the face: to your profession, to the hard work you've put in building a career, to anyone who cares about the industry, who cares about technology, to anyone who has a basic grasp of economics, to anyone who thinks intelligence, creativity are things you cant rubber-stamp.

    You want to do society and the industry a favor, Rushkoff?
    Teach.
    No, really teach.
    Go to a high school and teach a basic programming course.
    If you can't do that, donate.
    Either that or do us a favor and shut up.

  49. Coming to Late-Nite TV! by rueger · · Score: 1

    This just HAS to become an infomercial! Who needs to buy distressed real estate for no money down when you can just become a coder in a few short weeks!

  50. don't look down on this by Anonymous Coward · · Score: 0

    I know for a fact that many fortune 500 companies are literally pulling them off the street in India to work for $60-70k US here in the US. I honestly see it all the time. I couldn't have ever imagined that this profession would be what it is today, or I would have gone into something more reputable. Much of corporate world wants cheap, get it done coding, and don't give a rats ass if you know what you are doing. America needs to wise up and realize this. Create some institutions like IIT and market them like they are world elite places to learn, so that the big corps will hire them up like they are a precious commodity. It doesn't take much, believe me.

  51. Elitism by omarius · · Score: 5, Insightful

    The above is NOT flamebait, o moderators. I meant it. I've been listening to, and reading, "blah, blah, stupid users never learn anything" since the 90's, and I think these criticisms are disingenuous as hell. Along comes an easy, fun set of lessons on the rudiments of programming, and people are deriding it for: too much media attention, too simple, too popular, et cetera. If your stance is, "I like being a computer geek because it allows me to look down on others," then that's your sad bag, but at least be honest about it. Only good can come from average people coming to realize that this stuff isn't some magic inborn to the 7th son of a rocket scientist; it just takes curiosity and persistence. I am calling bullshit on your defensive insecurity, and I have the Slashdot karma to burn doing it, tyvm.

    1. Re:Elitism by The+End+Of+Days · · Score: 0

      Talk about your quixotic quests.

      You could make a better use of your time trying to get these people to shower.

    2. Re:Elitism by antifoidulus · · Score: 5, Insightful

      You seriously think that CodeAcademy is something even remotely unique? Here's a clue, it's not. These "teach yourself programming" things have been around for decades, and there is absolutely NOTHING unique about CodeAcademy save for it's buzz marketing campaign. Thats why people look down on it.

    3. Re:Elitism by AK+Marc · · Score: 2

      It is flamebait, and it is in this context) wrong. People sell "learn to code" as "learn to program" and they aren't the same thing. A programmer is a "software engineer" who designs software that gets the desired result in the minimum footprint possible while also addressing security, extensibility, and portability (not just literal porting, but with the knowledge that any well used program will be run on some other platform at some point). Instead, we have people who learn a string of commands that will make some computer do something and then apply to every "software designer" job posting. That's not elitism, that's reality, and it deserves ridicule.

    4. Re:Elitism by Matheus · · Score: 4, Insightful

      Mod Parent Up Please.

      Really, I'm currently in the position of needing to hire a couple-few good solid developers and am having a hard time finding applicants let alone qualified ones so the concept of increasing the developer pool sounds attractive... Except! 1) As you say these dealios have been around forever and they generally do NOT produce good developers. 2) Did everyone just forget about the tech bubble days?! Everyone and their freaking grandma tried to get into "computer stuff" clogging the market with many thousands of completely crap devs making it hard for those of us who actually knew the trade to rise above the mire until companies finally started to get a clue. 3) I'm currently dealing with a small handful of College trained, experienced developers who can't seem to code their way out of a wet paper bag which does not make me excited about the possibility of hiring someone who's programming knowledge is based on an online Java Script Tutorial.

      I will qualify my statements: We live in different days than we did 10 years ago. The sea change that has occurred means that people of all ages are now, generally, more "aware" of computers. They get along with them and are less likely to find their inner workings completely alien so maybe some more cream may come out of a better primordial goo. That and the article, if you actually read through it, specifically says they don't expect everyone to learn to program... just to better understand what they now work with on a day-to-day basis... in between lines telling them they'll be able to learn to code in 3 weeks and below a title saying "learn to code, get a job". I'll give very partial credit there.

    5. Re:Elitism by Zmobie · · Score: 5, Insightful

      Personally it has nothing to do with me being able to 'look down on others' and has everything to do with this shit giving people a false impression of what it takes to actually become a software engineer. This shit attempts to trivialize the discipline in description. I am not looking to run around and say I am better than everyone, but I damn sure don't want people saying that what I do is something any moron can pick up in a year.

      Not only that, this shit is just attempting to exploit the HUGE buzz around the need for more engineers (especially software engineers), the high pay statistics associated with the discipline, and the fact that people think the job market is in absolute shambles (it isn't near as bad as the general perception, with the way people talk you would think half the country is unemployed). I don't really approve of people being taken advantage of in such a manner, though I know some would argue if they fall for it they deserve. I disagree that anyone would deserve that precisely because of how little understanding the general populace has of what a software engineer does.

    6. Re:Elitism by SomePgmr · · Score: 2

      Yeah, the "teach yourself programming" things have been around. The problem is they've almost always been html versions of a horrible fucking textbook. And as anyone that learned to code outside academia will likely argue... learning out of a textbook isn't necessarily the best way anyways.

      CodeAcademy is a good attempt. Rails for Zombies and similar are better. I can't think of any reason I should have a problem with there being good, usable material at all levels.

    7. Re:Elitism by Anonymous Coward · · Score: 2, Insightful

      You're right--It's not unique in the traditional sense of teaching yourself to program, but that's not the only area in which it should be judged. That's like saying Reddit is redundant because Digg exists. The site is actually pretty good. The lessons are meaningful, the site is put together well. As it continues to grow and new lessons are added, I have no doubt in my mind that it will be an even more powerful resource to those wanting to learn.

    8. Re:Elitism by Teancum · · Score: 4, Interesting

      While I like what Code Academy is doing, I do not like their terms of service ("we own everything you do, including the software you write in these lessons and can exploit this mercilessly at our discretion without even giving you attribution. If you design a lesson for us, we own it and you automatically give us copyright and intellectual property rights without renumeration or even acknowledgement.") They also plan on charging visitors to their site eventually, so expect a "bait and switch" if you get into it.

      On top of that, what they have is useful for about the equivalent of the first week or so in an introductory computer science class. It is useful to get started and to "wet your feet", but by the time you are through all you can do is roughly the equivalent of writing a "Hello World" in Javascript.

      It looks like they are planning on taking it much further, so I do reserve judgement on the rest of what they are going to do, and apparently they have several series of lessons in the wings that they are planning on releasing about one each week through the rest of the year, at least if I can read between the lines. It could be useful though.

    9. Re:Elitism by DigiShaman · · Score: 1

      Granted. So for the average Slashdotter that has zero experience coding except for the occasional batch file editing and understanding the most basic of basic HTML tags, what website would you recommend learning to code from?

      --
      Life is not for the lazy.
    10. Re:Elitism by Oligonicella · · Score: 1

      I disagree and don't believe it's flamebait. There's no single definition of 'programmer'. What you listed actually goes well beyond programming, into analysis and design. I didn't contract myself out as a programmer, I contracted out as an analyst and with good monetary reason.

      I don't recall seeing listings for 'coders', so since the entry position is called programmer, you pretty much have to equate the title to the bottom level work and then add qualifiers as you prove you can do more.

      Do I think this is bleeding edge? No. It's being promoted to people in a way that lets them know that kind of knowledge is available though. That's somewhat new.

      As for dumbasses applying for jobs they can't do, I've seen a shitload of CS holders who couldn't make a machine work either, so that's a push. It's not like businesses requiring competent staff are going to give this kind of course any credence.

    11. Re:Elitism by Anonymous Coward · · Score: 0

      Hey look, some non-asshole who actually knows what he's talking about. God forbid someone create a fun little site how people who actually got laid once or twice can have a little fun and learn a little bit about programming. Don't worry gentlemen, your jobs will still be waiting for you in the office, and so will the blow up doll at home. Inb4 AC knows nothing..

    12. Re:Elitism by Anonymous Coward · · Score: 0

      FTA:

      No, I did not expect American adults to take the two or three weeks required to get their heads around programming

      This is mis-information, on a grand scale. It's not elitism, I've been coding for 15 years .. I'm better than anyone this program will turn out. I don't want my job opportunities killed off, working conditions stifled and pay reduced just because there's more programmers around. I want to do less work for more pay and be picky about the jobs I take.

    13. Re:Elitism by Anonymous Coward · · Score: 1

      There are lots of people for whom the traditional "teach yourself" tools have not worked, because they're not presented in the right format. Sure, maybe you and I can learn programming by poking at memory addresses in the dim glow of a crappy CRT, and eventually looking at a few reference books for the details once we basically knew what was going on. That was the way to do it, because we knew there was a job to be done, and damn if we weren't going to find out how.

      But not everyone can do that. My wife, for example, wants to learn to program. But she's not going to do her programming by firelight with charcoal on the back of an iShovel like Abraham Lincoln, so she needs it presented in a way that's convenient for her learning style and willpower for the subject. She's tried Scratch, Open Courseware, and some game frameworks like Alice, Game Salad, and Stencyl. Each one gets her a little bit of knowledge, but they're all pretty daunting when you come at it from almost zero, or if you haven't spent your life thinking like an engineer.

      Code Academy is a new interface, specifically one with really good hand-holding, based on what I've seen from the first two lessons. So yeah, I think that's unique enough to give a shit about.

    14. Re:Elitism by Anonymous Coward · · Score: 0

      designer != programmer != engineer

      These aren't interchangeable terms that you just throw around.

    15. Re:Elitism by DocHoncho · · Score: 2

      This is pretty much exactly what I was going to say, but I wasn't about to do it so politely. Who hasn't had that boss who thinks that because he once worked as a trainer in a group that did Java work and puzzled out god awful VBScript and perl scripts while creating an abomination of a MySQL database where everything is a string, but we can't change anything because hey, it works (for some values of "work").

      In other words, until you've supported (and god help you had to modify) the hoary abominations cultivated by these "self-trained" deciples of the Elder Gods, you really haven't any cause think that the bitterness directed at these "teach yerself to code" websites as anything more than the the resigned realization that now there are even more imbeciles devoted to ruining your life that it is.

      TL;DR: If you're to goddamned stupid to come to the realization that your abortion of a VBScript ASP classic "website" is slow because your're executing a query in a tight loop based on an ID you retrieved from a previous query that you could have trivially retrieved all at once in a single query then maybe, just maybe, you're too goddamned stupid to be programming. Furthermore, when you refuse to acknowledge that that very same website does absolutely no validation on input and it's breaking the bloody fucking things you wanted ME to develop because "it works", but if I forget to validate some obscure edge case you jump down my throat... then maybe you're just a douche bag as well.

      P.S. Sorry, got a little ranty there... wish I'd submitted some of that shit to The Daily WTF.

      --
      Celebrity worship is a poor substitute for Deity worship and costs more to boot.
    16. Re:Elitism by AK+Marc · · Score: 1

      They are used interchangably in the marketplace.

    17. Re:Elitism by Rasterfarian · · Score: 1

      I had the real pleasure recently of getting paid to attend a conference titled Women in Games and New Media. Mixed crowd: game studio people, educators, makers. artists of different kinds, even government people. Good times. My takeaway, relative to the context here, is that programming (my occupation for twenty years and interest since childhood) has a nascent potential in our culture to become an applicable skill far outside the sphere of commercial application development. The Arduino, for example, is motivating a lot of people whose ultimate interests are physical to learn "enough" to accomplish real things on small scales. I say hoorah! Programming is a humbling and brutally honest discipline. The more people get a taste of it the better off our world will be, I say.

    18. Re:Elitism by cheaphomemadeacid · · Score: 0

      Well, gotta start somewhere? ;P Personally i actually started with sams teach yourself c++ in 21 days... in 97

    19. Re:Elitism by mhelander · · Score: 1

      If by "people look down on it" you are suggesting veteran programmers look down on beginner courses because beginner courses have been around for ages, I would care to disagree. I am fairly sure many veteran programmers indeed began their careers with just such beginner courses, way back when, which corroborates your assertion that such courses have been around for ages but gives no insight into why anyone would look down on such courses...which leads me to guess that maybe you mean that it is the _hype_ that is being looked down on? In that case, sure, hype can look a bit laughable to a veteran who has perhaps seen the object in question being hyped several times before. On the other hand, perhaps for a few veteran coders it was some hype that once helped them to find their way to a beginner course that set them on their path to become veterans. So even the hype can have a purpose and should not be looked down on, in my opinion.

      But perhaps you didn't at all mean "veteran programmers" by "people" ? On the other hand, I don't see how junior programmers would have enough experience to look down on the material they are still learning from, and the general public (assuming they know even less about programming than the junior programmer) would consequently have even less experience to draw on when looking down on the material.

      So perhaps you meant "intermediary programmers"? In that case I must agree I have sometimes seen tendencies of some intermediary programmers who are overly eager to distinguish themselves from junior programmers to look down on material suited for the juniors, but it is an approach that rarely lasts for very long, and I would frankly advice against such advocacy as a way to establish one's experience as a coder as it is fairly transparent.

    20. Re:Elitism by Demonoid-Penguin · · Score: 1

      You seriously think that CodeAcademy is something even remotely unique? Here's a clue, it's not. These "teach yourself programming" things have been around for decades, and there is absolutely NOTHING unique about CodeAcademy save for it's buzz marketing campaign. Thats why people look down on it.

      Agreed.
      Computer Power => bankrupted and deregistered => arises from the ashes as Computer Training Institute, rinse and repeat => Spherion. Cue the ads of the guy with the BMW. And yes they actually get jobs just *as* (*not* like) the ads promise - unfortunately some are in the industry writing code rather than data entry for Sperion's sister company.

      If it sounds too good to be true - it generally is.

      There are people who can become proficient coders in a language inside 12 months. They're generally building on existing computer knowledge and are literate and numerate. Those sorts of people probably won't be well served by that sort of course (they tend to quit) because they can learn more, faster, from books and by pulling apart other people's code. Those sort of people are few and far between - they can also do a lot of other jobs. Most people take 3 -4 years to become proficient in a single language. There's a yawning gap between capable and proficient.

      The majority of people who describe themselves as "programmers" are not proficient, and probably never will be - they can't read or spell, or do basic math. They cut and paste code when not watching "training" videos on Youtube and "webinars". Like "web designeers" that can't write lucid CSS the industry today tends to attract the classic "geek" - the sort our grandparents paid a nickel to see in a cage. Except instead of a pointy head or fish feet they've got Asberger's Syndrome and extreme laziness (they call it dyslexia). Encouraging those sort of people to give up a career in fast food or car detailing just robs their parents of the little money they have, creates more crap software, and pushes down wages for many of the good programmers. Not good for business in general.

      For every Keith Packard and Theo Tso there's a thousand idiots with a greater knowledge of Star Wars quotes than programming. CodeAcademy can probably teach a dog to code, and maybe even Bloomberg, but being able to write "Hello Whirled" in Javascript is not much of an achievement on it's own, especially when a useful Javascript coder needs to know at least HTML, and CSS, and be able to work with different frameworks - or even without a framework. Maybe even the ability to write up a report, research and study independently, communicate with others, understand technical specifications, debug other peoples work etc. And a day to write a jquery for a website that the client is paying $1000 for? It's not possible to teach people all that in a year.
      Next applicant please.

    21. Re:Elitism by mhelander · · Score: 2

      But what if it leads to few of the College trained developers you hire being able to code their way out of a wet paper bag precisely because before they enrolled they had already been coding as a hobby for years, an interest that was initially sparked by an online javascript course?

    22. Re:Elitism by pitzG · · Score: 1

      Why can top quartile graduates of top quartile schools send out hundreds of resumes and get almost zero responses? Why are the resume queues of average paying companies like Google chock-full of resumes, >1000 for each position they actually hire, if there's no glut? I think a big part of the problem is that most firms essentially have HR screening resumes, and they do an awful job of such. A few resumes, usually the wrong resumes, are passed onto actual hiring teams. As for 'high pay statistics', I would beg to disagree. Most new grads in software are darn lucky if they even get a $75k/year offer in the Silicon Valley, without a pension, or much in terms of permanancy or benefits. Meanwhile San Jose City Police officers start at $72k/year, and have their internships paid for at ~$30/hour. Figure that out, CS grads who invested a ton into their own education, barely have earnings equal to that of a police officer. And as they progress in their careers, the policemen enjoy almost iron-clad job security and big raises (ie: most San Jose cops are in the $180k/year range), while the techies seem to have to find new employers every few years, can be fired on-the-spot for practically any reason, don't receive a huge pension upon their retirement, etc. Not to pick on police officers, but saying that techies are high paid is a big joke, especially in a place where decent, livable, middle-class houses start at $500k and go up from there.

    23. Re:Elitism by Demonoid-Penguin · · Score: 2

      Really, I'm currently in the position of needing to hire a couple-few good solid developers and am having a hard time finding applicants

      We found Open Source projects are the best way to find, and assess, good programmers. If people are talented, and dedicated, they produce. We advertise positions through the local Linux Users Group - if the applicants have contributed to Open Source projects it's easy to check their ability and character. As it's rare to find people with experience in exactly what we want done - it's preferable to hunt for people with a demonstrated ability to learn what's required. Resumes don't cover that the way a mailing list, irc and git logs do.

      Two of our best staff have no tertiary education (or programming school) - one of them is a retired secondary school teacher (language teacher).

    24. Re:Elitism by mhelander · · Score: 5, Informative

      If I started coding today I think I would go about it roughly thusly:

      1) google "Game coding tutorial HTML5" or similar,
      2) Find the code listings, run them, modify them a little to see what happens but eventually be annoyed that I don't really know what the magic incantations in javascript etc mean
      3) Google "javascript introduction" and spend some time just writing "Hello world" apps and such, trying to learn basic javascript, until I got bored with that.
      4) Return to the game code, be absolutely gratified by discovering I indeed understand a little more of the magic incantations, do a bit more targeted modifications of the code to see if I can actually predict the outcomes at all....until I got bored with what I could do with my current level of understanding and return to the course in basic javascript to learn more (repeat from 3, basically). At some point you may know so much general javascript that you can continue learning more about javascript itself by looking directly at the game code and realize how it must work.

      As long as you find some little "loop" like that where you actually have fun all the time while learning, chances are good you will end up knowing quite a lot about how to program.

    25. Re:Elitism by pitzG · · Score: 1

      So you've basically closed the door to all of the talent that has been working on coding for proprietary systems over the years. Sure, that probably works for you with the glut of programmers out there, but its a lousy way of runnning a business, and certainly you're closing the door on a vast array of people who may have done what you want done, but didn't happen to have been doing it in the F/OSS world.

    26. Re:Elitism by Anonymous Coward · · Score: 0

      The majority of people who describe themselves as "programmers" are not proficient, and probably never will be - they can't read or spell, [...] Asberger's [...] being able to write "Hello Whirled" in Javascript is not much of an achievement on it's own

      Muphry's law.

    27. Re:Elitism by Hognoxious · · Score: 1

      No they aren't. In some countries it would be illegal - "engineer" has quite strict requirements.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    28. Re:Elitism by Anonymous Coward · · Score: 0

      That may be why *you* look down on it, but Omar is damn right about geeks, and especially Slashdot geeks. In fact your "here's a clue" comment, which is one of the most annoying elitist twat phrases ever to have been invented, proves that you're just as guilty as most everyone else here. You can't even disagree with a co-geek's point without making some kind of "you don't even have a clue" snipe. Wanker.

    29. Re:Elitism by Demonoid-Penguin · · Score: 2

      So you've basically closed the door to all of the talent that has been working on coding for proprietary systems over the years. Sure, that probably works for you with the glut of programmers out there, but its a lousy way of runnning a business, and certainly you're closing the door on a vast array of people who may have done what you want done, but didn't happen to have been doing it in the F/OSS world.

      Show me where I said I don't hire people from closed source backgrounds.

      I don't hire people who's ability I can't check. I also don't hire people who can't spell - saves paying others to debug their code. Interpret that as you will.

    30. Re:Elitism by thetoadwarrior · · Score: 1

      Teach yourself programming books can work if you really want to program. It's all about getting started and the continuing on with what you learned. No system will ever make you an awesome programmer. You have to actually do it. So if the books gives you the gist of it and you keep banging away on the keyboard then you will get better.

      Why, imo, CodeAcademy will fail is because I'm sure it won't teach you everything (testing, version control, etc), it will likely only give you the basics and it will probably attract people that don't really care about programming but just want a better job or a job. So they'll never move onto the next level. Those that do use it as a beginning to a serious attempt at coding probably will succeed but not straight after the course. They'll have more work on their hands after the fact.

      At best it's going to create a load of people that think my job is easy because they've learned how to print hello world 5 times in a row and how to display a date on a web page.

    31. Re:Elitism by JoeMerchant · · Score: 1

      3) I'm currently dealing with a small handful of College trained, experienced developers who can't seem to code their way out of a wet paper bag which does not make me excited about the possibility of hiring someone who's programming knowledge is based on an online Java Script Tutorial.

      This is nothing new. In the late 1980s I was a Teaching Assistant for a senior level Computer Engineering lab... each new batch of 30 about to be Baccalaureated Computer Engineers contained about 2 people I might consider worth hiring.

    32. Re:Elitism by rioki · · Score: 1

      The term Programmer unfortunately is not well defined. But as job descriptions go, I the want a Programmer, they probably want someone to spew out code based on some more or less defined design. If they want a Software Engineer, they expect that you can work form a blank slate. That is requirements, analysis, design, development, test and deployment. I have never found a job posting as "coder", so you can assume that programmer is probably the simplest software development job, except maybe intern...

    33. Re:Elitism by Darth+Snowshoe · · Score: 1

      Programming is the new literacy. I wrestle with this a lot now, with a couple small kids - I realize there's a window coming up, where their reading and writing skills will be sufficient, and the willingness to follow their dad on some dubious venture is still approximately the equivalent mass of their attention span, when they could be introduced to programming in a fun, safe context. Public school is not going to try to address programming until much much later for them, if at all.

      I think it's wrong to make promises about job eligibility based on a single course of anything. And surely there are other, better programs around, better places to start. But I think we all, as ambassadors and good citizens of what amounts to a foreign culture, be encouraging and supportive of people trying to take beginning steps towards understanding us and our medium.

      I like this line in the parent; "Only good can come from average people coming to realize that this stuff isn't some magic inborn to the 7th son of a rocket scientist; it just takes curiosity and persistence."

    34. Re:Elitism by Zmobie · · Score: 1

      That may be true in some of the other areas of the country, but in Texas not so much. I've seen lots of CS grads start working within a few months (some literally have a job before graduation) of getting their degree with 50k+ a year. 50k may not seem like a huge number, but because of the cost of living in Texas 50k is quite good (I would guess that it is at least comparable to the 75k in California). In fact, according to the last state statistics I looked at 50k is top 30% of income earners in the state.

      Some states have disproportionate gluts maybe, or a lot of companies that have no concept of what makes a good software engineer. Those things are different problems though, and definitely more isolated to regions (I still routinely get companies from Wisconsin, Florida, Oregon, Oklahoma, etc. trying to get me to move there to work for them).

    35. Re:Elitism by jedidiah · · Score: 1

      Exactly. This is a concept geared towards people that really have no interest in computer science as a means to convince them that they don't have to learn about a lot of the fundementals.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    36. Re:Elitism by Anonymous Coward · · Score: 0

      Been coding for 30 years (can't hardly believe it's been that long). And have worked with / for / supervised / taught many developers over that time, and the one thing that was paramount to success was the ability to think / structure logically. Languages / syntax / frameworks can be learned, classes can be taken, you can self-teach, but if a person is not able 'think logic' they would never be a good developer. If a person can't understand concepts like loops (do this until I say to stop) then I does not matter how many classes or what language they learn.

    37. Re:Elitism by tehcyder · · Score: 1

      This reminds me of the recent story about children here in the UK being encouraged to learn programming/how computers actually work. I have to say, it makes a lot more sense to start at school age, rather than relying on people to learn in their own time once they're adults and working or looking for work...

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    38. Re:Elitism by tehcyder · · Score: 1

      extreme laziness (they call it dyslexia).

      Btu I've got wrod bilndness yuo insensitive cold!

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    39. Re:Elitism by Teancum · · Score: 1

      I have been largely self-taught in terms of the art of computer programming, but I will acknowledge that it is an acquired skill that doesn't come easy and took considerable time to actually learn. I have also taken formal software engineering courses at a university (as well as the usual programming classes) in part because I acknowledge that there were gaps in my education along the way that needed to be filled in.

      I have had supervisors and even CEOs who dabbled a little bit with code, where they knew enough "to be dangerous". On the positive side, those in a supervisory position over software developers and working on the management side having real knowledge of how to develop software on even a simple level is usually better than somebody who is completely ignorant of computers... at least in terms of trying to explain why you might be behind schedule or how difficult it is to kill a bug. On the other hand, if they've never developed software more complex than a couple hundred lines of code, they have no clue how complex interactions between parts can be or how hard it is to try and fix the problems that a co-worker (or worse yet, a former co-worker) caused due to simply being sloppy and taking shortcuts in the development process that you now have to fix. Just as bad, trying to explain to those who know a little bit of software development that you can't jump right in and start coding on day one of a new project, or that any such software developed that first week is likely going to need to be thrown out afterward.

      The worst is a half-way decent prototype created by the boss that you are told to "fix" and make it into a workable product. If you are lucky, you get to scrap the whole thing and start over with a clean sheet, but I've had to "add functionality" to a rough prototype all the time working around the kludge that a boss developed previously and try not to bruise their ego so bad by throwing stuff out, acknowledging that they are the boss and can fire your ass if you cut too deeply.

    40. Re:Elitism by dunezone · · Score: 1

      On top of that, what they have is useful for about the equivalent of the first week or so in an introductory computer science class.

      Except its missing the "Why" part that any good programming teacher will discuss with you or a good book. Its one thing to show a For Loop, its another to explain why and when you would use a For Loop and what type of real scenario you would use it in. Without applying what you learn to some real scenario you wont really advance.

    41. Re:Elitism by Slashdot+Parent · · Score: 1

      It really depends on what you're looking for, where you're looking for it, and how much you're willing to pay, but yeah, good devs are hard to find. I know a lot of them, but they never seem to be unemployed for longer than about 5 minutes.

      --
      They don't grade fathers, but if your daughter's a stripper, you fucked up. --Chris Rock
    42. Re:Elitism by AK+Marc · · Score: 1

      In the US, "engineer" is a word "protected" by professional societies, but their attempts at going after MS for MCSE and such all failed completely. I know of nowhere that "engineer" has strict requirements. In the UK, electricians call themselves electrical engineers. Engineer isn't as protected as Americans think.

    43. Re:Elitism by Krater76 · · Score: 1
      I think my order of operations would've been more like this:

      1) google "Game coding tutorial HTML5" or similar,
      2) Find the code listings, run them, modify them a little to see what happens but eventually be annoyed that I don't really know what the magic incantations in javascript etc mean

      3) Go play Skyrim

      --
      "Is life so dear, or peace so sweet, as to be purchased at the price of chains and slavery?" - Patrick Henry
    44. Re:Elitism by Anonymous Coward · · Score: 0

      It's funny that you mentioned not hiring people who cannot spell and yet misspelled whose.

    45. Re:Elitism by Anonymous Coward · · Score: 0

      If you flood the market with new developers and the hiring people treat developers as identical replacable parts in the company, the hiring managers are not willing to offer as much in terms of pay and benefits. The experienced programmers have the options of 1) accepting less pay, 2) moving into management, 3) starting their own consulting business, or 4) moving into another career. Often, consulting for a higher pay rate looks more attractive than accepting less pay especially when the clients are using less experienced coders as it ensures more consulting work. Of course, this leads to companies clamoring for more H1B visas since they have trouble finding experienced programmers at the low pay rate.

    46. Re:Elitism by Anonymous Coward · · Score: 0

      Congratulations, you just summed up how I've learned to program over the last 6 or so years. Not to be big-headed but I can code circles around many of the people in my college-level classes. The "try something hard, try something easier, return to something hard, expand on easier" type process is the best way to learn IMHO.

    47. Re:Elitism by Anonymous Coward · · Score: 0

      In Canada you cannot legally call yourself an Engineer if you are not one. And they did go after MS for the MCSE and they won. If you want to call yourself a Software Engineer you need to get a SE degree, do your 4 years of EIT work under a P.Eng and then get licensed.

    48. Re:Elitism by Demonoid-Penguin · · Score: 1

      It's funny that you mentioned not hiring people who cannot spell and yet misspelled whose.

      Hilarious isn't it.

      Maybe you could put your innate nitpicking abilities to good use - open a delousing stand somewhere.

    49. Re:Elitism by Demonoid-Penguin · · Score: 1

      Been coding for 30 years (can't hardly believe it's been that long). And have worked with / for / supervised / taught many developers over that time, and the one thing that was paramount to success was the ability to think / structure logically. Languages / syntax / frameworks can be learned, classes can be taken, you can self-teach, but if a person is not able 'think logic' they would never be a good developer. If a person can't understand concepts like loops (do this until I say to stop) then I does not matter how many classes or what language they learn.

      Well put. Reminds me of a debate I overheard amongst some programming job applicants at a friends office. They were arguing over what "putting the cart before the horse meant". None of them were right.

      I mentioned it to my friend over lunch and he noted that all three applicants I'd overheard had no portfolios of code they'd written, and were rude and arrogant*1 - basically they'd expected to get hired solely on the basis of having graduated from university. None of the three had been employed in the years since graduating - and used that as a reason for not having a work portfolio. (There's a joke about circular logic there somewhere). The same university has turned out some of the best programmers I've come across - so it's not just down to the institution.

      *1When, individually, shown around where they'd be working if hired, they had all badmouthed the systems and hardware in use.
      They had probably seen it as showcasing their knowledge but had just come off as condescending and smug. Another failure to demonstrate logic - especially given the calibre of the programmers they'd have been working with.

    50. Re:Elitism by Teancum · · Score: 1

      Actually, I think Code Academy does a pretty good job of explaining the why part. Most of the lessons are getting your hands dirty and actually coding stuff rather than a dry textbook sort of explanation, where you are encouraged to experiment and do variations of the coding as you are developing the example software.

      What annoys me with the for loop in particular is that they really don't go over the syntax in a manner sufficient for beginners as it is a very complex structure. The "C" for loop (which Javascript also uses) is exceedingly complex for a beginning student. You can give a quick prototype to gloss over all of the things it does to simply get stuff to happen, but IMHO the depth of coverage currently in the lessons is far too shallow.

      BTW, this gets back to their licensing model, where they are not open to new content from people who really understand the concepts and assuming that one or two people are the font of all possible knowledge on the topic. There are many people would wouldn't mind contributing a better way to teach some of the concepts, but the site isn't equipped to accept those contributors.

    51. Re:Elitism by Seupsut · · Score: 1

      Speaking as someone who learned a bit of BASICA back in the day and has recently been itching to learn to code again I think this tool is fantastic. To all those who have been saying "the advertising and hype is just sad" I would adamantly disagree. We need to have a site or two like this hyped. Sorting out the crappy tutorials from the decent is frustrating for someone like me who doesn't know what they're looking at yet. I've been going through the lessons on this site since it posted here and I'm having a blast. Thank you for standing up for it and not being one of the mass elitists looking down their nose at entry level support...as though they themselves never had to start at the bottom of the learning curve.

    52. Re:Elitism by Anonymous Coward · · Score: 0

      It's a great way to learn a new language and quick recipes for doing stuff. It's a great way to learn to write legible and maintainable code by avoiding hard-to-understand stuff others did. However, it is a hard way to learn "coding" (programming). You have to pick up some programming fundamentals at some point, some high level architecture and other concepts that are baked in the code by the time you look at it and not readily apparent.

    53. Re:Elitism by rlp0903 · · Score: 1

      Train operators are called "Engineers".

    54. Re:Elitism by AK+Marc · · Score: 1

      By dictionary definitions, anyone who designs, operates, or repairs an engine is an engineer. By the original definition, everyone with a driver's license is an "engineer."

    55. Re:Elitism by AK+Marc · · Score: 1

      In Canada you cannot legally call yourself an Engineer if you are not one.

      There is nowhere where you can call yourself something you are not. It's fraud to call yourself something you aren't. The only question is, do you use the "common" definition (one who engineers things), the professional definition (one who has paid a professional society for use of the title) or do you use the "original" defintion (one who builds, operates, or maintains engines).

    56. Re:Elitism by codgur · · Score: 1

      The last sentence has it: "As long as you find some little "loop" like that where you actually have fun all the time while learning, chances are good you will end up knowing quite a lot about how to program." [...] where you actually have fun [...] That's the key. Have fun and the years will pass, you will want to keep learning to feed the fun. This social media revolution is not helping at all keeping those who are introverted interested enough to learn how to program and keep at it: they may just be coming out of their shell and getting social, leaving the coding by the wayside.

  52. Not so fast. by PeanutButterBreath · · Score: 1

    A major argument of the opinion piece is that having at least a rudimentary understanding of how computers and software actually work is increasingly important, and that learning some programming is a good way to accomplish that. I doubt anyone here would argue with that.

    I will argue with that. Learning to "code" is not likely to aid non-programmers in understanding how to participate in the process of creating good software. What is increasingly important with respect to computers and software is how to analyze, organize and communicate business logic and requirements.

    As a developer, I want clients to be able to clearly describe the problem they are trying to solve or the goal they are trying to achieve. I do not want them suggesting how I meet their requirements.

  53. I took 1.5 years of programming. by Anonymous Coward · · Score: 0

    I passed the classes and actually learned the concepts. The main thing I learned was that I was NOWHERE near even being qualified to work as a coder.

  54. Smells like $$$ for the more experienced ... by tomhudson · · Score: 3, Interesting
    The more Krap Koders out there, the more Ca$h fixing the Krap from Krap Koders.

    If in the meantime a half million bad ideas get killed off by Krappy Koders badly executing them, how is that a "Bad Thing"?

    Anything that hastens the day when we have real standards is a good thing.

    1. Re:Smells like $$$ for the more experienced ... by LostMyBeaver · · Score: 1, Interesting

      I would look at it more as "The more crap coders out there, the more cash there is in telling them what and how to code it". Let's be honest, even with new graduates from the university with computer science degrees, they lack the experience to put together a real program of any complexity. I am a 36 year old engineer that regularly mentors those guys and it takes some time to teach them how to think. They are full of energy, full of great ideas and they left school often with the latest and greatest in coding theory. The bad part is, often when you tell them "On this device you can't use exceptions because while the compiler itself support it, the operating system (or lack thereof) can't route the exceptions to the programs when they occur. I actually will often suggest hiring a great coder who has made an application for Linux and had a good coding style as opposed to a fresh out of school graduate. At least then you can see if they "Get it".

      If you get a bunch of new guys learning to code, then they can do things in the open source and gain experience. Then you can hire them. Without any student loans to pay, they'll be much less expensive. A masters grad who did something useful in the open source is worth $85k, without the open source is worth $70k, just the open source $55k, just and online course like this $40k. Notice I don't even mention the bachelors degree... this is because in computer science a bachelors degree is little more than a high school diploma with advanced math. Unless they do a really great open source project which shows how they can apply that math (like a well written codec), then I wouldn't treat them any differently than with no degree at all.

      Oh... the main reason a university degree REALLY matters is that it proves to guys like me that the guy who was in the university was forced to finish projects no matter how stupid, boring or mundane they were. I don't actually expect them to have any useful skills other than learning how to get the job done using the tools they were told to use.

    2. Re:Smells like $$$ for the more experienced ... by Hognoxious · · Score: 1

      The more Krap Koders out there, the more Ca$h fixing the Krap from Krap Koders.

      Seems like a variation on the broken window fallacy to me.

      If a company spends its entire IT budget on something that doesn't work, surely it has zero money to spend on fixing it?

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    3. Re:Smells like $$$ for the more experienced ... by tomhudson · · Score: 1

      The more Krap Koders out there, the more Ca$h fixing the Krap from Krap Koders.

      Seems like a variation on the broken window fallacy to me.

      If a company spends its entire IT budget on something that doesn't work, surely it has zero money to spend on fixing it?

      I think that's a great^WFANTASTIC alternative as well - let them DIAF for all you should care, if they're just going to hire the cheapest, most inexperienced workers around and hope that they can do the job? If they only want to pay 1/5th (or more often, 1/10th) of what something would realistically cost to develop, and they want to try to do it by hiring people who can't do it, who am I to stand in the way of them blowing out their budget and their brains? It's not like they're going to put any money in my pocket (or yours) anyway.

      You know how this story ends - they have unrealistic time constraints, a "slap it together and let the customers find all the bugs - even the ones we already know about" mentality, a continuous "crunch time", and poorly defined (and always changing) requirements.

      The continuous crunch time is because they set an unrealistic budget and they want it done before the $$$ runs out. Same as why they want to hire the cheapest. They don't want to spend the money it would take, but they still want the benefits, and they try to do it this way because they don't know what they're doing, and don't want to take advice that contradicts what they "need" to hear.

      Besides, in this business it's a truism you need the experience of two or three failures or you won't recognize the smell the next time it begins to stink (and it weeds out a lot of the wannabes) - so why not let them go broke - it's all part of culling the herd. :-)

    4. Re:Smells like $$$ for the more experienced ... by Anonymous Coward · · Score: 0

      Don't fool urself tomhudson. U're no experienced coder. Show us a time when u've been recognized as that much from a reputable source in the field of computing such as publications or trade show results and standings if not commercially sold code to ur credit (not some puny website any fool or 10 yr. old could make either).

  55. Why Bloomberg? by Anonymous Coward · · Score: 0

    If I had billions of dollars, I'd have a seriously hard time learning to code. I'd be too busy spending my billions of dollars on things that aren't tedious.

    FWIW: I'm a comp sci major.

  56. Oh, good. by Minwee · · Score: 4, Funny

    At least thedailywtf.com will have an inexhaustible supply of new material once all of these people get exciting jobs in the fast-paced software industry.

    1. Re:Oh, good. by artor3 · · Score: 4, Insightful

      They don't already?

    2. Re:Oh, good. by Anonymous Coward · · Score: 0

      It will be a larger infinity.

  57. Ridiculous promise, but still cool for newbies. by DreadfulGrape · · Score: 1

    Programming is a great discipline. It's not my main gig anymore, but I still write widgets and utilities to help with the various other crap I do. Good for CodeAcademy (or whatever the hell it's called). Javascript is as good a place to start as any.

    --
    sig has been sent away for a few small repairs...
  58. Narrow point of view by deacent · · Score: 1

    Saying that someone should learn to code because we live in a digital age and use all sorts of information technology everyday is like saying we should all learn to compose and perform music because we all listen to it. Don't get me wrong. I gladly encourage anyone who finds coding interesting to pursue it. But not everyone finds it interesting or even intuitable. And there are definitely some people who should never, ever write code for a living (I've encountered some of their handiwork).

  59. modded insightful... Re:In a year? by Anonymous Coward · · Score: 0

    I modded this insightful because 1) even a semi-realistic awareness of one's skill levels seems to be rare (and valuable; scott, I suspect you're actually better then you give yourself credit for because of that), and 2) Scott's observation about lack of entry-level programming work is crucial. The later is a serious long-term problem; when I look around, I see skilled old people (self included), or young outsourced & off-shored contractors. I don't have an answer for it; maybe software "ecosystems" have moved past the point of entry-level programming, at least commercially.
    (closing thought: Scott, I'll throw out the idea of trying to hire on as a business analyst and start w/requirements documentation for projects. That might be an optimal stepping stone for moving into a development team.)

  60. Real Programmers... by Anonymous Coward · · Score: 0

    Its funny that anyone could learn to program in a year... If that were the case, Universities would loose millions of dollars to self help, learn to program, books.

    When these so called "Programmers" can write the Java Compiler that I had to write in my final semester, then I might believe it.

    -Bachelors Degree in Computer Science, University of Texas, Austin.

    1. Re:Real Programmers... by pommiekiwifruit · · Score: 1

      "the elements of computing systems" will get you from logic gates to cpu design to assembler to writing a compiler in 300 easy pages.

    2. Re:Real Programmers... by Anonymous Coward · · Score: 0

      Please, go out and give TECS to a random sampling of people who've done the CodeAcademy exercises and see how many of them manage to complete it.

  61. Hey dont burst my bubble by JustNiz · · Score: 1

    I'm currently planning on becoming a brain surgeon in about 9 months from scratch with their innovative internet courseware.

    1. Re:Hey dont burst my bubble by shentino · · Score: 1

      Here's a hint.

      Medicine isn't the only thing you need to study.

      You also have to rub elbows with the same people whose market share you're going to be taking a bite out of.

  62. A year!!?!?!?!?! by JAlexoi · · Score: 1

    LOL!!! I literally woke up my neighbors laughing at the statemented that you can have SwDev in a year...

  63. Offshoring Revisited by Bob9113 · · Score: 1

    2002: "We should hire third worlders to do this stuff."

    2012: "We should get the unemployed to do this stuff."

    It's all good, go for it. Some of them will be able to do it, and do it well, and communicate about it with others, and not go stark raving mad. Most won't. The ones who do will be a boon to our field. The rest will learn that we are actually worth more than our current considerable compensation. Average people knowing more about programming, by trying to do it, means more people who grok that what we do is far out of the ordinary.

    Admittedly, there will be another five year period when lots of pretty hairstyles with empty suits under them will think we can be replaced easily -- this time by homeless people or something -- and those empty suits will crash and burn. Just learn to recognize them and get out of the fallout zone.

    1. Re:Offshoring Revisited by pitzG · · Score: 1

      The number of lives ruined by the offshoring/outsourcing/H-1B 'experiment' of American business certainly must be enormous. 2001, 2002, 2003, 2004, even 2005 were years that produced some of the highest quality CS graduates to ever come out of the universities, as the dot-com bubble in the late 1990s forced most schools to institute enrolment quotas for CS. Cut-off averages were routinely in the mid 80s. While, these days, and prior to the boom, even guys with 65% averages could be admitted to CS. If employers want to hire brilliant people, they would be well advised to look to the 2001-2005 cohort, who mostly sit underemployed/unemployed right now, of CS/EE/IT graduates. Most of them never given a chance by the job market, passed over in favour of cheap foreign guest workers.

  64. Oh good by NotSoHeavyD3 · · Score: 1

    (Sarcasm on) Oh great, yet more people coding that will probably do crazy shit. Like writing functions that are thousands of lines long, giving crappy name to variables and functions. Oh and refusing to use templates when they should in C++, not understanding pointers. Hell, they'll probably even do some playing around code trying to figure something out and put all that mess in the final app. Yeah, should be great. (Sarcasm off)

    --
    Did you know 80 to 90% of the moderators on slashdot wouldn't recognize a troll even if one dragged them under a bridge.
  65. Meh!!! by Anonymous Coward · · Score: 0

    Great way to teach, learn, play with algebra and calculus, etc... throw a little history in there for good measure. Maybe give them pointers where they can continue their interests.

    1. Re:Meh!!! by retchdog · · Score: 1

      i do hope that "pointers" was a pun.

      --
      "They were pure niggers." – Noam Chomsky
  66. Tutoring? by Improv · · Score: 1

    I am confident that there are many people I could tutor up to being able to program reasonably given a year. Doing this in a large classroom sounds really difficult, but I won't discount the possibility that someone managed to come up with enough of a condensed curriculum that they can do this for a fair number of people, at least enough that they can fill a number of low-to-mid-level programming jobs. They might not understand a lot of the theory, but the one thing we know about the future is that there will be a need for a lot of programmers at various skill levels.

    --
    For every problem, there is at least one solution that is simple, neat, and wrong.
  67. In my experience... by leoc · · Score: 4, Informative

    Programming is like driving a car, everyone thinks they are really good at it but everyone else sucks.

    --
    STFU about slashdot bias.
  68. this is a very good thing by Anonymous Coward · · Score: 0

    i think it is fantastic when people create situations for folks to get involved. often that is all that is needed to launch someone into a life long career. it could lead to a developer position, qa, it, customer support, who knows -- and what segment of the industry the person lands in -- and it is truly something to watch someone that has a real natural ability pick start from humble beginnings and do some great work. can it be done in 12 months. yep. i've trained two people in less than 12 months. one person was working in shipping/receiving and the other a pc tech and i trained them while working in a major unix os company, in the kernel/networking organization of all places. all it takes is persistence, the ability and desire to learn and an opportunity. thats it. and thats how i got them their interviews -- by focusing on those simple traits. one is a manager now and the other retired early. mentoring can be a very rewarding experience.

  69. Re:Smells like a load by slackware+3.6 · · Score: 1

    Coding is like construction it's almost all shit and rarely done to perfection for two main reasons . Cost and time. I'm sure most would like to do an awesome job but there are bills to pay and the guy that does the almost good job for a little less money usually gets the job.

  70. yes by Weezul · · Score: 2

    I agree, that's actually my point, which you're taking the piss out of.

    There is an awful lot of room for "not the best coder in the world" out there, javascript, access, whatever. And the more "not the best" we have doing useful stuff the more gets done, the less stupid stuff we good ones must do, and the more important interfaces offer basic coding friendly APIs for us to exploit.

    In fact, I'm certainly "not the best" myself. I'm actually a mathematician by training. I love Haskell, C++, and Perl, but basically I learn whatever I need for whatever I'm doing, and then move on. I've never actually won at codegolf, but I've contributed useful insights even there.

    --
    The Christian religion has been and still is the principal enemy of moral progress in the world. -- Bertrand Russell
  71. Such arrogance by Foxhoundz · · Score: 1

    Our resident subject matter experts once again have once again proven that Slashdot is infested with arrogant intellectuals.

  72. Just corporate propaganda by Anonymous Coward · · Score: 0

    Look at the actual job ads, they all want at least 5 years experience in each of a dozen different skills. And every employer has a different list. Many of the skills are not even computer related. I see lots of jobs looking a degree, and loads of experience, for $14 an hour and less. And why not? You can hire all the offshore developers you want for $4 a hour - just go to rentacoder, odesk, elance, etc. Go to dice, or indeed, message boards, ask about the real world of software development.

    Yes there are good salaries, but it's hardly the stupidly simple story that this article implies.

  73. Adapt or die by MrCrassic · · Score: 1

    Most people grow to hate programming because most teachers teach it badly. Perfect example: all engineers at my alma mater (Stevens) needed to go through a programming course with the idea that everyone would become a better engineer with a little bit of programmer in their system. That probably would be the case IF they didn't C++, arguably the most unfriendly language for beginners to learn. It's fine for Computer Engineering students like myself to take that because we will actually need those concepts later on. Does a Chemical Engineer who's bound for doing pure chemistry research really need to know what pointers are and how to use them? (This alone confused most of the people in the class.) Does anyone that isn't doing this for a living need to do this if they just want to write an Android app?

    If CodeAcademy can teach people the basics in ways that are actually interesting and worthwhile (Project Euler doesn't count...a lot of people hate math too), more people *will* learn how to code. Tons and tons of people of varying intelligence come up with great ideas every minute of the day but fail to execute because they not only don't know how to code, but are afraid of learning because "it looks hard." Google tried working around this with App Inventor, but that never really took off. This initiative probably won't make people Google-quality coders in a year, but it will spark the innovative light our country has been direly looking for lately.

    (You can definitely start making serious money as a programmer or IT guy with a year or two of education and a good connection. People admire doctors and lawyers for what they make, but I know guys who make just as much as they do or more with no degrees and WAY less stress...as contractors anyway. IT in general still pays really nice money, especially if you know where to look.)

    If anything, I'm hoping this will make those with the IT pursestrings up those budgets a little easier...

    1. Re:Adapt or die by rock_climbing_guy · · Score: 1

      I learned on C++ in my first year CompSci courses. What do you propose would be better and why?

      --
      Wh47 d1d j00 541, 31337 15n't t3h r0xor5 ne m0r3???
  74. Learn EVERYTHING in one year??? by Anonymous Coward · · Score: 0

    Ok so, they are going to teach bash scripting, version control, web server configuration, javascripting, CSS, HTML, XML, some backend scripting language, SQL, and database administration??? Because this is what it takes to be a developer these days.

    One language a developer does not make. Like Yoda must I speak.

  75. Good idea... by Anonymous Coward · · Score: 0

    ... if you just want to get a taste of what programming is like. If you want to become a *good* software developer - with your pick of job opportunities - be prepared to eat, live, and breath software development for the next ten years.

  76. Butbut by ericdano · · Score: 1

    But oh, if we pass the stimulus we will stay under 8% unemployment. Or if we pass this insane high speed rail to southern california that will fix everything.

    Learning to code? If you are interested in that. It would be smarter to get into health care services, or tax related things. Law is always safe too. Coding? There are so many people doing it, and it's a cut throat business.

    --
    It's either on the beat or off the beat, it's that easy.
    I moderate therefore I rule!
    --
  77. Teach Yourself Programming in Ten Years... by Anonymous Coward · · Score: 0

    http://norvig.com/21-days.html

    1. Re:Teach Yourself Programming in Ten Years... by gweihir · · Score: 1

      Always a good recommendation, very insightful. The comments about C++ and Java being unsuitable for beginners are also right on the point. I second the recommendation of Python, it allows you to ignore the Machine mostly and focus on learning to program. As a second language I would recommend C on Linux, to get to know the OS API and find out how to actually do all those things Python makes easy. After that you may (or may not) be ready for a monster like C++ or Java.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  78. WTF a year? by strangeattraction · · Score: 1

    Why on earth would it take a year to learn to code? This isn't like becoming a surgeon or politician. It might take a couple of months to really type well but come on. I train someone in a matter of weeks to do as well as a Stanford or Berkeley CS Grad. Bottom line people skills are what really matter in programming. There is one very import skill however. You really need to be able to answer a ridiculous question in a phone screen. That is a true test of a great programmer and any Google employee can tell you that.

  79. Politician in 1 year by Anonymous Coward · · Score: 0

    Good idea, I'm going to make a become a politician in 1 year course. You will be taught to be given a budget, spend triple that amount, prevent companies from opening businesses, and make sure your campaign contributors get all the tax money.

    You all need to learn how not to be elitist and just turn a ridiculous statement back on the person making it.

  80. Why IT is perfect for offshoring/inshoring by walterbyrd · · Score: 1

    I don't think I could invent any type of work that is more perfect for
    offshoring/inshoring than IT.

    1) Unlike manufacturing, you don't have to mess with physical inventory. This is
    huge. Shipping costs, and other supply chain costs, can be very substantial.
    With IT, everything is done over the internet. Perfect for offshoring.

    2) Unlike manufacturing, you don't have to worry about special plants, or
    special equipment, special environmental regulations, or worker safety issues.
    Just use ordinary computers, and ordinary office space. Dealing with foreign
    regulations for building permits, and the like can be a nightmare. With IT, you
    don't have to bother with any that. Just rent space in an existing building.
    Even if you build your own building, you don't have to bother with all the
    special issues that go with manufacturing.

    3) Unlike health care, or other fields, you don't have to bother with sort of
    special education, or licensing requirements. For example, we can import nurses
    from Mexico, they would not be qualified. Health care licensing is regulated by
    the state. Nothing like that to worry about with IT, legally, practically
    anybody can do practically anything.

    4) No unions to fuss with. Replace all the IT workers you want with visa
    workers, then send the entire department offshore. No need to worry about union
    pushback.

    5) No standardization in IT. You can always tell the government there is a
    shortage of qualified workers, since there is absolutely no definition of what
    is "qualified." You have a virtual carte blanche to make up any kind of
    statistics about salaries, or qualification. For example, you could look for
    workers with an arbitrary list of experience requirements, and when you don't
    find them, use that as an excuse to hire offshore workers with no experience,
    and just a liberal arts degree.

    6) US IT workers are not represented by any professional organization, and
    therefore have no voice in congress. Dump on IT workers all you want, what's to
    stop you?

    7) Due to massive corporate propaganda, it is widely believed there is a
    shortage of qualified US IT workers, so nobody will blame you for going
    offshore. There was significant public outcry in the 1980s when manufacturing
    was moved offshore. Michael Moore even created a movie, and Billy Joel wrote a
    song. Nobody cares about spoiled IT workers.

    8) You can point to contributions made by actual immigrants, and then prentend
    that H1Bs are actual immigrants. Great PR.

    9) You can place the race card. You can say that anybody critical of replacing
    US workers with offshore is a racist, bigoted, and xenophobic; and thereby,
    immediately quash any dissention.

    10) US IT workers are too spineless, selfish, arrogant, and disorganized, to put
    up any sort of meaningful resistance to your offshoring plans. Take your time,
    when you start importing visa workers, only the workers who are directly
    affected will care. The guy in the next cubical won't care until his head is on
    the chopping block. US IT workers have a special trick of sticking their noses
    in the air, and their heads in the sand. US IT workers will say: "they could
    never do without me. I'm much too valuable. Only the poorly qualified lose their
    jobs." Dumping on US IT workers is like shooting fish in a barrel.

    11) Significant saving. US IT workers can be quite expensive.

    12) Indentured servant status is even more important for IT workers, than other
    workers. Everybody's information system setup is different, so it takes a while
    for IT workers to learn their jobs. US workers can quit just after they get up
    to speed. Which means you are training people for their next job. Worse yet,
    they can take what they have learned (on your dime) to your competitors. With
    visa workers, they have to stay with you for six years, then you can send them
    to your offshore operations.

    12) Most IT workers don't work directly with

    1. Re:Why IT is perfect for offshoring/inshoring by pitzG · · Score: 1

      Exactly Walterbyrd. US tech schools were chock full of the best and brightest US citizens in the late 1990s and early 2000s, chasing the riches of the 'new economy'. When they graduated, circa 2001-onwards, they were met with an industry that mostly slammed the door in their faces and only hired foreign workers on the H-1B visa -- a few firms like Google excepted who mostly picked up tech industry castoffs from previous years. Tech employment in the USA has not expanded from 2000 levels, but over a million H-1B and Green Card recipients now are in the US IT workforce. Which means that over a million American citizens have been displaced, including most new grads from the past decade. What is the plan to integrate the past decade's worth of grads into the workforce? Is it any wonder why the economy is collapsing when a decades worth of some our brightest grads basically have been condemneed to a live of unemployment and poverty, because an industry that they gave some of their best years in college to study to become productive members of, decided to reject them in favour of cheap imported labour?

    2. Re:Why IT is perfect for offshoring/inshoring by Anonymous Coward · · Score: 0

      Lack of an organized structure in our ranks is our biggest failing as a group (union, etc.)

      There was a small truth that the original India transplants wanted to start a new life here in
      the U.S., but what I see now is technology stealing. They work here only for training and
      to take our ideas. This is not cynicism. What U.S. companies don't realize is that there is no
      remedy for them when this happens. How do you sue? How do you even know your technology
      has been taken? Are you going to go to India and look at POS or Warehouse systems to see if
      it's you code?

      I'll use the lame reasoning you hear so often with other matters - H1B kills U.S. innovation!

    3. Re:Why IT is perfect for offshoring/inshoring by pitzG · · Score: 1

      Exactly.... Someone once said something about a million monkeys on a million typewriters, and how the output certainly wasn't very likely to be of much use. Yet this is exactly what US businesses have attempted to replicate. A million Indian H-1B's on a million computers, taking a million jobs away from qualified US citizen engineers who proved themselves, in the 80s and 90s, to be superior at coding, developing and growing the economy, and innovation in general. Is it any wonder why we have a domestic tech industry these days on the verge of collapse?

  81. Starting Point by Anonymous Coward · · Score: 0

    All you people bashing this course aren't realizing this is an amazing way to introduce programming to a metric fuckload of people who may find programming interesting enough to continue their education. Gee, whiz.... isn't that how we all started, too? The fact that it's heavily advertised is GOOD for the industry, which can use the fresh faces.

    Unless you're not as good as you say you are, this is ZERO threat to your massive ego... ahem.... talents. Bemoaning this is as stupid as claiming free community CPR classes will lead to talent-less doctors.

  82. The Cathderal and the Bazaar by skyggen · · Score: 1

    6) Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging. 8) Given a large enough beta-tester and co-developer base, almost every problem will be characterised quickly and the fix obvious to someone.

  83. The last thing the world need is more bad coders by gweihir · · Score: 2

    Good code comes from insight, creativity and other specific talents. Learning a language and learning how to program (two very different things) only help if the basis consisting of the aforementioned qualities is there.

    Average people will just write atrocious code, that may or may not work and will be a maintenance nightmare. Typically, it is best to throw such code away, sack the person responsible and start over. At the same time, people are being lied to here by being told that they can become reasonable coders and are being lured in with the promise of job opportunities. I find that despicable.

    If this sounds elitist, well, it is just realistic. You cannot qualify average people to be reasonable doctors, mathematicians, engineers, poets, ... either. All of these require specific talents. If you don't have them you should definitely not go there, because you will do more harm than good.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  84. Welcome to 1999 by Kagato · · Score: 1

    Seriously, we went down this road already. Y2K, 1999. My lord the number of mediocre developers. And the H1B limits were substantially higher then too. It just compounded the problem.

  85. Ok....Coding for Everyone by hackus · · Score: 1

    Ok, well....I am going to speak whats on my mind here, because I can't say it to some peoples faces.

    Being the manipulative and deceptive bastard that I am. ;-)

    1) Coding for everyone, perhaps he means php? Ok, when LAMP comes to my, I think of shooting people. ;-)

    It isn't that php is the worst of all time languages, with its messy all over the place bloat code. I mean, Java was bloaty, but I love Java because all of the conventions for declarative syntax, which exhibit and enforce decades old engineering approaches that make good software.

    It is easy to debug, has facilities for objects etc....but can still use functional methods of programming.

    Php? Absolute nightmare to debug, on any platform. Declarative syntax style is, _anything_ and _everywhere_ is just O.K. It is so super easy to do declarative logic because _everyone_ can code. Nope. The only thing I see php good for is building content managers, does an OK job.

    2) Don't get me wrong, I think php is great for little projects, as it allows you to do some things up front you couldn't do otherwise fast and simply.

    But it _never_ stops there. All of a sudden you got php all over the place with people thinking it is some sort of language they can build reliable applications with it.

    Php creates a huge and disastrous hardware requirement as a general purpose application platform. I have seen small changes literally, just blow up websites overnight not because the code is right or wrong, its just because php has really nasty memory requirements for executing stuff you can declare anytime. A website that could support 1,000 people literally can support like 50.

    Who knows, depends on the php implementation on the given platform.

    3) PhP is like all over on the UW-Madison campus, and everywhere I go it is nothing but a giant mess. People complain all the time about bugs, or classes that bring the whole website down because 30 people executed a php script all at the same time.

    Invariably it is because amateurs are coding stuff, that don't want to learn threading, don't know how to think or use any kind of parallel assisted language like Java, because it takes too long and it is too hard or worse, they only want to pay $10 bucks an hour.

      So I am not for everyone coding.

    I am going to shutup now, before I get the urge to talk about Javascript and its crap. ;-)

    -Hack

    --
    Got Geometrodynamics? Awe, too hard to figure out? Too bad.
    1. Re:Ok....Coding for Everyone by ErikZ · · Score: 1

      I've got a niche website that I threw together using PHP about 10 years ago. I've been thinking about tossing it all out and starting over from scratch.

      I see what programming languages you *don't* recommend, what *do* your recommend?

      --
      Democrats or Republicans. They are both taking us to the same place and they are not afraid of us anymore.
  86. Translation by Anonymous Coward · · Score: 0

    "Any Monkey Can Write Software"

    Now for those of us that are aware that someone has already proven that Shakespeare can be written by monkey bots, perhaps this isn't as amazing. This is just the typical attitude that management takes when they are faced with something they don't understand. The reaction is prideful ignorance.

  87. learn to be a billionaire program better? by Dan667 · · Score: 1

    think about how much better it would be to learn to be a billionaire and then have all that money in less than a year. It is looking more and more like anyone can do it if bloomberg can.

  88. They might not get jobs, but... by lpfarris · · Score: 3, Interesting

    they might learn to think a bit more logically. And that would not be a bad thing.

  89. "buzz marketing campaign" by unity100 · · Score: 2

    maybe that is the 'unique' thing ? i have never heard a popularized attempt to teach coding to masses.

  90. It's not something you do, it's something you are by ModernGeek · · Score: 1

    All of these people who think that they can take a few classes here and there, read a book, and then get a job are completely hopeless. They think that creating software is something that is taught in some sort of class. Guess what, it isn't. It's more of a way of life. You don't become a coder, programmer, software engineer, or whatever it is you want to call it. You either are, or you aren't. Those who are normally discover their talent by poking around and finding others with the same drive to learn how things are made. It isn't really about the code, it's about finding out how things work, and how to do those things for yourself. There are so many posers in this field, it isn't even funny. The sad part is that most of these posers have letters after their names and useless pieces of papers given by Universities that like to pretend that they are the gatekeepers of knowledge.

    --
    Sig: I stole this sig.
  91. "CodeAdacemy's" != Code ACADEMY by Anonymous Coward · · Score: 0

    "CodeAdacemy's" != Code ACADEMY

    APK

    P.S.=> Article submission says this verbatim:

    An anonymous reader writes

    "CNN is running an opinion article that talks about Michael Bloomberg's taking part in CodeAdacemy's CodeYear program"

    CONFUSCIOUS SAY "One must learn to write English before one can learn to code", lol...

    ... apk

    1. Re:"CodeAdacemy's" != Code ACADEMY by j35ter · · Score: 0

      CONFUSCIOUS SAY "One must learn to write English before one can learn to code", lol...

      ... apk

      And a bunch of Indians in Bangalore sensed the disturbance in the Force, created by this comment, you insensitive clod!

      --
      Delta-Mike November Bravo Tango
  92. Re:Smells like a load by logjon · · Score: 0

    Did I miss something? Since when is ability to code not inversely related to ability to spell?

    --
    The stories and info posted here are artistic works of fiction and falsehood.
    Only fools would take it as fact.
  93. Why not? by FWMiller · · Score: 1

    We let taxi drivers buy half million dollar houses. We're all gonna get our power from solar and wind farms. Everybody's gonna be driving electric cars in a couple of years. Why shouldn't laymen be able to write computer code?

    --
    Frank W. Miller
  94. I think we're missing the big picture here. by Anonymous Coward · · Score: 0

    This CodeAcademy deal is an attempt at implementing the Monkeys-Typewriters-Shakespeare Theory but in programming.

  95. Top grads don't even get calls! by Anonymous Coward · · Score: 0

    My observation -- top grads can send out hundreds, sometimes thousands of resumes, detailling their projects, their experience, and their marks -- and not even receive responses from many of these firms who claim a 'shortage' of programmers and engineers. During the past decade or two, the engineering schools were chock-full of Americans studying computer science and engineering -- only to join a job market that was pretty much taken over by firms that only hired foreigners. Its nice to talk about the Googles and the Facebooks hiring, but they actually only consider fewer than 1% of resumes submitted (and Facebook has an auto-rejection script so its fairly overt that they're not even bothering to consider people unless they have certain magical keywords or networks in their FB profiles!).

    Many very good EE, CS, physics, IT graduates, US citizens, over the past decade, have seen their lives ruined because of this nonsense. I graduated in 2002, and most of my graduating class in CS/EE, from a top quartile university, is still underemployed or unemployed -- rarely even receiving interviews. If tech firms want good coders, all they need to do is to start hiring smart people, and then turn them loose.

  96. Hmm by lightknight · · Score: 1

    I, for one, welcome the competition.

    However, I will point out that while it may take only 3 months to put out a programmer, it takes several years to produce one worth hiring. To put it another way, it only take 3 months of chemistry to put out a Chemist, but it takes several years of working with chemistry to put out a Chemist worth hiring. Or an 'introduction to English' class to put out someone who speaks English. What you are looking for is someone who can handle the task fluently, which is an all-together different category.

    We all remember the confusion that the fly-by-night IT companies caused during the dotcom boom, in which people with no understanding of computers took 3 week courses, and believed that was all they needed to get a good job in IT. These actions had the nasty side-effect of sabotaging wages for other IT people, as an inferior product was mixed in with a superior product, forcing wages downwards. Since programming is a fair amount more difficult than building a computer / maintaining a network, I do not think a 'gold rush' will result from people trying to get into programming jobs. Why? Because the bar is that much higher, and it's fairly obvious to your future boss (who is a programmer) that you know nothing about programming after two questions. From a conspiracy standpoint, jobs for programmers have been flowing back into the United States, after business's recent attempt to outsource fell on its face; as programmers once again are in demand, the wages for them are expected to rise; hence, someone may be making a belated attempt to (put charitably) increase supply of programmers to the market (and possibly scam people in the process by blowing smoke up their asses about attaining a six or seven-figure job with minimal training), or more realistically, to attempt to mingle inferior products (programmers knowing only one language, with 3 months experience) with superior products (programmers knowing at least 3 languages, with several years experience), to lower the cost of superior products (drive programmer wages down into the ocean, right as businesses need to hire local programmers).

       

    --
    I am John Hurt.
  97. Great, more Calvinism, just what we need by Anonymous Coward · · Score: 1

    This is just another method of claiming that those who are not great successes and in their predicament due to personal failings. After all, the only thing that stands between the guy who can’t find a decent job, and a great job is the willingness to spend some time learning to code on the internet.

    Promoting this mindset does nothing but fuel those who claim that one’s position in life is entirely the result of choices. They then go on to claim that their privileged position is entirely a result of their own choices and actions’. This allows them to escape to calls to a moral duty to help provide the opportunities that they java enjoyed to others.

    Now they can feel good about asking for the schools, which they have enjoyed the product of, to now be underfunded. After all, they can claim, you no longer need those expensive schools, you can learn to code on the internet.

  98. Story time by fyngyrz · · Score: 5, Insightful

    I'm a martial arts instructor. Inevitably, a time comes when certain types of people ask me to teach them some "quick self defense." What I tell them is that I can pretty much show them all the basics they need to know in a long day; but that without knowing when to use these things, how to use them, what degree of the various implementations to apply, learning to see things coming sooner, hopefully before they create mayhem upon your person... it does very little good.

    I see programming as somewhat like that. I can show how to write a conditional loop, maybe teach what a class is, talk about different kinds of variables... but without considerable experience wrapped around those things, not to mention at least some math, some tech savvy, some idea about what hardware actually consists of, and a goodly bit of time, you're not going to be a "programmer" any more than a day under my tender care will turn you into Bruce Lee.

    Which is not to say you can't go out and get those things over the long term (by which I do not mean one year, btw). But most people are looking for the easy fix, and they, consequently, are going nowhere.

    Just an IMHO from a bit of a cynic.

    --
    I've fallen off your lawn, and I can't get up.
    1. Re:Story time by kdemetter · · Score: 4, Insightful

      It also depends on previous skills : if you know other programming languages, it's not that hard to learn a new one, because the concepts are familiar.
      However, if you never did any sort of programming, you first need to learn that.

      However, to be a professional programmer, you need practice, otherwise it's going to take too long for you to write any production code.

      It's like muscle memory : You should no longer have to think about syntax : you just think ' i need to iterate this list ' , and your fingers write a for loop .
      It's similar to martial arts , in that there you will think : evade, defend low, counter attack , floor , etc ... but you shouldn't have to think about the separate techniques.

      Regarding the article : The idea of CodeAcademy is great for teaching programming , but it shouldn't be just to get a high pay job. That feels like cheating your boss.

    2. Re:Story time by msobkow · · Score: 1

      A far more lucid and coherent argument than my offended outrage.

      But I still think the author of the original article was the first of a million monkeys to bang on a keyboard...

      --
      I do not fail; I succeed at finding out what does not work.
    3. Re:Story time by Bill+Dog · · Score: 1

      if you know other programming languages, it's not that hard to learn a new one

      1) No. For example knowing C still does not make C++ "not that hard to learn". Be an expert in Java and (modern usage of) JavaScript will still take a lot of getting used to. Grokking SQL is not helped by knowing any of the above.

      2) So? Even in the rare cases where your statement is true, such as going between mutually redundant languages like C# and Java, you can't hardly actually do anything with either of those two unless you learn the GUI or web templating and database access and networking and other API's in their expansive associated class libraries. (Of which there are usually multiple of each.)

      This is why I always shudder when I see the recurring "I can pick up any new language in a couple of weeks" sentiments posted to Slashdot. Maybe so, but they can't get a job in it unless it only requires coding for-loops and writing text to stdout.

      --
      Attention zealots and haters: 00100 00100
    4. Re:Story time by VanessaE · · Score: 1

      It also depends on previous skills : if you know other programming languages, it's not that hard to learn a new one, because the concepts are familiar.

      Dead wrong in my case. Sometimes, languages which should be at least similar, are so wildly different that none of your skills can transfer over. The platform one will be using the language with is equally important, to the point that changing from one architecture to another, while keeping the same language, can still require a whole new way of thinking.

      My first language was BASIC, on two different platforms, neither of which was particularly similar in the way their implementations and environments worked. I moved to assembly language some years after changing to the second platform in question, but the skills required to write in that language far exceeded what I needed for BASIC. Ditto when I started learning C later in college. Same thing happened again when I started learning bash scripting, and yet again when I started learning Verilog recently, despite them both bearing some similarity to C.

      Each language is/was different enough from the previous one to present a significant obstacle to learning it.

    5. Re:Story time by vell0cet · · Score: 2

      I agree as I'm a lifelong martial artist as well... but I will also say that knowing something tends to be much better than the majority of people out there who know nothing.

      And I've worked a lot in the IT industry, I would argue that the same is true there.

    6. Re:Story time by Patch86 · · Score: 4, Interesting

      I agree with you that practice and broader understanding are far more important than just knowing the basics.

      I work in IT, but I'm not a developer. I "know" code- in that I can look at a piece of code written in one of the more common languages and read what it's doing, and I can hold meaningful conversations with developers, and I can write amateurish little programmes for my own pleasure. But I am definitely not a developer; you ask me to write something of even moderate complexity and you're going to be dissapointed. It's not my job, and it's not a skill I've mastered to a professional level.

      If this CodeAccademy thing can get large number of people to just understand coding, understand what can and can't be done, understand the consequences of certain requests or decisions, and able to write BASIC macros for Excel, then it's no bad thing. But there's no short cut to training up a proper developer.

    7. Re:Story time by Tom · · Score: 2

      Just an IMHO from a bit of a cynic.

      You aren't cynical in the least. Lots of people with much more martial arts training than a day or two will simply freeze when they are met with actual danger.

      Few people understand that the mind works in contexts and settings. If you ever wondered why you can decide today that you will work out more, and not do it tomorrow, and feel no dissonance whatsoever - it's because the "you" that made the decision and the "you" that didn't follow through are not really the same person.

      And for many people it's a rude awakening when they find out that their training "you" never left the dojo.

      --
      Assorted stuff I do sometimes: Lemuria.org
    8. Re:Story time by Anonymous Coward · · Score: 0

      Quick self defence:
      1) Don't wear headphones when you're out and about.
      2) If you feel threatened, run away.
      3) Lose the ego, see 2).

      Not a very long day...

    9. Re:Story time by Hognoxious · · Score: 1

      Even if the languages are different that shouldn't be more than an irritation. What you should have picked up is higher level concepts that do transfer between languages.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    10. Re:Story time by dintech · · Score: 1

      I'm a martial arts instructor.

      I can show how to write a conditional loop, maybe teach what a class is, talk about different kinds of variables...

      The code-fu is strong with this one. I hope one day you use your skills for 'good'. That means dressing up in costumes at night and fighting crimes against software, with a band of ninja code reviewers at your side using powerbooks and ipads as your weapons. Teenage Mutant Ninja Turtlenecks, oh yeah.

    11. Re:Story time by Darfeld · · Score: 3, Interesting

      There are significant differences between language, but that doesn't mean in any way that you're starting from nothing each times.

      When you learned your first programming language, you learn some programming practices that aren't language dependent. When you learned you're second one, you learned a bit about the difference between syntax and logic, and so on...

      Also, most of the programming challenge isn't the language anyway. (well, can be... I'm looking at you, Perl!)
      It's true it does have an influence, but for exemple, you can think your programs pretty much the same way in all Object Oriented language.

      --
      (\__/) This is Lapinator
      (='.'=) copy it in your sig
      (")_(") so it can take over the world
    12. Re:Story time by q.kontinuum · · Score: 3, Informative

      I disagree. A bit of knowledge is a very dangerous thing at times, because little knowledge often comes with a lot of confidence. Better be ignorant and know it, thus avoiding a fight whenever possible, than being overconfident and receiving a beating.
      It's a bit related to the old joke between electronic engineers and software engineers. Says the electronic engineer: "What's the most dangerous thing in a lab? A software engineer reaching for the soldering iron!". Says the software engineer: "What's the most dangerous thing in the office? An electronic engineer discovering the C compiler!"

      Seriously: I saw some source code written by some highly qualified electronic engineers, and it was awful. They just have a different mindset. In electronic engineering for mass market products, cost-efficiency and real-live performance is probably *much* more valuable than re-usability and maintainability, since every cent saved on one device repays million-fold. In Programming readability / maintainability is among the highest priorities, and the runtime complexity of algorithms (http://en.wikipedia.org/wiki/Big_O_notation) is often way more important than current real live performance, because for later product iterations the amount of data might grow exponential, leading to extremely different "real live" performance.

      I can only imagine what pain the ee's suffer when they have to watch an se with a soldering iron...

      --
      Trolling is a art!
    13. Re:Story time by V!NCENT · · Score: 1

      Practise alone doesn't make you a good programmer. How about knowing this:
      -How does the OS that you're programming for, schedule?;
      -So when to use userlevel threading and when to use kernel level threading, and why?;
      -How many threads to use for what situation, where, and why?;
      -CPU caching; how little operations where? When does it and doesn't it work and why?
      -I/O scheduling; how does the OS in regards to the CPU schedule/interupt/que? Maybe interupts are disabled by the OS due to multiple cores?
      -And so on and so forth...

      Hacking away at Visual Studio for years, still doesn't make you a good programmer. Only arrogant.

      --
      Here be signatures
    14. Re:Story time by Culture20 · · Score: 1

      if you know other programming languages, it's not that hard to learn a new one

      1) No. For example knowing C still does not make C++ "not that hard to learn". Be an expert in Java and (modern usage of) JavaScript will still take a lot of getting used to. Grokking SQL is not helped by knowing any of the above.

      2) So? Even in the rare cases where your statement is true, such as going between mutually redundant languages like C# and Java, you can't hardly actually do anything with either of those two unless you learn the GUI or web templating and database access and networking and other API's in their expansive associated class libraries. (Of which there are usually multiple of each.)

      This is why I always shudder when I see the recurring "I can pick up any new language in a couple of weeks" sentiments posted to Slashdot. Maybe so, but they can't get a job in it unless it only requires coding for-loops and writing text to stdout.

      If it takes you a couple weeks to learn how to do a loop and output in new syntax instead of less than a couple minutes, then you've got serious problems. C++ was extremely easy for me to learn after I had already learned C. Likewise Javascript, Perl, et al. LISP took a mental reconfiguring, but once I accepted that recursion was the norm, I took to it in less than a couple weeks. And I'm not a programmer by trade; I'm a sysadmin.
      Once you know enough about one language (that there are things that allow information storage and retrieval, repetition, and branching), you'll know what to look for in the new languages and you'll spend less time on concepts and more time on syntax.

    15. Re:Story time by JasterBobaMereel · · Score: 2

      Learning a new language when you already know how to program should just be a case of :

        1) learning a new syntax - which should be straightforward ?

        2) unlearning to automatically use the syntax you are familiar with

      Only if you are moving to a completely different kind of language will you need longer (e.g. C++ to Haskell)

      If you can only program in one language and think in that language then you will have huge difficulty in changing languages, but if you learn to program in any language and think in the abstract and then learn the syntax of one language, you will have no trouble moving to a new one ...

      Writing efficient code, and learning all the quirks and tricks in a new language will take longer, but should not stop you writing good code....

      --
      Puteulanus fenestra mortis
    16. Re:Story time by AdrianKemp · · Score: 1

      I'd be a lot happier if even a tenth of the programmers I meet these days knew how to dynamically manage memory.

      Unfortunately the article is true, you could easily learn enough in a year (or probably a month) to get through an interview and get a job.

    17. Re:Story time by tbannist · · Score: 1

      I've even seen code from computer engineers (hardware, not software) where the engineers refused to use function calls because "they add unnecessary overhead". I also had a boss who taught himself PHP and decided that his hobby project should be our live customer facing credit card processing system despite the fact that it took about a minute to discover and exploit the first SQL injection vulnerability.

      There's a lot more to designing and writing good software than knowing the syntax of a particular language.

      --
      Fanatically anti-fanatical
    18. Re:Story time by Anonymous Coward · · Score: 0

      Not to mention that you can exports ideas from the styles you prefer (or are familiar with) to other languages, at least to some degree. ("I can write FORTRAN in any language", and all that.)

    19. Re:Story time by sick197666 · · Score: 0

      10000% agreed! Is Operating Systems 300-ish level class should be required for all CS students. I double majored in IS and I took the A+ class for IS and Operating Systems class in CS at the same time (on purpose, I added the IS major late, it was only like a 200~ level class) and I must say, learning about Operating Systems from both sides - the programmer of the OS and the power user of the OS - at the same time was a learning experience I wouldn't trade anything in the world for. It hands down made me a better programmer and IT manager at the same time, when you understand WHY the system is deadlocking BEFORE it crashes, why the SQL server is acting in such a way due to X amount of processes doing Y, etc, etc. It also helped a lot for the N+ and CCNA classes, when we're reprogramming our routers by command line I had a distinct advantage against the IS-only students who had no underlying grasp of the intricacies of the OS - even ones small/simple enough for consumer routers.

    20. Re:Story time by bckrispi · · Score: 1

      These concerns are pretty irrelevant for most web programming.

      --
      Xenon, where's my money? -Borno
    21. Re:Story time by c++0xFF · · Score: 1

      No, no no!

      I used to agree with you. After all, C, C++, Java, and C# all have nearly identical syntax. Just learn the slight differences between them and you know them all, right? Learn at least one language in each major class (procedural, functional, scripting, etc), and the next one of the class will be just about the same.

      It's a good theory, but reality is different. It's so incredibly obvious when C++ code was written by a C programmer. Or when Java code has been written by a C++ programmer. Just like with human languages, programmers have an accent when writing code in a foreign programming language.

      The difference isn't just syntax! It's the way code is organized. It's the way algorithms are written. Even code syntax with direct analogues (templates vs. generics, for example) tend to be used completely differently! And this isn't even getting into the issue of APIs.

      Learning syntax is like learning the grammar of a human language. APIs might be analogous to vocabulary. These will get you around and let you communicate to a point, but full fluency (and writing good code) will only come once you learn the culture, too.

    22. Re:Story time by Kamiza+Ikioi · · Score: 1

      So it's a stupid idea... yeah, I agree with that.

      --
      I8-D
    23. Re:Story time by c++0xFF · · Score: 1

      Back in the early days of C, some PASCAL programmers thought it would be a clever idea to do something like the following:

      #define BEGIN {
      #define END }

      Then the could write PASCAL code in C!

      If you've ever worked with such code, you know that the results aren't pretty. Thankfully the practice was short-lived.

    24. Re:Story time by KingMotley · · Score: 1

      Sorry, I disagree. Once you learn at least one language in each of the major types, it does making learning a new language extremely easy.

      Yes, there are ways of structuring code different, and many languages have different sets of coding standards or methodologies, but there are always many different ways to accomplish the same task. Just because the majority of programmers who use a particular language typically do something one way does not necessarily make it the correct way.

      I've done enough coding, in enough different languages that if you put me in front of a new language, and I'll be able to start producing in a matter of days. In weeks I'll be competent, in a couple months I'll be correcting the errors of the "average programmer" who has been working in the language for 5+ years, and in a year, I'll be an expert. This isn't a theoretical discussion for me, I've done it many times already.

    25. Re:Story time by hacksoncode · · Score: 1
      Not complaining about your point, but just a nit pick:

      If your data actually grows exponentially, it probably matters very little what O your algorithm is (unless it's O(1), of course :-), because even a linear algorithm will take exponentially longer with exponential data. Naturally, higher orders will break faster, and that might save you for a very little while. But if you're planning for exponential data growth, you need an entirely different paradigm.

    26. Re:Story time by Marxist+Hacker+42 · · Score: 2

      I agree with the parent and disagree strongly with the grandparent- but the grandparent does have ONE big point- SQL is different from HTML is different from Javascript is different from any Object Oriented language is different from any LISP Variant is different from Forth is different from Assembly. But once you've been exposed to the big 7 methodologies- jumping to a new language *within* any methodology you've been exposed to is cake.

      And I got exposed to all 7 in the Programming Languages Series at OIT back in 1991. In a year (well, Programming Languages I, II, and III taken Fall, Winter, and Spring Term) a new language every two weeks, NONE of which I've used since. But what I learned programming LISP, translated easily to Scheme. What I learned in Fortran and Cobol, translated easily to Visual Basic. What I learned in ADA and Smalltalk, translated easily to C# and Visual C++. What I learned in assembly on the PDP-11 (despite being in OCTAL instead of HEX) translated easily to 386x MASM. What I learned in Oracle SQL, with a few syntax changes, works just fine in Transact SQL, or even in mySQL.

      The rest is just "what framework am I on and what objects do I have available?"

      --
      SJW: a person who perceives an injustice, and while correcting it, commits a greater injustice.
    27. Re:Story time by Nethemas+the+Great · · Score: 1

      Hmm... Go learn LISP, now BASIC, then PERL, then Java, then FORTRAN. What concept is familiar? The fact that you use a text editor?

      Either way this is an absurd proposition for an average person with no previous experience to actually learn how to use {fill in the blank} language to express and solve real world problems, especially inside of a single year. Brains just don't rewire that quickly nor that easily. You'd have to eat and breath computer science and to some extent mathematics for the whole year to even hope to pull it off. While you're at it you'd best hope that your intellectual capacity really isn't all that average unless a sweatshop code-monkey is your ambition.

      --
      Two of my imaginary friends reproduced once ... with negative results.
    28. Re:Story time by q.kontinuum · · Score: 1

      not complaining either, but cpu speed and storage size usually also grow exponentially ;-)
      (Moors Law)

      --
      Trolling is a art!
    29. Re:Story time by Sam+Williams · · Score: 1

      That "easy fix" thing you mentioned...any idea where I can find one?

    30. Re:Story time by Bill+Dog · · Score: 1

      you'll spend less time on concepts and more time on syntax.

      As someone who's a programmer by trade, it's the opposite of that. Syntax is trivial to learn. It's applying the concepts of different kinds of programming languages that's the fun and interesting part.

      --
      Attention zealots and haters: 00100 00100
    31. Re:Story time by Anonymous Coward · · Score: 0

      Programming and martial arts don't mix. If you're good at one, you're not supposed to be good at the other... unless your best move is down, forward, back, back, high kick.

    32. Re:Story time by Bill+Dog · · Score: 1

      The rest is just "what framework am I on and what objects do I have available?"

      "Just"?!? Maybe you've made your living mostly doing contract work and dabbling in a multitude of technologies to be maximally versatile and knowing them just enough to get the job done. So maybe it's a YMMV thing, but I take "learn" differently than say a sysadmin who spent a couple of weeks on "learning" C++ at a superficial level and declared that it was easy. I've spent my career specializing on things, and over 10 years with C++ for example, and when I thought I had "learned" it, every couple of years I found out there was so much more to learn and that I really hadn't "learned" it when I thought I did.

      Same with frameworks. Esp. since there are so many, it's hard to find the time to get really good at more than just a few of them. So I guess I take "learn" more as "mastery" than "have become (sufficiently) familiar with". But I'm more of a depth person, whereas as others like to be more breadth people, tech-wise.

      --
      Attention zealots and haters: 00100 00100
    33. Re:Story time by emilper · · Score: 1

      coding is a vocation not a profession: most people can learn to code, but most of those that can learn to code will hate sitting 8 or more hours a day in a chair looking at lines of text in an editor or debating the advantages of various caching algorithms

      if CodeAcademy will help identify even 1% of the people that have the calling but got lost and hate their life doing some other work, it will be a positive result

      software developers are needed in all lines of work, from humanities to education to accounting ... the only reason there are no job titles like "archivist-programmer" is bureaucratic inertia; domain knowledge is more important than advanced algorithms and a developer that understands the business is more valuable than a developer who knows the Knuth and "gang of four" books by heart but has no understanding of the domain for which he is writing code

    34. Re:Story time by Marxist+Hacker+42 · · Score: 1

      Yeah, that's pretty much been my career- to tell the truth, I haven't had the time in any one position to learn more than "just enough to get the job done". But a big question is, why would you expect your employer to pay you for learning MORE than just getting the job done?

      In depth is great for academics, but in the real world, it's the guy with the breadth of knowledge that actually gets the job done. And as for learning frameworks? I find google (or really http://goosh.org/ because I like command lines) to be indispensable.

      --
      SJW: a person who perceives an injustice, and while correcting it, commits a greater injustice.
    35. Re:Story time by Bill+Dog · · Score: 1

      You're coming at this solely from a contractor's POV. There's a whole other (and very common) side to looking at this.

      For a temporary, hired gun type of job, I definitely wouldn't consider it ethical to get the organization to pay me for learning anything beyond what it took to get the job done.

      For that matter, I wouldn't really consider it right that the org pay me for learning *anything* technical, unless it was clearly stated or implied as already understood. That is, I think of contracting as specifically *not* for any on-the-job learning, except for the org's particular systems and way of doing things and maybe their problem domain. I think of contracting as hiring an expert in something technical, where as soon as they learn what it is that's needed to be done, they can immediately get down to doing it, because they already have all the necessary background in whatever technologies are involved.

      Whereas for full-time type employees, the view is often much more long-term, and the thoughtful ones are looking not only for someone who can get up-to-speed quickly (but not necessarily immediately), but also someone who'll stick around and grow with the job and the company.

      So my big question might be, why would anyone expect their employer to give them raises for learning nothing more than just getting the job done. And today's needs might not be tomorrow's needs. This is less of an issue in contracting, where I suppose they can just not re-hire you and instead go with someone who already and better matches the new needs. But in the full-time model it's in the interest of the org to invest somewhat in their people, and it's typical between projects to be given time, on the company dime, to ramp up on what's anticipated to be the coming technical needs.

      Not to mention as you become more expert in the technologies the org uses and learn more of their business and your salary rises, there's the expectation that you'll be willing, and also able, to move up into more difficult and valuable and contributory roles. Including mentoring more junior people.

      So in depth is great for academics, but it also fills a need for people like me who need it to satisfy our technical craving, and it's also useful I think for doing the full-time employee thing where you stay at a place for 5 or more years (when you can).

      But, this discussion has made me realize that there's a wiiide difference in people's definitions of "learning a technology".

      --
      Attention zealots and haters: 00100 00100
    36. Re:Story time by Marxist+Hacker+42 · · Score: 1

      After 16 years of "contracting" (in that even when I have a so-called permanent position, my continued employment is tied *directly* to what I can do for the company and there is no loyalty)- 99.99% of what I learn on any given job, is industry-specific stuff. I very rarely use the same API or piece of a framework twice, and the steep learning curve is *ALWAYS* the industry-specific data model and acronyms.

      I'm to a point where I doubt I'll ever be in a job for 5 years. 2 seems to be my average, and most last less than a year.

      Yes, there most certainly is a wide difference- in my experience, most hiring managers expect "Can you use the IDE and help files and ask questions of the rest of the team?" If you can do that, then you've learned the technology sufficient to get the job done.

      Raises- I've only seen two in the last 16 years that didn't come from me negotiating a new labor contract. Salary going up comes from changing jobs, not gifts from management who are already under pressure from shareholders to reduce budgets.

      --
      SJW: a person who perceives an injustice, and while correcting it, commits a greater injustice.
    37. Re:Story time by Bill+Dog · · Score: 1

      In order (and since I think we pretty much have this whole discussion to ourselves, by now):

      * That's rough, and a lot of pressure, having to come up to speed on a new API or framework *plus* a new business, every year. I already learn a new tech something each year, but usually with a heads-up, either by a boss or myself, before it's actually needed, so as not any real pressure. And learning a problem domain is the hardest, or rather longest taking, part for me.

      * If you've only been a short-timer all your career, you might indeed never get selected, or even interviewed, for a position where they're looking for someone to stay a while. I've had a few comments from interviewers about my two ~ 6-year stints and how they're looking for someone who sticks around. (Which might be advertising that I'm more easily abused, but when I need a job, companies are free to draw all the wrong, positive conclusions about me they want.)

      * "Ask questions of the rest of the team"?!? Man, I wish I had that luxury. Maybe in contracting you're given more respect, but asking questions in my experience puts you in danger. Like my current job, where they told me in the interview (for a Software Engineer level II position) that they'd hired junior programmers for it before, but they needed too much help, so that's why they were looking for someone like me. So I don't ask a lot of questions, and try to (appear to) be self-sufficient.

      * I've almost always got a raise, but they've been nominal except when they've been for changing jobs. But the intra-job raises seemed to have been about how indispensable I was (or not) for something, and the inter-job ones seemed to have had to do with which way the economy was going at the time. I.e. it doesn't seem like the shareholders had much say in it. You have to retain the talent you need, or promised delivery dates to customers get missed and expected sales/revenues then don't happen. And you have to pay for new talent according to the market. Reality doesn't leave much room for mgrs or shareholders wishing for otherwise.

      But I have a new outlook on salary. I'm 45 and am not at an "enterprise architect" level or anywhere near it, nor do I have really any project lead experience, so my goal is to be a bargain. I'd like to stay where I'm at a number of years, and get another good span of employment on my resume and show that I've bounced back from my long spell of sans job, and have future employers pleasantly surprised how cheaply they can get a solid, older dev. I hope it works.

      --
      Attention zealots and haters: 00100 00100
    38. Re:Story time by Marxist+Hacker+42 · · Score: 1

      Just this morning I found out that carrier market area has two different, simultaneous, meanings at my current job. It's things like that which keep me up nights.....I think I'm going to need the analyst who is feeding me my requirments to define when "carrier" means "MarketArea=33" vs "MarketArea27" except when it's "ProvisionalMarketArea" when the numbers become 37 and 27 instead.

      That's the kind of tech learning I have a problem with. Learning a new framework? Or even a new language, as long as I can fit it into the 7 language groups I've worked on before? Cake in comparison.

      --
      SJW: a person who perceives an injustice, and while correcting it, commits a greater injustice.
  99. DANGER! problems for even seasoned programmers.. by Cutting_Crew · · Score: 1

    out there today. Just look at the job ads. you see an ad for a C++ programmer. You scream for joy. Little do you know, before you click on that link, that you are about to have the hammer dropped on you by words like VB.net, ASP.net, python, perl, MS SQL, Websphere(what the heck is that?), BEALogic(wtf??), Rational Rose(WHAT THE?), MFC(yeah even something MS doesn't even support anymore), assembly/registry manipulation, Posix threads, awk, http/html, javascript. All REQUIRED for ONE job.....and YES there are PLENTY of job ads out there just like that.

    who in the right mind would apply for that job? even if you are seasoned how much are they gonna pay for that? and how many people born since 1990, most of them about to get out of college have ever heard of BeaLogic and RationalRose? I was born in 1976 and i had to go look up websphere, bealogic and rational rose up on google to find out for myself.

  100. Re:It's not something you do, it's something you a by Oligonicella · · Score: 2

    It's not a calling, it's a profession and you can learn it just like you can learn any other profession. Yes, you have to be intelligent enough to handle the concepts, but that's it and they aren't that hard.

  101. Re:Smells like a load by Curunir_wolf · · Score: 1

    Most good coders that I know are among the best at spelling and grammar. Probably because they have to know ... languages.

    --
    "Somebody has to do something. It's just incredibly pathetic it has to be us."
    --- Jerry Garcia
  102. Assumption: by ChiRaven · · Score: 1

    This assumes, of course, that the person can probably count above 10 with their shoes on. An assumption, by the way, which I've found is not always justified in some of the coders (and even some design engineers) I ran across during a career that spanned five decades in the business (OK, so just barely five).

    1. Re:Assumption: by bugs2squash · · Score: 1

      I agree, having twelve fingers really improves typing speed.

      --
      Nullius in verba
    2. Re:Assumption: by ChiRaven · · Score: 1

      Or anyway gives you two to keep crossed at final compile time as the errors come cascading out and you start to type in your patch code .

  103. Does this mean that by Anonymous Coward · · Score: 0

    Michael Bloomberg is ready to learn coding? He's probably got as much free time as anyone...

  104. Re:Smells like a load by ae1294 · · Score: 1

    ASSEMBLY

    'MOV me up' XOR my wife please...

  105. Let's accept the premise as true by Anonymous Coward · · Score: 1

    Let's accept that they can turn out professional developers in a year. If that's true, then they'll turn out developers until the wages become unappealing. They probably couldn't run it all the way down to minimum wage. A year is quite an investment, so the wage will be more than that. What jobs are there where people train for a year and get hired?

    Now, please don't take this as an insult to plumbers. You'd expect that a lot of people could become plumbers with the proper training. A quick Googling revealed that you apprentice for 4 to 5 years. APPRENTICE. The concept of plumbing is something that anyone can grasp--pipes, they gotta fit together, valves, blah, blah. We've all seen it in our house a million times. The devil's in the details though. If I had to replace a copper pipe with a torch and all that, it'd probably take me 10X as long as a pro. I'd be lucky not to have it leak the first time.

    Now that's plumbing. It's common. Anyone can tell you what it's there for. It makes sense. TCP/IP stack? RFC? Writing a TCP/IP stack based what you read in the RFC? It's so far removed from the every day world. I didn't do anything like that until I had been programming for 20 years, and it was challenging work that took months. OK that's a bit of an unusual task; but reading technical specs and coding up an in-house solution is something a developer should know how to do. Heck, how long before these people would even be able to read the API documentation and write a simple JPEG processer using libjpeg without any hand-holding? How do I parse the command line? What's a library? I have to link it? What's a linker? Shit. Not even funny. Totally not connected to the ordinary world.

  106. So.. by Anonymous Coward · · Score: 0

    For those of us with no money and no job who WANT to learn to code, what the fuck do you elitists recommend? There are precious few places that let you start from scratch and are useable without having to shell out for a college course. Kahn Academy and Code Academy are the only two things I've found that are remotely understandable. If people like me who want to code are such assholes, then why do I see threads every other week with slashdotters desperately trying to interest their kids/family/friends in programming?

    1. Re:So.. by Todd+Knarr · · Score: 1

      You don't want to learn to code. You want to learn to program. Analogy: you don't want to learn how to nail 2x4s together, you want to learn how to be a carpenter. To be a programmer you need 4 things:

      1. You need to know how to write code in the language you'll be using. That's the easy part.
      2. You need to understand how to analyze the problem and frame the steps needed to solve it. This has nothing to do with writing code. It's also the hardest part to learn because it involves building up a vocabulary of ways to do things, a library of ways to apply those things to solving problems, and a knack for breaking large intractable problems down into a collection of simpler ones that can be solved and combining those solutions to solve the bigger problem. You need to become good at inductive logic to succeed at this.
      3. You have to have a knack for seeing the right way to solve a problem. There's usually a lot of ways to solve any given problem, but some are more... elegant for lack of a clearer term. You can drive a screw in with a hammer quite successfully, you'll just need a very big hammer and hit the screw very very hard, and you'll do a lot of collateral damage in the process of succeeding. Or you can put down the hammer and rummage around in the toolbox until you come up with a screwdriver.
      4. For large enterprise projects you also need a knack for stepping back from what you need to do right now and looking down the road at the kinds of things you'll need the software to do 5 years from now. Many programmers who manage the first 3 things never make the jump to this one.

      The problem is that all but the first are things you won't learn in the simple "programming for dummies" courses.

  107. What a Maroon! by msobkow · · Score: 1

    It's time Americans begin treating computer code the way we do the alphabet or arithmetic. Code is the stuff that makes computer programs work -- the list of commands that tells a word processor, a website, a video game, or an airplane navigation system what to do. That's all software is: lines of code, written by people.

    I cannot begin to express my disgust at this oversimplification of a career that can take DECADES to master. The idea that you can "teach anyone to program" in a year is so fucking INSULTING it's not even real.

    Can you teach a doctor to operate in a year?
    A lawyer to handle a case in a year?
    An engineer to design a building in a year?

    Then why in God's name does this FUCKTARD think you can treat programming in the same way.

    What a way to expose his complete and utter ignorance.

    Tell you what buddy, how about we let people take over YOUR job. After all, it's just spitting out random words that make no sense. Anyone can spout nonsense. Apparently YOU get paid for it.

    --
    I do not fail; I succeed at finding out what does not work.
  108. Re:Smells like a load by msobkow · · Score: 1

    I READ the article, where do you think I got the quote from?

    Douglas Rushkoff must be the first of the million monkeys it takes to produce Shakespeare by randomly banging on a keyboard. As he's the first to utterly fail to produce even ONE coherent word, I think it's an apt analogy.

    --
    I do not fail; I succeed at finding out what does not work.
  109. The point is not being a software developer by Casandro · · Score: 1

    The point is to be able to write short little commands for everyday use. Commands you might only use once, and even when used once already save hours.
    People must understand how computers work in order to use them. Since the state of the art in GUIs is still horrible, this means they need to be able to program at least in whatever shell skripting language they have.

    This is something that needs to be taught like maths or history. It's something which everybody should have heard of. Then you will find people who are good at it around you. Those people will be able to actually use computers to gain productivity, and help others improve their productivity.

    I take some offence on the word "software developer". It indicates that there is a special class of people who are allowed to program, while the rest only uses it without being allowed to write a loop. This is a false idea. The task of the software developer is to make little pieces of "Lego" the users can incorporate into their own programs. Those programs might also be single line shell commands.

  110. Learn to code != Be a Software Engineer/Get Job by hughbar · · Score: 2

    I'm looking at all this with some dismay. Of course, learning a little javascript or [better, since it was designed for non-specialists] BASIC won't make people a real-world top-class coder, software engineer etc. Therefore, if people are realistic about expectations, this activity is fine, a little over-hyped perhaps, but fine.

    Secondly motivation and progression. Some people just want to learn a little code, for example, to process the csv file for their charity group or simply have fun messing around, learning for simple needs or out of curiosity. Others, especially people who are motivated but haven't access to paid-for tuition can use this [as they used to use teach-yourself etc] as a starting point for a more serious assault on computer science. Learning isn't just about jobs, instant skills or being the 'best' immediately.

    It won't teach them to listen hard to users or any humility, but that's another separate matter for a huge flame-filled thread.

    --
    On y va, qui mal y pense!
  111. Programmer is the new factory worker by Xipher · · Score: 1

    With so much manufacturing work going overseas or replaced with low maintenance machines we have a lot of people who can't do jack shit for the current job market. This is trying to take our assembly line workforce and convert them to programmers. The problem is programming isn't a learn and repeat process, it's a creative one. Just about anyone can do assembly line work, you get trained and just do the same task over and over until you rotate into a different spot. Programming requires the person at the keyboard to think about the process that function/module/task needs to perform and articulate it, something that requires a different thought process and much less common.

    We either need to find some other rudimentary tasks for those incapable of creative tasks to perform or our jobless rate is probably stuck in limbo. Sadly this means we are likely screwed until the other countries we have outsourced all this manufacturing work to reach our economic level and stop being so cheap. Will we be able to adapt before the pendulum swings too far and brings down the stack of cards.

    Then again I could be wrong and making a bad assumption about how much people can adapt.

    --
    I don't know everything.
  112. and also... by Anonymous Coward · · Score: 0

    knowing how to DEBUG.

  113. put up or shut up by Anonymous Coward · · Score: 0

    all you so called good coders -- post your code!

  114. good luck with that. by Anonymous Coward · · Score: 0

    You can fake it, but to be a confident programmer with viable solutions, that can bear the scrutiny of fellow developers? It's like being in a cage full of trogdors, fear of the unknown is a terrible thing, and you'll be swimming in it.

  115. I agree with the article by John+Da'+Baddest · · Score: 1
    A misunderstanding here is the Slashdotter's assumption that "get a good job" means getting a job specifically doing high-powered software development after taking this training course.

    While that might not be reasonable, I do see jobs where the addition of programming know-how (or even more awareness) would be helpful and can make the difference between available work or not.

    Eg, system/application integration. Sometimes a bit of glue programming is needed above and beyond doing installations and support. (Perl, anyone?)

    The business-type people (or anyone who talks in sound-bites) scramble to put a label on this activity. Tacking on "analyst" is getting old now, so maybe the new buzz word is "coder" which might have a different context than what the audience here is jumping all over.

    1. Re:I agree with the article by bugs2squash · · Score: 1

      Anything that raises the median level of understanding is good for all of us. How many times have I created "amazing" results using grep | cut | sort in a few seconds and then marveled at the way computing outsiders wonder at the magic of it all. How many issues have been caused through lack of understanding that "5" != 5 ? So many little things could be taught in a day or two that would really raise awareness and translate well into almost any field.

      --
      Nullius in verba
  116. learn by Anonymous Coward · · Score: 0

    I'm not a CS major (though I am a science major).

    I spent more than 6 months mastering emacs (15 years ago), then I learned to code. It's been very profitable.

  117. We're all equal by hessian · · Score: 1

    All minds are the same. They just need to be molded.

    We're all the same except for differences in opportunities.

    If we use rote memorization we can create millions of new programmers, who will be adequate and spend lots of hours in the office (I mean "work hard").

    Genius is a myth and does not exist. It's just pure practice and the right training.

    Give me your average mouth-breather and through the magic of education I can transform him into a top-performing coder overnight.

    We are all equal! If you disagree, you are a Communist.

  118. HOW COULD LEARNING BE BAD?! by cshark · · Score: 2

    And you call yourselves nerds...

    Look, you seriously don't need to know a lot to get started. Some people are talented enough to learn as they go.

    And just because you learn something doesn't mean you're going to enter one of the most competitive development marketplaces in the world to do it professionally. Those that do probably would have anyway.

    I would like to see programming in highschools. Seriously teach it to everyone, like Spanish. You learn things that are absolutely critical in life when you learn how to program, and a lot of supposedly normal well adjusted people are lacking some of these basic analytical and coping skills. Programming teaches problem solving, patience, linear thinking, humility, and an eye for detail. People that are artistically inclined will find that programming skills make them better artists. People who are not artically inclined will find that programming skills make them better people. Those are the things you take with you, even if you can't remember how to output hello world in base64 a year later.

    Maybe I'm being narrow minded and biased, but I'm not seeing the downside.

    --

    This signature has Super Cow Powers

  119. It is not only programmer by aepervius · · Score: 1

    Most persons taking a job without a passion will do uninspiring product and will be a chore to work with. No scratch that, it will be a job to work with them. You are not a special snowflake as programmer. It is just that we had the luck of having a lot of pationate people, much more than other profession IMHO, and we were spoiled by it.

    --
    C. Sagan : A demon haunted world:
    http://www.amazon.com/gp/product/0345409469/
    visit randi.org
  120. Well. i guess thats possible. by drolli · · Score: 1

    Good that the rates for people who can clean up the mess are higher.

    1. Re:Well. i guess thats possible. by cshark · · Score: 1

      I think when Bloomberg says "good jobs," he means what people with no training or skill would consider "good jobs." Entry level stuff. Damn nerds at Slashdot getting in a huff over their esoteric little programming cults. Nobody's taking our jobs. The cheap Indians though, maybe they'll have something to worry about, but I doubt it.

      --

      This signature has Super Cow Powers

  121. just what we need... by Tom · · Score: 1

    That's just what we need. More inexperienced people writing bad software.

    No surprise that IT has such a bad reputation. Look at the people we allow to run our servers, write our software and design our systems. Many of them are brilliant, few of them are good craftsmen. That is because we admire hacks and shortcuts so much that we allow them on production systems. No where else in any industry does that happen. Every geeky subculture, be it engineers, scientists or doctors (oh yes, doctors are very geeky - talk to some!) has its admiration for hacks - but the adult crafts see them as steps towards an elegant solution, not as the solution itself.

    We don't need lower barriers for programmers, we need higher ones. Much higher ones. We don't have a lack of coders, we have a lack of good code.

    --
    Assorted stuff I do sometimes: Lemuria.org
  122. It's when he says they taste good we worry by fantomas · · Score: 1

    It's when parent poster says they taste good we gotta worry!

  123. From the expert ! by Anonymous Coward · · Score: 0

    Isn't M. Boomberg the guy that thought that the city of NY did handle "quite well" the time management software debacle ?

    I think what he really want's is to get a large set of desk fodder that being quite useless but hard to distinguish from real programmer (if you are a pointy headed boss) so that :
    a: the prices get dragged down but not too much, so that
    b: you can use outsourced desk fodder in "elbonia"
    c: your projects never work anything close to on time, but while they drag on and on and on you can solicit nice fat campain subventions, and since the companies are in a nice foreign country is makes it just a little bit harder to trak
    d: profit !
    nb: there is no "natural" reasons why people in "outsourcing" countries should not be able to be good computer scientist, but:
    1) due to the income skew between "ordinary people" and "e-jobs" young people get pushed into jobs that they find quite boring, but makes their parents proud because they get 3 time their fathers salary (which is still nothing, but ...)
    so the majority doing things that they do not like do it badly
    2) the good ones find that there is little interesting work to be done locally so they move out of the country and therefore of the outsourcing pool
    3) the universities have trouble attracting good teacher and researcher, so the level of knowledge and in particular real scientific knowledge is low (many 3rd world universities think that an MSCE is a university curriculum, even if you have no morals and no interests in "how things are built", and are hopping to work for microsoft clients you still need to understand what and why you are doing something, not just where to click
    4) there is no incentive to deliver real quality (as opposed to what ever paperwork/trail you need to do to get FOOBAR certified), the longer the project the more overtime you get paid for, and since you are "cheap" it is cheaper to go on with you rather than change provider)

    So the solution is obvious:

      For the NYer here, please to the rest of the world a favor, Vote the f**g a**e out of office, and for all of you:
        just remember, re-elect nobody (not if they are the incumbent, nor if they had their chances before, if you are not sure of your choice, use the following algorithm
        remove anybody who was elected before (even if you liked him or her, if that person really tried it will be grateful for the holidays)
        remove the ones you would really hate
        use a dice to select if there is more than one left
    if there is none left try to writein yourself

  124. Nothing is easy... by Genda · · Score: 1

    Nothing is "simple". When Jane Goodall first did her research with chimpanzees in the field it was because women were so so despised in the then male dominated field of biology, that no lab would have her and her only access to real research was in the field (a place where very few leading researchers spent any time.) What was particularly interesting is, that at the time the definition of human being included the use of tools. She discovered that chimps were fishing for termites with specially prepared sticks that the apes would carefully fashion for the task. When word got back to the main body of researchers, they had to change the definition of what it meant to be human and spoke of the primitive use of tools. Jane laughed and said "Primitive? You try fishing for termites with a stick." In fact the skill requires such finesse and care, that it takes a human being almost as long as a chimpanzee to perfect the skill. That is, it takes weeks, even months of training.

    Plumbing, isn't just sweating pipes. Its following code. Its knowing about the relationship between flow, pressure, and hydraulic shock. Its being clear how to plumb a system so your fresh water source never gets mixed with your grey or black water even if for some reason flow reverses. There are thousands of important issues to be aware of to perform plumbing well, even more to do it brilliantly.

    At one time I worked with plumbing for semiconductor furnaces. These were very critical lines carrying N2, SiH4, ArH4, PH3, gases that are toxic in part per billion. We had to use helium leak check equipment to ensure the security of our plumbing. Advanced fittings, exotic metals, high vac and pneumatic systems, all of it is just plumbing.

    Basic or simply scripting are coding. Dynamic HTML sits on the borderline between coding and simple content. I don't know what they plan on teaching in a year, but it depends on the person playing. Give a bright kid a little rope and he might just get all boy scout on you. More often then not though, expect some poor sod to hang himself.

  125. Coding is not about mathematics... unless it is. by Anonymous Coward · · Score: 0

    "Learning code is not about numbers and mathematics. It's more like architecture, where you are presented with a puzzle problem such as "How do we get all these cars from this highway to that one without having to build a bridge across this river or putting an overpass next to the hospital?"

    Wow, I mean I understand that some, especially web based coding might require less math, but this makes as much sense as saying "Building a bridge is not about engineering or mathematics! It's more like construction work, where you pile lots of cement and build some columns over a water body."

    Not to mention, ironically, the problem they presented as an example, for a "puzzle problem, nothing like mathematics", has everything to do with math, and could actually be a typical OR problem, to be solved with rather sophisticated optimization algorithms. After tens of math classes I still wouldn't understand all kinds of methods to approach this problem, but yeah don't take my word for it. Maybe universities should consider creating a degree "BSc. Puzzleology" where people are taught to solve these kind of "puzzles" without math.

  126. Ugh, not. SKILL is a required. by drwho · · Score: 1

    Maybe there are some geniuses out there who could do it, but learning to be a COMPETENT and valuable programmer takes more than a year. More than two years. There's a reason why it pays a lot - because it is HARD and requires SKILL and KNOWLEDGE. Maybe some factory could turn out a number of stumbling oafs in a year, who would make things worse by not knowing sound programming practices, but this is a BAD thing. We have enough problems with people, particularly those from China and India, faking credentials in order to get programming jobs (but I must say there are also a lot of talented programmers from those countries). We don't need more people dumped on the market with lots of dubious credentials and little skill.

    People need to have fundamentals which make them valuable thinkers, such as basic skills in communications (English, or whatever the language is of the country in which they reside), mathematics, physics, reason, logic. Then they can attempt engineering (I suggest we need more mechanical engineers in the world), metallurgy (sorely underrated), biology, etc.

    Not everyone needs a doctorate! I'd rather have a handful of competent BS or BA people than an incompetent doctor! I know that's not the style these days, but it's how I'd run things.

    Sometimes I think I belong in the 19th century America, with individual discovery and exploitation of the principles getting one ahead (in spite of Edison). Alas, steampunk style does not guarantee success...

  127. Re:It's not something you do, it's something you a by kaizokuace · · Score: 1

    I think I kind of agree with your position yet not quite. I think it's just a little harsh and doesn't leave room for the gray(grey?) area. I'm don't consider myself a software engineer or whatever term as I only recently really got into learning programming and software dev a year ago. But I do understand that there are types of people. I for one am the type to want to know how things work and don't feel comfortable using something that I don't understand. So for instance this drove me to take apart cars and do all work on my cars. I pretty much know everything about cars but am no engineer by any means. I've been using computer since childhood (I'm 29) and just fiddle with things. I played around with programming when I was younger like in jr high and high school but then got into 3d animation and have been on that adventure for a while. In college I was a comp sci major for like 2 years then switched to be an animation student. After working as an artist and spending so much time working on that I finally decided to try my hand at getting into programming again as it is something I really want to learn about. There is something interesting here though. Suddenly I am able to learn this shit way faster and easier than ever before previously. All the concepts of programming are just clicking. I had a hard time back in the day learning. So, I guess for me the gray area is timing. I somehow achieved the necessary mindset to be able to learn programming concepts and I don't know why. Maybe you have some input?

    --
    Balderdash!
  128. Re:I smell a pile of low cost poor quality cowboys by Hognoxious · · Score: 1

    I smell a pile of low cost poor quality cowboys coming onto the market and underbidding the competent contractors.

    Does anyone remember when "cowboys and Indians" was a kids' game and not a tautology?

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  129. Industrial age thinking will kill us by svetzal · · Score: 1

    The world does not need more code, it needs better code.

    The more code we have, the more humanity needs to maintain. This is a problem.

    I'm not saying this won't work, but I question our ability to inspire and train competent software developers. Software development is a big process that involves a wide array of skills, many more around human interaction, logic and communications than memorizing syntax and APIs. The way I see "programmers" taught continues to focus on syntax and one or two API ecosystems, and ignores the fact that programming languages and API ecosystems change fluidly and frequently. Graduates arrive ready to work in a world that was 5 years ago.

    When a developer comes to me, I don't give a crap about the alphabet soup on their resumé. I care about whether they are good at working with people, and good at adopting new technologies.

    1. Re:Industrial age thinking will kill us by cshark · · Score: 1

      No, I think you're missing it. The world does need more low quality code if we're all going to continue to be gainfully employed. Without really bad code to fix, where would all the lucrative rewriting work come from? I for one welcome our low skilled friends in new york.

      --

      This signature has Super Cow Powers

  130. What a hoot!! by Anonymous Coward · · Score: 0

    And you wonder why things screw up? Why there is no security in websites? Why you can't get a company to do things right and mail your order on time?

    What a hoot! Why not hire the homeless and mentally ill as well as programmers?

  131. LOL by Anonymous Coward · · Score: 0

    I have been programming for 8+ years and even when I finally got into the business world I am STILL learning a fair bit

    When you graduate and enter the real world, that's when the learning begins.

    1. Re:LOL by Zmobie · · Score: 1

      Only true to an extent. Like I said in my post, the initial education is laying foundation which is the most important part of creating a good software engineer. Actual applications of the concepts is akin to the way engineers work to begin with. We know tons of math and physics principles but the engineers job is to apply those principles in a meaningful way. It is very difficult for people to apply principles that they never learned.

  132. Actually.... by Anonymous Coward · · Score: 0

    I can never remember my login but here goes.

    I think that these type of 'learn to code' / 'teach yourself' sites can work to actually get people thinking in the right way.

    Yes some people sneer at javascript but it is a computer language (for want of a better expression that people will pick apart) and that can be used in an instant (notepad + browser) way to show how simple programs work. At this point you can introduce the basic ideas of programming and build more complicated ideas.

    I learned to program when I was 12 (I am 33 now and develop software for a living) using BBC basic - then I learned about using sub routines and building procedural code, then memory manipulation. It was great and I stopped in my teens then at uni I learned C - which I made huge leaps in compared to my peers (all in an Electrical Engineering course - so they were not too slow) because I had a good grounding.

    Take Javascript further and learn about asynchronous, event driven programming. Believe it or not but you can do something like 'OO' concepts in Javascript even without a framework. Thinking of frameworks, you can introduce the idea of using and writing 'libraries' of code and you are starting to think like a proper developer.

    I am not saying everyone should learn javascript and it really is the business - it can be any (half decent) language but it is all in how you teach the early concepts and what you manage to instill into (hopefully keen and eager) minds. Learning programming is quite literally conceptual to start with. get the concepts right and understood and you can translate that basic understanding to so many other languages and systems.

    Just my idealized two cents

  133. programmer, hell, become a manager by Coop · · Score: 1

    From what I've seen, manager boot camp takes 0 days, and you can declare success no matter what happens. Kind of like politics. Oh, wait, exactly like politics.

    --
    "If you're not passionate about your operating system, you're married to the wrong one."
  134. And my boss by RichardCory · · Score: 0

    will hire them!! After all, it's just a lot of misspelled words with way too much punctuation. How hard can it be?

  135. 1 billion Indians believe this too by Anonymous Coward · · Score: 0

    Almost 1 billion Indians believe this too and work for 1/3 less.

  136. Re:It's not something you do, it's something you a by thetoadwarrior · · Score: 1

    You have to care about it and not everyone does. That is what makes the difference between a good coder, mechanic or most any other job that's harder than typing letters or stack shelves.

    Most people could draw well too but most people don't want to invest the time into learning it. Same with coding. CA is probably going to be a good start point but it's just that a start point. You won't be a good coder by the end.

  137. Trying to out-India India by Anonymous Coward · · Score: 0

    They're trying to get India to re-outsource their currently outsourced jobs to even cheaper coders.

  138. Learn To Write, Find a Job as Journalist by Anonymous Coward · · Score: 0

    Following that logic: Learn To Write, Find a Job as Journalist

  139. Get a job? by Anonymous Coward · · Score: 0

    These guys are so smart! But they should teach us something more in demand. How about learn enough to become a doctor in a year. Wow it only takes a year. I could be rolling in the doe in no time. Sign me up.

  140. My name is tomhudson by Anonymous Coward · · Score: 0
  141. nothing shuts a person down like a compiler error by Haven · · Score: 1

    Writing programs is pretty easy... relatively easy to the near impossible task of debugging programs.

    I'm an artist that uses code to create my work (openFrameworks, processing, vvvv, quartzComp, libcinder, etc.). I code 15-18 hours a day. I am ALWAYS thinking about code.

    My bugs bend my mind into a pretzel. I couldn't imagine someone who hardly cares about this putting in any real effort.

    What kind of programs do people who do it only for a job write?

  142. This is an accurate fact. by Anonymous Coward · · Score: 0

    Stop complaining. Coders aren't special.

  143. A flawed concept, but not a new one by Anonymous Coward · · Score: 0

    So the average joe/jane thinks they can be a rockstar developer in addition to their day job. How many other people out there have tried to do their day jobs and think they can also be an expert mechanic, or a seasoned investor, or any other job that takes years of full time experience to master? Some people will never learn the concept of the division of labor; let evolution deal with them as it deems fit.

  144. Get Over Yourselves by Anonymous Coward · · Score: 0

    OK, some code is excellent, but the majority? Well, most of it is just like plumbing. Dead simple routine jobs to get the task accomplished. I really wish coders would finally wake up and smell the coffee - we know that what you do is mostly simple, most of us can do it too now. You're not special, you're just another form of manual labor.

  145. Where can I sign up by SpaghettiPattern · · Score: 1

    Where can I sign up? To become a brain surgeon. Within a year or so.

    I'm very tech savy. I'd have no problem in screwing a frame on someone's head, to cut away skin, to very carefully drill a hole in a scull and to insert an electrode in the right place. Hell I'd to the systematic checks in order to assure that I'm not damaging anything in the process. Imagine how much time I could save a real brain surgeon!

    That didn't sound too convincing, did it? Just as convincing as people trying to code in one year. Sure, you'd be able to write a small program on your private system. But you can forget doing anything half meaningful. Unless you have real talent in which case you still need a formal CS education.

    --

    I hadn't the slightest objection to his spending his time planning massacres for the bourgeoisie... (P.G. Wodehouse)
  146. About martial arts, the worst part is by Travoltus · · Score: 2

    Teaching them how to react PROPERLY when their fight or flight response kicks in.

    You know, like when your adrenaline levels hit 125 heart beats per minute, and your body goes into its first stage of panic. Things go real weird with the mind at that point. People freeze up or go psycho. Their ability to make rational decisions and think out their subsequent reactions plummets dramatically. Which means everything you just taught them goes right out of the window when a predator jumps in their face. Let's not even talk about when a crisis drives you to 150bpm or higher.

    You can't teach people how to adapt to this inside of a day, and without being able to adapt to that 125 bpm level 1 panic mode, anything you teach them is fairly useless.

    --
    --- Grow a pair, liberals... stop letting the Republicans bully you!
  147. The first skill a programmer should learn by Travoltus · · Score: 1

    Is how to speak a Slavic language or Hindu.

    The second skill to learn is how to get a passport.

    --
    --- Grow a pair, liberals... stop letting the Republicans bully you!
  148. Look everyone: It's "Krispy Kreme's" #1 customer! by Anonymous Coward · · Score: 0

    tomhudson = Lard body & eats 2 wheelbarrows of donuts @ 1 sitting!

  149. DOable... by hesaigo999ca · · Score: 1

    My best teacher of all time, was my programming teacher, he could tailor his teaching style to match your learning styel, we do not all learn the same, yet he had most of his classes with high grades because everybody got it, and it was thanks to him. I was in an intensive 1.5 year course, highly intense....day in day out...but the .5 of it was 6 months stage...on the job training, so technically I knew how to program by year end. It is very doable if you have a proper curriculum, and have set goals that are realistic. Keeping on top of what needs to be done is the most important. If you set a timeline, you must respect it, else you fall into the procrastination
    and this is where a week project turns into a month long one.

  150. Missing from the article... by CFBMoo1 · · Score: 1

    A section should have been added about documenting your code. If the article had that it would have been better.

    --
    ~~ Behold the flying cow with a rail gun! ~~
  151. I love this idea :-) by Tanuki64 · · Score: 1

    And why not? I make most of my money with failed projects and crappy code.

  152. In The FUTURE!!!!1 by Anonymous Coward · · Score: 0

    I think in the future everybody will have some degree of programming expertise as software become as ubiquitous as mathematics. There are many, many jobs that require or at least would benefit from some degree of programming skill. I believe that in the future teachers will be explaining to students how everybody ("even strippers") needs to know how to program, just as is the case with mathematics today.

  153. A No Brainer... by Anonymous Coward · · Score: 0

    Hey, have you seen the code produced by the average consultant? Most people can write code that good with only one month of training!

  154. Do you smell it... by Hangtime · · Score: 1

    All the articles coming out about start-ups, being your own boss, writing your own iOS app and making money....sure smells like 1999 - 2000 to this Slashdot old-timer.

  155. uninspired programmers by SolusSD · · Score: 1

    The last thing the world needs are more "day job" uninspired programmers.

  156. Re:Smells like a load by oh_my_080980980 · · Score: 0

    America the new sweat shop of coders.

  157. Lifetime job security by Sir+Realist · · Score: 1

    Lifetime job security fixing or replacing badly-written code, here we come!

  158. Create and promote language mere mortals can learn by Anonymous Coward · · Score: 0

    If you want ppl to learn to code, we need to create and promote a language the causal user can learn and understand. This ridiculous java and other OOP bullshit has to go.

  159. Trainig by Larry_Dillon · · Score: 1

    This has been a problem every since businesses stopped being willing to train! I hate to say it, but business has brought this on themselves by thinking they can find someone who's a prefect fix off the street without providing actual training (versus learn-as-you-go which is the norm everywhere I've worked). Companies seem much more willing to invest in other things besides their employees. The workforce as a whole suffers.

    Sure, you can get generic training at school (and accrue a mountain of debt) but whatever they teach you isn't going to be the exact skill-set that a given employer wants. I'd like to see some sort of program where a company provides, for instance, two years of training (perhaps 4 hours of formal training and 4 hours of mentoring (like working with an experienced programmer)) in return for a contract to work for another two to four years after the training. All programmers should take a turn training because nothing makes you lean a subject like having to teach it.

    --
    Competition Good, Monopoly Bad.
    1. Re:Trainig by Matheus · · Score: 1

      Training only goes so far. The company I work for is in a very specialized field. It is extremely rare that anyone we hire would have any experience with our business and so we don't expect it. The presumption is, depending on the quality of the dev, there will be at least 3-6 months where we are doing little more than training (including babysitting any dev tasks assigned) heck I've been around for 4 years and I learn something new every day (hopefully that'll never change).

      What is prohibitive to teach "on the job" is how to think like a programmer. If you don't have the mind to wrap your brain around a problem (any problem) and find a logical way to fix it then no amount of training is going to get you there. It is not necessarily impossible to tech these things but the gap for some is just too much to bridge and that bridge is not one you're going to teach a new hire. Some people just weren't meant to be developers just as I wasn't built to be many things I don't pursue in my work life.

  160. KISS by Anonymous Coward · · Score: 0

    I for one love this idea and the direction bloomberg's taking. Simple things like copy/paste, using excel, googling are important skill sets that we IT-folk take for granted and write off as simple. However, there are too many people [around me] that don't know how to do these simple things. This is an opportunity for a huge collective productivity boost. That's how I interpret bloomberg's actions.

  161. Arrogance by nagalman · · Score: 1

    I am seeing a lot of arrogance in the replies to these posts. Maybe it is because the original article mentioned the idea of getting a job after completing these lessons. Maybe its because some people feel threatened. Maybe its because some people can't conceive of the possibility that another person might be able to be as good or better than they are because they didn't share the same experience. CodeAcademy is a great idea. It is a relatively ease and free way of learning the BASICS of programming and software engineering. It easy to see how someone could complete a course or two and dive further into the art of software development. They might take a course at their local college, MIT OCW, Khan Academy, etc., get involved in an open source project, or just have a greater understanding of complexities of what make our digital society work and more respect for the "real" programmers. Get over yourself.

    1. Re:Arrogance by cshark · · Score: 1

      This one needs to be modded up. Anything that brings more low level programming jobs to America by increasing the labor force is a good thing.

      --

      This signature has Super Cow Powers

  162. Re:Smells like a load by Tanuki64 · · Score: 1

    This might depend on the language. Some languages have a more fixed set of grammar and spelling rules than others. As programmer I love to learn patterns, which I can apply to a well defined group of problems. My native language is German. And it is an extremely ugly language when compared with a computer language. Exceptions of exceptions in exceptions in every imaginable grammar and spelling rule. For each exception there might exist a historical reason, but in many cases they don't follow a apparent logic. Many of the mnemonic tricks given by teachers to at least give the appearance of some logic behind those exceptions, are utterly worthless. They all could be compared with algorithms, which works only in 85% of all cases. As a programmer I would not want to rely on crap like that. So in contrary to your experience, most coders I know are much better in computer languages than in German.

  163. Re:It's not something you do, it's something you a by tehcyder · · Score: 1

    Guess what, it isn't. It's more of a way of life. You don't become a coder, programmer, software engineer, or whatever it is you want to call it. You either are, or you aren't.

    That's utter hogwash. You're no more a born programmer than you are a born doctor, actuary or lawyer . All require a certain level of intelligence plus lots of hard work to become good, but they're not like being a concert pianist or professional sportsman which only a very few can ever achieve.

    --
    To have a right to do a thing is not at all the same as to be right in doing it
  164. Let's get over ourselves.. by segfault_0 · · Score: 1

    I'm sorry, but it's perfectly possible to learn enough to write fine code in a year, even in a self-directed manner (since you are free to study current material it may actually be beneficial to do so) -- the limiting factors are experience, aptitude, and desire -- not a degree.

    I've seen far too many people come in the door with a nice degree and an entitlement attitude, just to watch them sit in a corner and flounder about. What makes it worse is that they are often unaware of their ineptitude, and having that degree in common with other successful engineers, they tend to make poor assumptions about their place in the scheme of things.

    Now many of those who work hard and spend the $$ to get a fancy piece of paper often have those important attributes I cited, but we should avoid mistaking cause and effect.

    --

    I was crazy back when being crazy really meant something. (Charles Manson)
    1. Re:Let's get over ourselves.. by PhloppyPhallus · · Score: 1

      Also, learning how to program a computer is an important skill, even if you aren't working as a developer! Knowing how to write a script to manipulate text files, or to plot complex data in different ways, or to code and automate a complicated calculation in a spreadsheet macro are useful skills many workers could benefit from having. A lot of programs are written for use by one person to do one thing and maybe even to do it just once. They don't need to be efficient, well written, or easy to understand so long as they work, and in working they can bring huge gains in productivity.

      I think knowing how to program is becoming a lot like knowing math beyond arithmetic. There are lots of jobs you can do without algebra, but mathematical knowledge opens up many doors and there's a clear line in demand and salary for normally obtainable jobs which require a mathematical background and those that don't. If you're an engineering, a machinist, an accountant, an economist, a typesetter, so on and so on, not knowing how to write at least small programs simply won't cut it for much longer. If you're an innumerate assembly line worker, opportunities for success without extra training and skills are just getting farther away.

      So sure, CodeAcademy won't get you a job as a programmer; but it might help you make the leap from unskilled to skilled labor. Developers and IT professionals are not the only people who program as a part of their jobs duties--you don't need all of the skills of a developer to write useful programs. I think the IT centric /. community might not appreciate how many people outside IT use some programming knowledge as a part of their job duties.

    2. Re:Let's get over ourselves.. by segfault_0 · · Score: 1

      I agree totally. Knowing a little programming can only help.

      --

      I was crazy back when being crazy really meant something. (Charles Manson)
  165. Re:The last thing the world need is more bad coder by segfault_0 · · Score: 1

    "Average person", as you're using it, is a meaningless concept. Average intelligence? Average creativity? Average aptitude? Average aesthetic ability? Average what? Does this mythical average person only ever possess average quantities of each? And who decides what average is?

    Obviously, the people trying don't find themselves so mediocre that they don't want to try.

    I'm not trying to troll you here, but there is nothing realistic about your perspective. Take a look at a Gaussian distribution -- that is the reality. The "average" outnumber the "special" people by orders of magnitude and will, without exception, have to do occupy the jobs you state they should never do.

    --

    I was crazy back when being crazy really meant something. (Charles Manson)
  166. Re:DANGER! problems for even seasoned programmers. by scottbomb · · Score: 1

    I suspect those ads are placed just to pacify the Dept of Labor. After getting no replies, the employer can then say, "See? We can't find qualified candidates! We need that H1B!". The real job probably requires only 1 or 2 of those skillsets.

  167. What a crock! by Anonymous Coward · · Score: 0

    As someone who spent the first half of the oughts "between positions", with decades of experience, the number of CS grads and experienced people out here is so large it's a buyers' market; these kiddies with neither experience nor degree* will, if they're incredibly lucky, get something paying not much more than flipping burgers.

                  mark

    * Let's not even *start* to talk about how not one of them will ever get passed through an HR dept, who, since they don't no diddly, substitute certificates and degrees to even let hiring managers interview, much less hire.

  168. I think what ppl might want to learn is... by Ex-MislTech · · Score: 1

    Survival basics if the economy collapses and a major inflation event
    makes money nearly worthless.

    Be ready to evacuate away from any concrete jungles when it all falls apart,
    and good luck !!!

    --
    google "32 trillion offshore needs IRS attention"
  169. Training? We needs some. by Caerdwyn · · Score: 1

    I can't speak to the effectiveness of a one-year coding boot camp.

    What I CAN speak to is the effectiveness (or lack thereof) of the academic training people are getting. My group has had open positions for almost a year, because we can't find anyone with decent IP networking, scripting/automation, and QA skills. We're getting applicants... lots of them.... with master-of-science degrees in computer science who can't write code to traverse a directory tree or automate an SSH login. And these degrees aren't from "Smilin' Fred's Used Truck Parts and University"; these are major accredited universities like Stanford and UCLA. It doesn't matter whether the applicants come from the US, Europe or Asia; none of them are qualified. Those folks should be mighty upset at their schools, because by the time they emerge from college with a Master's degree they're carrying six figures of student loan debt, and all that money has not prepared them to be hired.

    We pay well, we're consistently in the top 5% of places-to-work rankings, we pile benefits on employees until they submerge, we don't do 60+ hour workweeks, and we still can't find a qualified candidate.

    I'm all for the one-year boot camp, because six-plus years of academia sure aren't working for squat.

    --
    Everybody gets what the majority deserves.
  170. Programmer vs Software Developer by slapout · · Score: 1

    "learn enough to work as a Software Developer by year end."

    There's a difference in being a Programmer and being a Software Developer. A programmer writes code. A software developer not only writes code, but understands were things fit together in the bigger picture.

    --
    Coder's Stone: The programming language quick ref for iPad
  171. IQ? by Anonymous Coward · · Score: 0

    Has the average person's IQ been taken into consideration in light of the intelligence required to be a good programmer? I can't see someone with 100 IQ writing great code. Sorry.

  172. Re:Smells like a load by Marxist+Hacker+42 · · Score: 1

    Since syntax checking. :-)

    My belated opinion on the original article- coding is a hell of a lot easier today than when I started. Almost all the common patterns and algorithms are in the framework libraries, no matter which framework you're programming in. I wouldn't hire somebody with this experience as a senior developer- but as a first year initial hire, no problem.

    --
    SJW: a person who perceives an injustice, and while correcting it, commits a greater injustice.
  173. Wow CBTs making a come back! by pkinetics · · Score: 1

    CodeAcademy is just that... Computer Based Training modules revamped into a webby centric platfrom....

    I hated them when I started out, but management deemed them totally cool and the greatest low cost way to teach old programmers new tricks.

    The old programmers hated it because it was mind numbingly slow and ineffective at retention of new concepts.

    The young programmers hated it because it was mind numbingly slow and ineffective because these were concepts we learned before the CBT was designed.

    CBTs are reactive programming to address yesterdays problems.

  174. Re:The last thing the world need is more bad coder by gweihir · · Score: 1

    Your model is flawed: You get a Gaussian distribution for each specific talent requirement profile. Some may be in the, say, top 5% for poet, others for engineer and still others for mathematician. If you are not in the top 5% for "coder", you have no business trying to work as one, as you will do more harm than good (fuzzyness applies). Same for the other examples. However even if you would not be a good coder, you may still be a good candidate for poet, doctor or mathematician.

    Hence "average" always refers to a specific talent profile, not a specific person. Sorry if that was unclear.

    I expect there are people that are really talented at nothing, but the typical "average" person (as in "randomly selected") should at least have better scores with regard to some talent profiles.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  175. coding in a year??? by Anonymous Coward · · Score: 0

    can happen, if you look at the far end of the bell curve. Very unlikely, there is just too much to integrate to be anything other than just above a general luddite computer user, who really doesn't want to know more. A single programming language is about like getting thru first grade.... move on to another, you'll find that your understanding of the first goes WAY up.

    Coding takes learning HOW to think in certain ways as much as it does thinking creatively.

    Being able to see the peices and how they fit in the whole. This takes experience, and experience of this type takes years, and plenty of refinement.

    I've been programming professionally for over 15yrs, and a professional DBA for over 5yrs (with 15+yrs of heavy experience, in very large databases), and i learn how to do things better, really on a daily basis.

    A true programmer isn't relegated to a single programming language. A true programmer is identified by his ability to think a problem through, by truely using the "Divide and Conquer" methodology (language inspecific) we all learned in 100 lvl CS courses . (if you took one)

    The question I have is given the equivalent # of 'supposed' years of experience, how can you tell a good programmer from a ..... not so good one. I've seen and work with both, but how do you do that in the hire process?

    I make the supposition, that by determining what 'potential' canidates do at home for side 'fun' related to comptuers is more telling than a lot of work 'history'.

    is this person a technologist? or a job seeker? a) is much more likely to deliver, b) yawn.

  176. (A => B) => (!B => !A) by epine · · Score: 1

    There is always elitism, but you miss the point. Most people can't think their way out of a wet paper bag.

    Wason selection task
    Correlation does not imply causation

    In the second case, you get wankers who take this maxim far too seriously, when they should be reasoning "where there's smoke, there's fire". The vast majority of valid reasoning falls below the harsh standard of implication. Programming escapes many people, because you have to have one foot in each camp. pfail = 1e-6 is no good for a file system. In debugging, the common case is to succumb to the rare event.

    I've worked with really good students who can't consistently manage to get modular clock arithmetic right on a micro-controller. In the vast majority of cases, normal algebra applies, except when it doesn't.

    /* monkey number one */
    u16 begin = clock();
    while (clock() - begin < 100);

    /* monkey number two */
    u16 begin = clock();
    while (clock() < 100 + begin);

    In a normal programming task (e.g. far away from the file system), this kind of small distinction isn't critical every hour of the day. But when it does become critical, you need the kind of person with an instinct for realizing "but wait, this might be the tricky bit, slow down a think a bit here".

    This requires an innate capacity for self-monitoring the process of conviction. Many people have it, more people don't. The second group will never become value-added programmers whether they are trained and paid a wage or not.

  177. Re:It's not something you do, it's something you a by epine · · Score: 1

    You're no more a born programmer than you are a born doctor, actuary or lawyer .

    Yes, but if one spends your first twenty years growing up in a New Age cult of evolution deniers, one is awfully late to the party when it comes time to buckle down with intelligence and hard work.

    When you're picking teams at the staff picnic to run the obstacle course, do you pick the kid who practically lived on a skateboard growing up, or the bookworm with coke bottle glasses? A secure sense of balance navigating logic-dominated systems takes just as much work to develop as a bunch of skateboard tricks.

    We had a kid in my residence who had never wrestled with his siblings growing up. He got the hang of it pretty quickly when the rough-housing started, but someone always got beaked in the nose whenever he was involved. The rest of us knew how to play hard without getting hurt or hurting anyone else.

    You're not born any of these things, but the differentiation is well under way by elementary school. That beaker is a doctor now.

  178. Interesting by stevenfuzz · · Score: 1

    I'm a Software Developer. I started programming when I was 11, so I guess I have 18 years experience (10 Professionally). Programming certainly uses the brain differently than the average non-programmer is every going to comprehend. I have worked with many fresh-out-of-College programmers, and most of them (not all of them), who hadn't started when they were younger, were way behind where I was freshman year of high-school. Many of my "I'm going to be a programmer" friends who started in College failed, miserably. I remember a good friend of mine, brilliant in Math, was just constantly frustrated like a one-armed man trying to learn to juggle. Somebody wake me up when I can take a 1 year Rocket Science course. Or, a 1 year MD program.

  179. Carbon / Credit Rule of Economics by Anonymous Coward · · Score: 0

    Let met teach everyone a fundamental carbon economy rule : If it uses more carbon it is promoted.

    Many people sitting behind their pc's trying to be codes will uses a shitload of energy

    Also every other job has been made easy to replace, but coders are still in short supply..

  180. Learn a new language, get a job. by Kingrames · · Score: 1

    "learn to code, get a job" is functionally identical to "Learn a new language, get a job." We call our programming languages languages because that's what they are. it's a new way to communicate.

    People who only know how to communicate in one language never really understand how easy it is to figure out how to solve translation problems. Learning a new language is incredibly easy and it's probably one of the most valuable tools that you can get as a human being. Why? Because communication is key to human advancement.

    It's true that learning how to code will make you a more valuable worker. But it's not the only way and it's not a fire and forget solution. If you don't learn how to code, and you don't learn another language, you're holding yourself back in ways you'll never be able to understand.

    --
    If you can read this, I forgot to post anonymously.
  181. As a Codeacademy subject... by Anonymous Coward · · Score: 0

    I decided to try the Codeacademy Code Year. Why? I lack the funds for college and I lack the motivation to choose a single career to follow. Sure, there are better teaching tools, but I am testing the waters with this. The other tools I tried were generally less suited for my style of learning (lots of simple steps until I catch on and take off with expanded concepts). I did HTML and JS in high school and I was among the best in the class. I want to relearn what I did so well in that class and see if I have the mindset for programming before I launch into more serious learning. Stepping stones to understanding and implementation.

    I agree that the tools Codeacademy provides are simple and not suited well to improvisation and efficiency. However, those who get the ideas and want to do more will be what the tech industry wants.

  182. Meh. by Anonymous Coward · · Score: 0

    Took 4 courses of java in the national university. Ask for a job and they say: "Ah You can take your courses and smoke them up. I want a certification in Java 6.2" *phone rings* excuse me... My IT crew just told me that JAVA 6.2.1 has been released and if you don't have an certification for JAVA 6.2.1 you are wasting my time.

    So they hang up all the courses online they want, they wast us money and time for nothing as employers want certifications of 5000 USD and always current.

  183. Not everyone can code by Anonymous Coward · · Score: 0

    Not everyone can code. I learned that when I tried to teach my wife to code. She has advanced degrees in economics from a top university and has a high level job, .....she got the idea, but was repelled by the minute logical details required to write a good program.

    Similarly I have tried to teach disadvantaged kids to code - about 1 in 10 gets it and has the mental discipline to follow through. The others don't have the ability or the interest to bother.

    Good luck Mayor Bloomberg.

    Developing complex software is difficult - and all the simple problems have now been coded and are available.

  184. Re:It's not something you do, it's something you a by ModernGeek · · Score: 1

    The experience of tinkering with other systems such as cars let you see the logic behind the way things work. After you started breaking into these types of systems, your mind started to enter a lower latent inhibition state. You started seeing things for what they are, not what they are perceived as. Young programmers normally build things with legos and start taking apart things around the house to see how they work. This marks the difference between a schoolyard engineer and a real engineer. You aren't the exception, you are the standard, you just may have came a little late to the game.

    --
    Sig: I stole this sig.
  185. Re:It's not something you do, it's something you a by kaizokuace · · Score: 1

    Yea, late to the game definitely. I mean, I have other experience behind me but I wish I learned what I am learning now a lot earlier.

    --
    Balderdash!
  186. Re:The last thing the world need is more bad coder by segfault_0 · · Score: 1

    I don't think you could even apply these categories and classifications yourself, let alone tell someone else how to. You may call someone a "5% coder" and I may say they are more like 50%. All of this is subjective, you can't deal with people this way.

    --

    I was crazy back when being crazy really meant something. (Charles Manson)
  187. Creepy Greeting by siriuskase · · Score: 1

    Hey! Let's get to know each other. What's your name? Type it with quotes around it like this "Ryan" and then press enter on your keyboard.

    That's exactly the kind of greeting that I warn children and other newbies not to respond to unless the site is thoroughly vetted.

    --
    If you must moderate, please moderate as irrelevent, not something bad, because I'm sure someone will find this interest
  188. HOWTO by Anonymous Coward · · Score: 0

    I figured some years ago how to get really good at almost anything. Here's my secret: do it all day, every day, for the rest of your life.

  189. Where's the Degree? by m1xram · · Score: 1

    Guess they're a bit clueless at CNN. Has anyone seen a Software Engineering job posting that didn't require a degree? I haven't and some require a Masters. Have even seen Electronic Tech jobs requiring a degree. Want a software job? Go to college, get good grades and then maybe, just maybe, you can get into a good software job. But I should tell you that the other Software Engineers I knew who had degrees were still having difficulties finding work. People like myself with decades of experience and no degree are pretty much out of luck.

  190. Re:It takes a lot longer by Anonymous Coward · · Score: 0

    I have not read _all_ 500 replies so far, but I'm surprised no one has pointed out the lesson that after about 10,000 hours of careful work, you get really good at something. You have to like it a lot, and have some reasonable ability in that direction. I know several people who are very smart (in some ways) but utterly clueless when it comes to computers.
    t