Slashdot Mirror


Computer Science Degrees Aren't Returning On Investment For Coders, Research Finds (theregister.co.uk)

According to a new survey, coders with a bachelor's degree in computer science only earn 3,000 British Pounds (BP) more a year than those who don't have one. The survey of 4,700 developers in the UK was conducted by Stack Overflow, a community site frequented by developers for answers to technical questions. The Register reports the findings: This is despite the average degree now costing 9,000 BP a year in tuition fees alone. Average student debt is now more than 50,000 BP, according the Institute of Fiscal Studies. The research found that the median salary of those who did not have higher education was 35,000 BP per year, while those who gained a bachelor's degree earned 38,000 BP and postgraduates took home 42,000 BP. It found that 48 per cent of developers with less than four years of professional experience currently hold a Computer Science-related undergraduate degree, while 49 per cent had completed an online course instead. The research also found that JavaScript developers were most in demand, with almost 27 per cent of jobs advertised on Stack Overflow now requiring this skill, followed by Java (22 per cent), Python (16 per cent), C# (15 per cent) and ReactJS (9 per cent).

395 comments

  1. Money this, money that... by Anonymous Coward · · Score: 0

    Degree this, percent that... Do you never get tired of the stupid fucking bullshit that's posted on this site 24/7?

    1. Re:Money this, money that... by Moblaster · · Score: 4, Funny

      I only get tired of explaining to traditionalist relatives who have engineering degrees why I'm called an "engineer" when I don't have an engineering degree. It's brutal. But not as nasty as the look I got from that damn chemist who took umbrage at my explanation of how I was creating biodiesel in my garage. My god, my nerve at being such an impudent auteur as to research the chemistry on the web and try it at home. The death state I got when I explained that any way to get energy into the reaction - heat, ultrasonic, microwave, catalytic assistance - made it more efficient... I'll never forget the evil eye cast upon me. I bite my thumb at that dude!

    2. Re:Money this, money that... by Pseudonym · · Score: 1

      Some one who had begun to read geometry with Euclid, when he had learnt the first theorem, asked Euclid, "What shall I get by learning these things?" Euclid called his slave and said, "Give him threepence, since he must make gain out of what he learns."

      - Serenus of Antinouplis

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    3. Re:Money this, money that... by Frosty+Piss · · Score: 4, Funny

      It probably IS hard to explain to relatives who have engineering degrees why you're called an "engineer" when you're not an engineer.

      --
      If you want news from today, you have to come back tomorrow.
    4. Re: Money this, money that... by Anonymous Coward · · Score: 0

      Engineer: (n) A person who designs, constructs and tests structures, materials or systems.

      Sure sounds like people who design, construct and test software systems are engineers. The profession isnâ(TM)t defined by some specific type of degree or certification.

    5. Re: Money this, money that... by Anonymous Coward · · Score: 0

      Oh oh tell me news - when one is expected to live 24/7 connected to his/her computer just to ensure it will keep interesting for the next sweat shop monkey coder job where he is going to compete with cheaper imported code monkeys ... now that should be an awesomeness of a career ... I guess western youngsters are just lazy stupid bums because they don't buy into this miraculous life ...

    6. Re:Money this, money that... by Anonymous Coward · · Score: 0

      This True Scotsman Scotch is on me, to go with your British-class poseur arrogance.

    7. Re:Money this, money that... by mrsquid0 · · Score: 0

      Unless you drive a train you are not an engineer if you do not have an engineering degree. Get over it.

      --
      Just because you are paranoid does not mean that no-one is out to get you.
    8. Re: Money this, money that... by mrsquid0 · · Score: 1

      Yes, it is. Most places require a degree and professional certification of some kind before you can call yourself an engineer. North Korea may be an exception.

      --
      Just because you are paranoid does not mean that no-one is out to get you.
    9. Re: Money this, money that... by Anonymous Coward · · Score: 0

      I for one hate being called a "software engineer". I find it belittling.

      Not everyone who writes software for a living is some unkempt, small minded dullard. Not all of us wasted 4+ years of university on vocational training. At least the software trade is willing to admit men of liberal education and broad interests. Rumor has it, there are even a few poets and historians among our number.

      Thank goodness, although I still write software all day, my title is now "Director" rather than "Engineer".

    10. Re:Money this, money that... by Anonymous Coward · · Score: 0

      What is a BP though? Some kind of scamcoin?

    11. Re: Money this, money that... by Anonymous Coward · · Score: 0

      Same

    12. Re: Money this, money that... by Anonymous Coward · · Score: 0

      Every first world nation is an exception to that rule, since the majority of engineers in those nations are not ring-wearing club members.

    13. Re: Money this, money that... by Anonymous Coward · · Score: 0

      I have my CCIE, does that count?

    14. Re: Money this, money that... by Anonymous Coward · · Score: 0

      Engineer has different meanings in different languages. A real "engineer" is a man who runs a steam engine and keeps it efficient and safe. He has no degree, but he wasn't allowed out of his apprenticeship until his master was sure he would be safe with everybody's lives. "Engineering is the art of doing for 10 shillings what any fool can do for a pound” is one of the best definitions of a modern engineer. Formal degrees are just one part of that.

      However, the main thing is that engineers work with known components and rules. Tolerances and compromises. Is that patch I've done to the boiler safe or should I tell the passengers we have to wait for a new engine. Will that bridge stand up or will I go to prison? Can that strut be reduced by 100g and still last for 30 years?

      Software is still in the dark ages where we can't have solid components and rules that we properly understand. Gödel's theorem says that, with small lucky exceptions, it always will be. Formal proofs may be useful but will likely never properly cover normal large systems in anything but a superficial way. Even if we do eventually to using solid formally proven code for many parts of our systems, we are nowhere near to having the solid rules and components needed for engineering. What developers do is a craft not a profession even though they need to start doing it more properly.

      This means that, if you call yourself a "software engineer" and you aren't working for NASA, the people who write the code for car brakes or something similar, all it proves is that you understand neither software nor engineering.

    15. Re:Money this, money that... by WolfgangVL · · Score: 1

      PE is a bought title. Your peers and co-workers suffer your input because you're the paid-for scapegoat.

      --
      You are being ripped off every second of every day, so that advertisers can help rip you off even more tomorrow.
    16. Re:Money this, money that... by Anonymous Coward · · Score: 0

      Tell them you're not responsible for the way the business guys tell themselves things work, you just have to do the implementation.

      If they don't give you sympathy in response to that, you're within rights to doubt their qualifications are meaningful. Out loud.

    17. Re: Money this, money that... by Anonymous Coward · · Score: 0

      Back when I went to school the degree for programmers was either Computer Science or Business Accounting, so mine is in Computer Science. I suppose I could go around referring to myself as a scientist but I prefer software architect.

    18. Re: Money this, money that... by Anonymous Coward · · Score: 0

      In many jurisdictions, if you aren't a licensed professional engineer, then you're not an engineer, and it is unlawful to call yourself one.

      To be honest, Dunning-Kruger effect applies here too. If you think following a recipe you found online to add lye to oil makes you an engineer, then you really don't know all you don't know.

    19. Re: Money this, money that... by KGIII · · Score: 1

      Boiler operators are also engineers. Steam engines were used for more than trains.

      --
      "So long and thanks for all the fish."
    20. Re:Money this, money that... by sinij · · Score: 3, Funny

      It probably IS hard to explain to relatives who have engineering degrees why you're called an "engineer" when you're not an engineer.

      Please, this is 2017. If someone chose to identify engineer-sexual, we don't question it.

    21. Re:Money this, money that... by sinij · · Score: 2

      Unless you actually do your job and check their work before you sign-off.

    22. Re: Money this, money that... by Anonymous Coward · · Score: 0

      "PE is a bought title. Your peers and co-workers suffer your input because you're the paid-for scapegoat."

      So says the man who can't pass the exam.

    23. Re:Money this, money that... by jellomizer · · Score: 2

      Engineer is a job. Not an academic title.
      Higher education is not a job training institution so for most professions you job title isn’t tied to your degree.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    24. Re: Money this, money that... by number6x · · Score: 1

      Those 'real' engineers usually had pretty cool boots. (Hot cinders required some major league protection.)

    25. Re: Money this, money that... by dcw3 · · Score: 1

      Thank goodness, although I still write software all day, my title is now "Director" rather than "Engineer

      Titles are a dime a dozen. I've been in management for fifteen years, but I'm still a software engineer, and so are you, even if you're not in that role anymore. It's a shame you "find it belittling", but that's on you.

      --
      Just another day in Paradise
    26. Re:Money this, money that... by lgw · · Score: 1

      It probably IS hard to explain to relatives who have engineering degrees why you're called an "engineer" when you're not an engineer.

      Those new-fangled train drivers who call themselves engineers - you're not a real engineer unless you roll your petard up to the castle gate!

      A friend of mine with a PhD complains that medical doctors "aren't real doctors". OK, sure, but they make a lot more. I may not be a "real engineer" , OK, but I make a lot more.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    27. Re: Money this, money that... by makerfixer · · Score: 1

      I had a guy call himself an engineer in his email signature without an ABET degree or PE license in my office with three PEâ(TM)s in management. It was: Not. A. Smart. Idea. Write ups and a serious dress down.

    28. Re: Money this, money that... by Anonymous Coward · · Score: 0

      In many jurisdictions, if you aren't a licensed professional engineer, then you're not an engineer, and it is unlawful to call yourself one.

      You made that up. It was here a few months back

    29. Re: Money this, money that... by Anonymous Coward · · Score: 0
    30. Re: Money this, money that... by Anonymous Coward · · Score: 0

      Just the retarded currency the British still use because they don't want nothing to do with the euro

    31. Re:Money this, money that... by synp71 · · Score: 1

      Engineers drive trains. If you don't drive a train, you're not an engineer.

    32. Re: Money this, money that... by K.+S.+Kyosuke · · Score: 1

      Here we go again. Not all the world is your lunatic part of the world that hijacks ancient common words to turn them into trademarks and protected designations and whatever.

      --
      Ezekiel 23:20
    33. Re:Money this, money that... by K.+S.+Kyosuke · · Score: 1

      Well, they're physicians. Many languages apparently have a distinct word for healers, with "doctor" being more of a colloquialism.

      --
      Ezekiel 23:20
    34. Re: Money this, money that... by K.+S.+Kyosuke · · Score: 1

      Translated to common speech: gatekeeping and pretentiousness are alive and well!

      --
      Ezekiel 23:20
    35. Re:Money this, money that... by Anonymous Coward · · Score: 0

      Engineers record albums. If you don't record albums, you're not an engineer.

    36. Re: Money this, money that... by makerfixer · · Score: 1

      In the life-safety industry, yes! Unless the fireproofing on your building and alarm systems arenâ(TM)t that important in a regional hospital. Read up on Engineering disasters and how they happened. A good majority in construction are some salesman or designer overriding their specs to do what they âoeknowâ is right while shaking their heads at the no-nothing PE they were required to ask For permission to go off spec. Representing yourself as one and making those decisions letting people think you are acting professionally is disgusting.

    37. Re:Money this, money that... by lgw · · Score: 1

      English did as well - the majority of those who treated the wounded were just people who knew how to keep a blade sharp or saw through a bone very quickly. "Doctor" was reserved, appropriately, for learned scholars who were actually trying to advance the art.

      --
      Socialism: a lie told by totalitarians and believed by fools.
  2. Makes sense by Jason1729 · · Score: 4, Insightful

    Computer Science degrees aren't supposed to lead to jobs as "coders". That's like saying someone with a degree in mechanical engineering aren't getting a good return on their investment in the degree when they get a job doing oil changes.

    You can learn coding in a couple of days. Computer science is something different.

    1. Re: Makes sense by Anonymous Coward · · Score: 0

      Exactly. "coder" is an entry level position and is not computer science or engineering. You don't go to college to be a coder

    2. Re:Makes sense by Anonymous Coward · · Score: 0

      There are college degrees in software engineering. What if computer science was switched out for software engineering in the article?

    3. Re:Makes sense by Anonymous Coward · · Score: 3, Informative

      True, but these days people have largely forgotten the actual purpose of university and treat it more like a factory for churning out wage slaves. You really shouldn't need a tertiary degree for a lot of jobs. Hell for some jobs you'd be better prepared if you left half way through secondary school and did an apprenticeship. But I guess when jobs are scarce and people look down on the "uneducated" then it makes sense that people are spending longer and longer in school and not getting proportional benefit.

      On the plus side Uni is actually rather fun. You can study irrelevant but enjoyable subjects, get to know people and do a bit of growing up, so even a bad degree is not without its benefits.

    4. Re:Makes sense by Anonymous Coward · · Score: 0

      College is a racket that became a toll gate between normal working people and normal jobs without any benefit other than student loans. And it rose up in proportion to student loans giving people credit where they can mortgage their future on the largely false promise of higher pay.

      Fuck your irrelevant but enjoyable subjects and your bit of Wonder Years growing up right in the ass, like it's been doing to everyone else. The benefits are wasted years and wage slaving and a broken system.

    5. Re:Makes sense by Anonymous Coward · · Score: 0

      And getting that "something different" costs a small fortune and you end up writing code anyways.

    6. Re:Makes sense by 0100010001010011 · · Score: 1

      CS : Software Engineering : Coders :: Physics : Mechanical Engineering : Engineering Technologists.

      Having more head chefs in the kitchen doesn't get the food out faster.

    7. Re: Makes sense by Anonymous Coward · · Score: 0

      That is exactly right, engineering is a diverse profession, and yet Silicon Valley CEOs are essentially saying âget a CS degree! Code or die!â(TM), to the point of trying to hijack the entire countryâ(TM)s cirriculum. Makes one question their true motivations, huh? ;) I personally think itâ(TM)s at least partially in response to the high tech charter scam failing, and people beginning to see through the âa 4 year degree is now a high school diplomaâ(TM) payolla bullshit coming from our government and universities. You are absolutely correct: people, and subsequently their professions, are NOT that one dimensional. I suppose yiu coukd throw the H1-B scam in there too, if ine wanted to be contrary.

    8. Re: Makes sense by Anonymous Coward · · Score: 0

      PS - I canâ(TM)t help but notice it is software introducing typos in this thread, not the posters. More food for thought, methinks.

    9. Re: Makes sense by Anonymous Coward · · Score: 0

      Sounds like you'd really love for the university system to completely fail and all universities to close down. Be careful what you wish for.

    10. Re:Makes sense by Darinbob · · Score: 1

      Long term matters. Do you want that stupid entry level job for the next 40 years? I suspect most people want to be promoted, lead teams, and especially be able to design stuff and work on new projects. That is much more likely to happen with a degree; CS or EE degree helps a lot, but any degree will help there. The field is already chock full of people who can just barely code, and have no clue whatsoever why their algorithm takes days to run even though they're using all the latest fashions in coding.

    11. Re:Makes sense by srmalloy · · Score: 1

      That's like saying someone with a degree in mechanical engineering aren't getting a good return on their investment in the degree when they get a job doing oil changes.

      More like getting a job as a technical draftsman or a CNC milling machine operator, but the intent of your analogy is good.

    12. Re:Makes sense by NicknameUnavailable · · Score: 1

      You can learn coding in a couple of days.

      No, you absolutely can not. It takes decades to become a competent programmer. You might be able to learn a handful of core abstractions within a couple of days, you can only learn how to make scalable real-world systems on a budget/time-constraint with arbitrary levels of complexity of decades of trial and error. CS degree holders actually tend to be fairly shit at that because they have the complex side with none of the underlying understanding of why you do or do not do particular things in a given situation. Hell, most of them are taught in Java and they don't even understand why that's bad.

    13. Re:Makes sense by Anonymous Coward · · Score: 3, Interesting

      Blame HR departments and anyone responsible for hiring.

      They all wanted an easy way to trim the hundreds of resumes they received for a job posting down to a handful. So the first thing they did was start making it necessary for a college or university education for EVERY damn job out there. No college....resume went into the garbage.

      Luckily I'm on the downward slope towards retirement because I'm very certain that within the next 10 years, you are going to see those same people in charge of hiring raise the bar to a Masters degree at minimum....again for EVERY damn job out there. Got a college degree but not a masters? Ooops...too bad...go back to school and try again.

    14. Re:Makes sense by El_Muerte_TDS · · Score: 1

      You can learn to write sentences in a couple of days. Writing a book is something else.

      There are a lot of people with programming jobs who are highly overpaid, they can only write sentences but not a book.

    15. Re:Makes sense by Anonymous Coward · · Score: 0

      without any benefit other than student loans

      Now I feel kind-of ripped off for working my way through college instead of experiencing the joys of going into debt.

    16. Re:Makes sense by Maxo-Texas · · Score: 2

      Bachelor's degrees in computer science are absolutely supposed to lead to jobs as coders. But not as "code monkeys".

      Masters and Doctorates lead to jobs as actual Computer Scientists.

      A 4 year degree teaches you theory, teaches you to think rigorously (mostly the math), makes you well rounded (english, government, history), gives you good written and verbal communication skills (english classes), and gives you a good base in math- which you may never use (in which case it will rot), gives you better design theory, gives you a wider range of experience.

      Compare that to someone who spends a couple days learning a single language in a single setting and writes a program.

      I have a bachelor's degree, in Science-- Computer Science. In my case it paid off well- retired at 51. Many 6 figure income years. And it was dirt cheap for me- about $4,000 out of pocket (about $9,000 with $5,000 reimbursed by my job).

      School is TOO expensive for the kids. We shouldn't be charging them so much.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    17. Re:Makes sense by lindseyp · · Score: 2

      I'd think that very few software engineering graduates are coders.

      Software engineering teaches a very broad base of various coding styles, computer science, and tops it off with a lot of software design methodology.

      A software engineer is training to be an architect, not a builder. An automotive engineer (design), not a machinist.

      --
      j'ai découvert une démonstration vraiment admirable (de ce théorème général) que cette si
    18. Re:Makes sense by Anonymous Coward · · Score: 1

      I have a degree in CS. It gave me nothing useful that I couldn't research on the Internet during my junior years. The only extra I got out of it was the proofs of a bunch of these that I forgot roughly 2 weeks after the exams and have not needed ever since.

    19. Re:Makes sense by Anonymous Coward · · Score: 0

      You should. Imagine if you could have put that money into a real investment instead of a cultish piece of paper.

    20. Re: Makes sense by KGIII · · Score: 2

      It may also be due to the selection bias. CS degree holders that are good might not be on StackOverflow and thus not answering the survey while simultaneously earning more money. They are ore-selecting based on people needing additional help or people with enough free time to give their time away in exchange for Internet Points.

      More skilled people have other things to do, don't need the help, and probably make more money. Basing any major choices on the results from a self-selected survey is not a good idea. Additionally, there are people like me who will get bored and fill your survey in with bullshit for the sole reason of demonstrating why self-selection surveys are a bad idea and not very scientific. I'm not really a middle aged housewife making $12/hour at Starbucks, but if you present a survey to me, I just might pretend to be.

      --
      "So long and thanks for all the fish."
    21. Re:Makes sense by johannesg · · Score: 5, Insightful

      No, you _cannot_ learn coding in a couple of days - why does drivel like this get +5?

      You can maybe understand a few of the absolute bottom layer basics in a few days, but that doesn't qualify you for a job as a programmer yet - that takes years of effort and experience.

      Who are you, Jason1729? Some manager type who really looks down on his employees? An academic who really believes coding is something you can learn in a few days, but of course you never bothered because it is for those of lower education?

    22. Re:Makes sense by Ol+Olsoc · · Score: 1

      True, but these days people have largely forgotten the actual purpose of university and treat it more like a factory for churning out wage slaves. You really shouldn't need a tertiary degree for a lot of jobs. Hell for some jobs you'd be better prepared if you left half way through secondary school and did an apprenticeship.

      I was talking with a professor of mine about how his graduates were all woefully unprepared when they applied for jobs with us. He agreed, then told me that it was not designed to prepare graduates for employment.

      I then asked if the students were informed of that little fact. No answer

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
    23. Re: Makes sense by Ol+Olsoc · · Score: 1

      Sounds like you'd really love for the university system to completely fail and all universities to close down. Be careful what you wish for.

      What is needed is for the University system to align itself with reality. There needs to be a distinction between majors that prepare you to get employment, and ones that essentially are you giving your opinion, and agreement with the professor assures you of a 4.0.

      There needs to be a way of allowing students to help pay for their education. I am always amazed at the young people working at the shore. Almost all from outside the US. American college students used to hold most of those jobs, but they cannot since most Universities start fall term before the summer season is over. This isn't even a disparagement of the young people working there now, they've all been very nice.

      Point is, it's a terribly broken system when a person can come out of college with a degree in Philosophy or Women's Studies, over a hundred thousand dollars in debt, and having not one useful thing learned that will qualify them for a job, and in some cases a negative at hiring time for that job at McDonald's. That opinion everyone stood and clapped for you in class is worthless.

      As well, the campus environment has become pretty toxic for some people. I've been recommending on-line degrees in viable fields to people for several years now.

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
    24. Re:Makes sense by Anonymous Coward · · Score: 0

      I'm not so sure that a degree teaches much any more. I did a whole variety of stuff on mine, a fair amount of Pascal and BCPL on Dec10 but we did Functional Programming and Assembler, and built CPUs and so on, and some fairly tough mathematics and analytical stuff. Proofs and so on. There seems to be much less of that nowadays and too much pretty stuff.

    25. Re: Makes sense by jellomizer · · Score: 1

      While someone with a CS degree may start off as a coder the same position as someone without one. The education (if you chose to apply it) can allow you to get out of coding to development, and architecture where each new level allows you to have more control of what is done and how to do it.
      While the person without the degree will have a much steeper threshold for promotion. Although they may be an excellent coder they will have funny gaps in their skills that makes advancement difficult.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    26. Re:Makes sense by bravecanadian · · Score: 2

      Bachelor's degrees in computer science are absolutely supposed to lead to jobs as coders. But not as "code monkeys".

      Not in real computer science programs. Strangely enough, computer science programs are supposed to teach you computer science.

    27. Re:Makes sense by Anonymous Coward · · Score: 0

      Sorry dude but this is just ignoring reality. 90% of those majoring in CS are doing it to go into development careers.

    28. Re:Makes sense by computational+super · · Score: 1

      No, you absolutely can not. It takes decades to become a competent programmer.

      Yeah, that sentiment, modded up to a +5, scares the hell out of me. That's how you end up with Equifax. Coding is all there is.

      --
      Proud neuron in the Slashdot hivemind since 2002.
    29. Re:Makes sense by computational+super · · Score: 2

      Slashdot is surprisingly anti-programmer, but seeing this modded up is something even for slashdot. Even the developer boot camp people never suggested you could learn to code in a couple of days.

      --
      Proud neuron in the Slashdot hivemind since 2002.
    30. Re:Makes sense by Anonymous Coward · · Score: 0

      Unfortunately, many of the ones with no clue about their lousy algorithm (they're using the latest framework - woo hoo) ARE the recent CS grads. The ones with any clue about the real world performance implications are often those with real world experience - who often DIDN'T get the vaunted CS degree.

    31. Re:Makes sense by mark-t · · Score: 2

      Even a so-called "entry level job" can pay quite fairly... as long as the salary keeps pace with the rise in cost of living, once you've found something you love to do, what's the problem?

    32. Re:Makes sense by Gr8Apes · · Score: 1

      You'd think that. The reality is, most coming out of schools for the past 15 years know Java and JS, or, for the really unfortunately ones, C# and JS. They know next to nothing about how to design and build real solutions, because that means you know more than some fancy academic software design methodology, which they also often don't understand. So most of them, if they're good for anything at all, is being a coder. Maybe after a few years they'll be promotable, but many aren't.

      --
      The cesspool just got a check and balance.
    33. Re:Makes sense by geekmux · · Score: 4, Insightful

      You can learn coding in a couple of days. Computer science is something different.

      Becoming proficient at anything takes time and dedication to gain the experience necessary in order to actually provide value.

      Otherwise, you're just another idiot who assumes they know what they're doing after hacking away at it for a couple of days.

    34. Re: Makes sense by Anonymous Coward · · Score: 0

      We need to restore college to what it used to be: a parent-sponsored orgy of drinking, dancing, and fornication!

    35. Re:Makes sense by datavirtue · · Score: 1

      ...and then they read blogs and articles and apply their vast misunderstanding with their colleagues on software projects where the business has no idea how clueless the developers are; all the while they operate under limp-wristed dev managers who think they have to let people run wild in order to keep them happy. Code reviews are conducted by the architects but the "solutions" are usually so fucked up that correcting them will amount to a lot of work, missed deadlines, and basically a full dress down of the snow-flake developer. In the end it goes to production and people lie and throw others under the bus to obscure the true nature of the collection of monumental fuck-ups and those responsible. ....and that is at a nice company with a good culture.

      --
      I object to power without constructive purpose. --Spock
    36. Re: Makes sense by Hognoxious · · Score: 1

      In fact, forget the dancing.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    37. Re:Makes sense by Hognoxious · · Score: 1

      I'm very certain that within the next 10 years, you are going to see those same people in charge of hiring raise the bar to a Masters degree at minimum

      Red Queen effect. It's a known thing.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    38. Re: Makes sense by Anonymous Coward · · Score: 0

      TLDR: Your employees are shit because they're not college graduates and they often lack the interpersonal skills needed for projects of extended duration.

      I have a Philosophy degree. ("hundreds of thousands of dollars in debt"? You don't know what you're talking about on that one, Ol.) My first job (in 1992) was at a large communications company with some sort of "blahblah technician" title. I got the job by taking a test to show engineering ability. The test include some basic mathematics operations in binary and hex. I took the test with a group of about 10 other competitors, most of whom had extensive experience in the industry. Speaking with the industry veterans after the tests, I heard the complaint "I never have to use binary or hex math on the job. That's ridiculous." I became employed with the company, and, well, playing with numbers on a computer is essentially what the job was. I used all sorts of math to do a few sorts of things. My philosophy education and degree prepared me for that job better than professional experience prepared the others. I could be an outlier, but we would need to commission a study for that.

      That company knew that by finishing a college degree, you've proven that you can take steps on your own to complete a multi-year task. No matter what the degree, you've gone through the BS to get a BS (or whatever) and you've completed it successfully after years of research, writing, and various forms of professional communication. This is the reality: college will prepare you to work with others on complex tasks, to be able to propose good ideas, and to be able to defend those ideas or incorporate other points of view to produce workable solutions. Getting a college degree means you were able to able to do that over course of multiple years, and you've not only gone through it, but you've gone through it successfully enough that the people around you have lauded you for it. That opinion that everyone stood and clapped for me in class? Evidently, it's worth over $150K/year.

      ("Agreement with the professor" is just a bizarre opinion. The professor is not the text. If I'm right, and the professor is wrong, then I'll still get the 4.0 when I contest that with the faculty.)

      College should absolutely not be about preparing people for the workforce. College already produces people who make better employees than someone with the same "real world" experience. What is NEEDED is for business to align itself with reality. Your employees are shit because they're not college graduates and they often lack the interpersonal skills needed for projects of extended duration.

    39. Re:Makes sense by Anonymous Coward · · Score: 0

      Sadly I know at least one software engineer graduate who sponged off his team mates, didn't do the work, graduated with no idea how to actually code, and then got hired at a McDonalds while he tried to muddle through a Coding Boot Camp. AFAIK he's still working fast food.

    40. Re: Makes sense by Anonymous Coward · · Score: 0

      Use the preview function, you retread.

    41. Re: Makes sense by Anonymous Coward · · Score: 0

      Spoken like a true Philosophy major. It's telling when you have to spend three paragraphs explaining why your degree really does make you better than the non-star bellies.

    42. Re: Makes sense by Ol+Olsoc · · Score: 1

      TLDR: Your employees are shit because they're not college graduates and they often lack the interpersonal skills needed for projects of extended duration.

      My employees? Not quite certain where I was talking about my employees.

      I have a Philosophy degree. ("hundreds of thousands of dollars in debt"? You don't know what you're talking about on that one, Ol.)

      Just so you know, http://blog.readyforzero.com/h... , https://www.theguardian.com/mo... , and there are more that you can google. 100K is higher than the average debt, but as a philosophy major, surely you can parse my post, and not pick out of it that I was saying everyone was 100,000 dollars in debt? Notice the difference between the apparent belief on your part that I said that everyone graduates with 100 K in debt, with the more accurate reading - based on teh exact words I wrote: "it's a terribly broken system when a person can come out of college with a degree in Philosophy or Women's Studies, over a hundred thousand dollars in debt,

      I'll leave it up to you to expound on the various meanings of can. One does not have to delve into Clintonesque definitions of "is" to understand that "can" is more related to possibilities, or perhaps a metal device to hold matter in. But if I was not clear to you, I used the word "can" in the manner of "it is possible" or "might" when "can is used as an auxiliary verb.

      College should absolutely not be about preparing people for the workforce.

      Then they should work very hard and diligently to disabuse almost everyone's notion that they are.

      College already produces people who make better employees than someone with the same "real world" experience.

      Oh my sphincter! Sorry, This is hilarious, As a philosophy major, if you even had the experience of graduates in completely unrealated fields being superior employees based on them having spent 4 years in college, studying anythiing at all, versus a person without who has actually made a living already, by actually doing the needed work, they must be teaching some hella good stuff in philosophy.

      What is NEEDED is for business to align itself with reality. Your employees are shit because they're not college graduates and they often lack the interpersonal skills needed for projects of extended duration.

      Well first, as a philosophy major, you are using a lot of straw man arguments. And unless you are remarkably different than the philosophy majors I am personally familiar with, interpersonal skills are pretty far down the list of their qualifications. I'll enjoy an afternoon of chatting and no doubt, but not one would work for me, they have a certain ability to not be very motivated, rather intractable in their opinion, and enjoy disagreeing with you and chatting for the afternoon rather than getting work done.

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
    43. Re:Makes sense by Maxo-Texas · · Score: 1

      yea right. A bachelors degree in computer science is equivalent to a bachelors degree in chemistry or psychology.

      It's the first 3-5 years of your real degree if you want to work as a computer scientist.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    44. Re:Makes sense by Maxo-Texas · · Score: 1

      That was what my degree was like. It was damn hard.

      Never built CPU's but we did work with breadboards and we did programming like yours (vax macro assembly language at my school). Implemented our own database with simple SQL statements. Implemented our own compiler from a skeleton.

      If you wanted to be a computer scientist- you got a masters or better yet a doctorate.

      Bachelors degree was just to get you a solid programming job (not a code monkey).

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    45. Re:Makes sense by Anonymous Coward · · Score: 0

      Honestly? I would trade all the promotions in the world for a job where I was allowed to just get on with it safe in the knowledge that I wasn't going to have to do another job application ever again. Hell I would take a pay cut and work twice as hard for that sort of job security!

      (Also I quite like programming, almost as much as I quietly loathe the management crap I find myself increasingly railroaded into by "optional" - which is another name for mandatory unless you want to get shown the door - career "advancement")

    46. Re:Makes sense by Anonymous Coward · · Score: 0

      Mod this up many times.

    47. Re:Makes sense by Anonymous Coward · · Score: 0

      As my teacher said, knowledge is a worthless thing to teach, it can be easily acquired from the Internet, and quickly forgotten. The University's goal is to teach you how to teach yourself, and the degree represents your ability to understand and solve problems. Outside of 100 level courses, most were either team based projects or open internet for tests. Most classes tested your ability to solve problems, work as a team, or communicate to the class. Rarely was my knowledge tested.

    48. Re:Makes sense by Bengie · · Score: 1

      In "programming" few masters are experts and few experts are masters. In psychology, advanced knowledge and advanced reasoning are inversely related. You either know a lot and understand little or know little and understand a lot.

      People with the strongest abstract reasoning skills have learned how to quickly forget. Turns out that the act of learning requires a lot of working memory. The more you know, the more clogged your working memory becomes because everything you see triggers a memory that keeps your working memory saturated. The less you remember, the faster you learn and the more complex ideas you can learn. Spatial memory uses a complete different part of your memory. You can remember a lot of abstract concepts without negatively affecting your working memory. If you focus on learning abstract concepts and not facts, you will learn faster.

      Most people peak in abstract reasoning in their late teens and plummet in their 30s. This seems to be caused from lots of experience that causes the person to learn more. As the person learns more, their abstract reasoning gets used less and less while they continue to grow their knowledge and use their memory. At some point their abstract reasoning hits an inflection point veering down. People who do no focus on knowledge, but instead focus on understanding do not have this issue because they don't gain as much knowledge. They instead increase their abstract reasoning, which allows them to quickly learn new things and just as quickly forget them.

      This is why experience is such a worthless metric in a problem domain that requires much abstract reasoning.

      An expert is great for "solving" (remembering solutions) old problems, a master is great as solving new problems. Depending on what problems you have, choose wisely. Then you have the whole issue that in tech, specific knowledge has a half-life of 3-5 years. Worthless by the time you become an expert in it, unless you have a niche position for some legacy system.

    49. Re:Makes sense by Anonymous Coward · · Score: 0

      C# Java? Are you crazy?

    50. Re:Makes sense by Anonymous Coward · · Score: 0

      JS? Are you crazy?

  3. Degree by ebonum · · Score: 0

    I'll take a Biology, Physics, double-E, etc major who taught him/her self to code over a CS major any day of the week.

    Demonstrate that you are smart. Then demonstrate the ability to learn and adapt.

    1. Re:Degree by 0xdeadbeef · · Score: 3, Insightful

      Why? You listed them in increasing order of incompetence. The only people who write shittier code than EEs are mathematicians.

    2. Re: Degree by Anonymous Coward · · Score: 0

      Yeah. I've had my share of MechE's that "code" in just awful, stupid ways, too.

    3. Re:Degree by Anonymous Coward · · Score: 0

      I ended up going the EE route, even getting a PhD, though the PhD was a design involving programming. Now I do programming most days as a software engineer. In some ways, a lot of the courses I took almost seem a waste, yet it is hard to really regret them, though I really doubt I'll ever be on a program involving laser cooling.

      The biggest downside to the lack of a CS degree is you might just learn how to do something, without really learning the best methods. For instance, you might initially make perfectly reliable code that is harder to follow than it needs to be. Of course, I'm not convinced that having a CS degree changes that that much. It just takes time and continuous learning and experience.

      The real problem with software engineering is finding a job that is both rewarding and pays well, that doesn't want you to spend tons of overtime, usually unpaid. This year I got a lot accomplished, though I suspect my lead will sweep most of it under the rug early next year after I change jobs, if for no other reason to make his work look better in comparison. I suspect I could find a job where my time was better valued, but again, most of them outside the defense company I'm in want a lot of hours. One I interviewed for showed me this horrible eye bleeding labview code that must have spanned many pages of block diagram in one Virtual Instrument. I felt an immediate instinct to refactor it, but that is not what their management wanted. They wanted small patches at best. It worked, and they didn't care.

      Out of curiosity, how many software engineers have a reasonably rewarding stress free job where quality matters without having to volunteer a bunch of overtime? Also, where are you working?

    4. Re:Degree by Pseudonym · · Score: 1

      ^ Person who has never had to maintain software written by a biologist detected.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    5. Re:Degree by rfengr · · Score: 1

      Well CS people write shitty embedded and DSP code and, and EE write shitty all-other code.

    6. Re:Degree by Anonymous Coward · · Score: 0

      I'll take a Biology, Physics, double-E, etc major who taught him/her self to code over a CS major any day of the week.

      Demonstrate that you are smart. Then demonstrate the ability to learn and adapt.

      As a first order, that line is correct.

      More specifically, I'd want to hire people that see software as a tool, rather than as a role. It's a pretty extreme difference in behavior, and that difference matters when you get to testing/fixing issues. The person that tries to understand the domain tends to be much faster. Some CS people try... but some throw some "not my area" BS that makes them beyond a certain point.

      Basically, if you see yourself as a "Software Engineer," I don't want you. If you're an engineer (or whatever else) that solves real problems using software, you have value.

    7. Re:Degree by Anonymous Coward · · Score: 1

      Enjoy dealing with highly coupled unmaintainable spaghetti code.

      Sincerely,

      CS Major who makes a good living refactoring the garbage put out by self-taught coders.

    8. Re:Degree by Anonymous Coward · · Score: 0

      Does the CS guy or EE write verilog for FPGAs?

    9. Re:Degree by Anonymous Coward · · Score: 0

      No, that's a job for 6 Indians or 5 Chinese that get paid less together than one of you.

    10. Re:Degree by Obfuscant · · Score: 1

      ^ Person who has never had to maintain software written by a biologist detected.

      I've had to maintain code written by physical scientists and I can attest to the fact that they write code using empirical testing and not thinking about what they are doing.

      For example, one math guy wrote a bunch of code in Pascal that I had to translate to FORTRAN. After doing that, I noticed that he wasn't initializing any of his arrays, and that starting with all-zero entries resulted in all-zero answers. Well, he said, he didn't initialize them to anything because the random values they started with worked well. Can anyone guess one difference between the Pascal compiler he used and standard FORTRAN?

      A highly respected physical scientist (and a bunch of his grad students) wrote a large program in FORTRAN, and when I ran it it crashed horribly while reading the input parameters from a file. It was THEIR EXAMPLE input. It boiled down to a failure to properly deal with a line that had no colon as a label:value separator and returned a -1 index for the "colon", which their version of FORTRAN ignored in a memory copy, but my version of FORTRAN did not. Can you think of what happens when you try to copy memory using a function that accepts unsigned input when you send it a -1 for the starting address?

      Computer scientists are not where coders come from. Why would they get ANY extra money over anyone else when it comes to something they didn't really learn to do in college anyway?

    11. Re:Degree by TsuruchiBrian · · Score: 1

      First of all being an X major is not the same as completing a degree in X.

      Secondly completing a degree in X at some shitty for-profit scam school is not the same as completing a degree in X at a reputable university.

      Thirdly, what do you think computer science is? I'll give you a hint, it's not coding for the same reason electrical engineering isn't soldering.

    12. Re: Degree by Anonymous Coward · · Score: 0

      In my experience the people who went around refactoring everything are the same people who were the most inflexible and pain in the ass employees.

      Sincerely,
      HS graduate that had several PhDs and "Masters" degree folks working for him.

    13. Re: Degree by Njorthbiatr · · Score: 1

      That's because they're taught MatLab is the end all of everything you'll ever need. It's the closest thing to programming that they know and MatLab has just enough functionality to hobble along as a general purpose language (it might be turing complete?).

    14. Re:Degree by Anonymous Coward · · Score: 0

      I'll actually give the biologist the higher grade here. Dear lord, the ability to mistake memorization and complexity for useful code among them is *astounding*. Do you have any idea how much absolutely *fraudulent* crap data is in the Human Genome Project, pretending to be valid squences?

      I swear Leonart Pottering's previous life was as a geneticist.

    15. Re: Degree by Anonymous Coward · · Score: 0

      So just a question. Why the fuck would you be translating a shitty program from Pascal to FORTRAN? I mean if the code was so bad and didn't initialize any variables then why not write your own. I have a CS degree and I'm pretty sure they didn't teach me how to write java code that would compile fine for C#. I guess I missed that class you must of taken.

    16. Re: Degree by mikael · · Score: 1

      Probably because it was some complex mathematics/statistics/image processing algorithm that had to be converted.

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    17. Re:Degree by Anonymous Coward · · Score: 1

      The only people who write shittier code than EEs are mathematicians.

      Anecdotally, many years ago, when I was in college, two friends of mine -- an EE major and a Math/CompSci major like me -- convinced me to join them in taking an upper-division, suitable for graduate work EE course titled 'Microprocessors'. It was essentially assembly-language programming at the hardware level -- controlling SIO and PIO chips, for example. At the first exam, half the class couldn't read a microprocessor timing diagram to answer the question 'If an address is put on the address bus for a read, how many clock cycles later does the data become valid?' The three of us got the three highest scores in the class on the exam, with my EE-major friend scoring only 55 on the test. This pattern persisted through the entire semester, with the professor having to give the three of us 'A's, then grade the rest of the class on a curve, so he wouldn't have to flunk half a class of upperclassmen and graduate EE students because of two undergraduate math majors... while the EE department was undergoing reaccreditation. I later found out that the course had been reclassified as an undergraduate-level class.

    18. Re: Degree by Anonymous Coward · · Score: 0

      Sounds like genuinely interesting stuff. Please post about the hgp. Thanks!

    19. Re: Degree by prefec2 · · Score: 1

      They all write horrible code which does its job but become incomprehensible after month (including the author).

    20. Re: Degree by prefec2 · · Score: 1

      No the issue is that they do not know what architecture is and they have limited skills in modularization. Yes EE people are better than natural scientists, but still they did not get the complete set of pattern and processes necessary to be good in that particular department.

    21. Re: Degree by prefec2 · · Score: 2

      No this is not the case. Most people write shitty code, because they are lazy, fall victim to not invented here etc. However, natural scientists are not trained in modularization and abstraction. They usually are taught analysis and less discrete math. In EE things are a little different, but they still have limited knowledge of programming pattern and modularization beyond their duplication of structures.

    22. Re:Degree by gweihir · · Score: 1

      Good luck with that if your code needs to be maintained, be secure or needs to have good performance. Sure, a lot of CS grads are not engineers and do not understand engineering. But to find really good coders, they need to be both engineers (which is a state of mind) and CS grads. The non-CS grads stay limited in what they can do. The non-engineer CS grads can do, but the engineering may be really bad.

      Hence you need CS grads for anything more advanced, but you need to select pretty carefully which CS grads. Or in other words, the degree is necessary but not sufficient. If you just look for people with that CS degree, you will get a lot of incompetent people. But people without that CS degree are worse, unless you coding tasks are very simple and the main problem is understanding the problem space. In that case, hire people with a degree directly relevant to the problem space. But do not even consider connecting the software they produce to the Internet.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    23. Re:Degree by gweihir · · Score: 2

      Oh, yes. Mathematicians are the worst. Sure, their code will usually do what it should, but it will be bad in any other respect. Quite often you cannot even read it and forget about trying to modify it. That makes it unusable for anything besides run-once-then-throw-away projects.

      There are exceptions though. I personally know one mathematician that can code really well. His problem was that his last employer did not allow him to code (a large insurance), because they made extremely bad experiences with mathematicians coding.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    24. Re: Degree by LordWabbit2 · · Score: 1

      So fucking true, bank i worked for hired a mathematician to help with creating some complex algorithms, and to be honest, we did need him for that. At first we let him implement them, but after a while we just told him to give us the algorithm and we would do the coding around it. Which worked well for a while, until he decided to go to a year long prayer thing in the US? Never did figure out how someone like that got stuck on religion?

      --
      There are three kinds of falsehood: the first is a 'fib,' the second is a downright lie, and the third is statistics.
    25. Re: Degree by KGIII · · Score: 1

      That is remarkably true.

      I'm a mathematician, albeit retired. Trust me, you do not want me to program. With a very loose definition, I can program. In fact, I've done a whole lot of programming, all of it horrible.

      Eventually, I was able to hire competent programmers, skilled professionals, and those sorry bastards were forced to work on my code base. It was so horrible that they rewrote the entire thing and, quite literally, forbade me from pushing any of my code to production.

      Me, the boss and owner, was told I could not push my code into their production version. Their threat was that they'd quit if I continued doing so. Programmers had much more leverage back then. Regardless, I listened to them because that's why I'd hired them. In the future, I'd do a mockup of what I wanted done and they'd implement it for me. It worked out well.

      --
      "So long and thanks for all the fish."
    26. Re:Degree by Anonymous Coward · · Score: 1

      You get incompetents in any population. And talents. Not everyone needs a CS degree to be a decent developer. If you'd rather have a fresh CS grad over a non-degree-holding architect/developer with 10 years experience, feel free - we'll hire the experienced guy.

    27. Re:Degree by Anonymous+Cow+Ward · · Score: 1

      And you know this about the HGP how, exactly?

      --
      Examine even your most deeply held beliefs. Nobody is always right.
    28. Re:Degree by swilver · · Score: 1

      It's great when you can put people into boxes and then apply all your prejudices. What did you study, so I can file you into the proper box as well?

    29. Re: Degree by jeff4747 · · Score: 1

      However, natural scientists are not trained in modularization and abstraction.

      Depends on the science.

      For example, biology is modularization (these processes run in this organ), and the large gaps in what we know means you have to use abstraction (something triggers this process as needed, we aren't studying that so we'll just pretend there's some sort of regulator).

    30. Re: Degree by prefec2 · · Score: 1

      This a different kind of structure. I have analyzed tonnes of biological chemical models, grid based ocean models, and other software written by scientists. They are very good in handling complex structures in their head, but are unable to modularize, as this is done in normal software development.

    31. Re: Degree by jeff4747 · · Score: 1

      That's because they're still being biologists.

      But if they wanted to actually become software developers, the modularization and abstraction they learned in biology can help in the transition.

    32. Re: Degree by prefec2 · · Score: 1

      In theory yes, but I have not seen one in industry nor academia who actually made the extra effort to learn some basic software engineering concepts. Although I did not encounter biologists in industry programming jobs only physicists , chemists and geologists oh and mathematicians, they ate the least trainable, as CS is just applied math ;-)

    33. Re: Degree by jeff4747 · · Score: 1

      And I haven't seen any software developers make the extra effort to learn the real science behind what the academics are doing.

      Again, the key difference is the transition to the new field, not staying in your old field and bleeding a bit into another.

  4. Code monkeys don't need degrees by Anonymous Coward · · Score: 0

    And for the most part, they're stuck working long hours on full stack crap.

    Get a degree and you open doors towards more advanced paths. Of course, you can do that without a degree, but you can do pretty much anything without a degree if you're a savant at self-studying and/or know the right people.

    Degrees do not guarantee success, they just open doors. If you think otherwise, you're a fucking moron.

    1. Re:Code monkeys don't need degrees by JohnFen · · Score: 2

      Pretty much. What an employer wants to know is if you are skilled enough for the position. A degree provides assurance of at least a minimum level of skill, but demonstrating the required skill through through experience is just as good (or better, if the candidate is a recent grad. They always need additional training.) That's why most jobs ask for a minimum degree "or equivalent experience".

      Generally speaking, if you have serious experience then a degree is of minimal or no value. If you have a medium level of experience, then a degree is helpful but optional (skill-specific certifications can be of more value in this case). If you have little or no experience, then a degree is essential.

      Whichever way you go, though, there are no guarantees. There are a million reasons why you might not get the job that are unrelated to your experience or education.

    2. Re:Code monkeys don't need degrees by TsuruchiBrian · · Score: 4, Interesting

      A degree provides an assurance of a *very low* skill level. Some people are very highly skilled at getting degrees they definitely don't deserve.

      That said, the degree is not worth very much. Ideally the knowledge gained on the road to getting that degree is very valuable. Many people don't actually retain (or never acquired) this knowledge, and therefore are not getting a good return on investment.

    3. Re:Code monkeys don't need degrees by The+Cynical+Critic · · Score: 3, Insightful

      If a degree provides an assurance of a "very low" skill level then your schools are either not very good or then they're just letting students pass courses they have no right to pass with their knowledge and skill level.

      A degree is supposed to guarantee an at least halfway decent skill level and a versatile foundation to build additional skills on. If a degree doesn't do this, then it's clearly not worth even the paper it's printed on.

      --
      "Why should I want to make anything up? Life's bad enough as it is without wanting to invent any more of it."
    4. Re:Code monkeys don't need degrees by Anonymous Coward · · Score: 0

      A degree used to be an indicator that you were one of the few people clever enough (and patient enough) to get a degree.
      Now, a degree is an indicator that you are one of the many people willing to take on enough debt to get a degree.

      Unless you're planning on becoming an academic, degrees do not prepare you for work.

    5. Re: Code monkeys don't need degrees by Anonymous Coward · · Score: 0

      An English degree would yell you both that the obvious intention was... ...at least a certain minimal level of skill.

    6. Re:Code monkeys don't need degrees by Drethon · · Score: 2

      Or a degree tries to prove an ability to learn complex skills. On the job is when real skills are actually learned and it takes someone who can learn them to do the job.

      Of course many companies want to hire people who already have the skills these days, rather than training people up. This despite the fact that few to no colleges can give a student years of experience with ARINC 429, MIL 1553, military GPS or TACAN radios to name a few possible things I've seen companies looking for experience on.

    7. Re:Code monkeys don't need degrees by Drethon · · Score: 2

      Instead of "very low", perhaps "very broad" is a more appropriate guarantee from a school. Companies on the other hand often want a very specific set of skills for the job they want. Too specific to make sense to teach in a school, without making, say, 1000 students with skills specific to 100 jobs.

    8. Re:Code monkeys don't need degrees by Freischutz · · Score: 3, Insightful

      A degree provides an assurance of a *very low* skill level. Some people are very highly skilled at getting degrees they definitely don't deserve. That said, the degree is not worth very much.

      If two fresh faced rookie developers with next to no experience walk in off the street one with a certificate that he has been made to work like a donkey for four years to acquire a certain basic skill level by a trusted training provider while all the other one has is his ability to radiate confidence and recite the mantra 'I taught myself to code, degrees are useless, trust me I'm an expert'. I know who I'm going to hire.

      Ideally the knowledge gained on the road to getting that degree is very valuable.

      Well, duh....

    9. Re:Code monkeys don't need degrees by JohnFen · · Score: 1

      Unless you're planning on becoming an academic, degrees do not prepare you for work.

      Yeah, that's not true.

      What's true is that a degree doesn't fully prepare you, but it does get you most of the way there. What's also true is that a degree isn't the only way to get prepared.

    10. Re:Code monkeys don't need degrees by Attila+Dimedici · · Score: 1

      If two fresh faced rookie developers with next to no experience walk in off the street one with a certificate that he has been made to work like a donkey for four years to acquire a certain basic skill level by a trusted training provider while all the other one has is his ability to radiate confidence and recite the mantra 'I taught myself to code, degrees are useless, trust me I'm an expert'. I know who I'm going to hire.

      That is all well and good, but what does your comparison between the handful of people who have gotten trained to program at a technical school with the many more numerous self-trained programmers have to do with a discussion comparing the many people with University degrees in Computer Science to the numerous self-trained programmers.

      There are few technical schools which work students like a donkey, but there are no universities which do.

      --
      The truth is that all men having power ought to be mistrusted. James Madison
    11. Re:Code monkeys don't need degrees by Gr8Apes · · Score: 1

      What's true is that a degree doesn't fully prepare you, but it does get you most of the way there. What's also true is that a degree isn't the only way to get prepared.

      I'd argue that for many degree based careers, a degree opens the door more easily and certainly smooths your path after getting in the door, provided you develop all the skills you need to learn post degree. This is true across quite a few technically based career paths, and is why a PE requires (or rather strongly promotes) an apprenticeship.

      --
      The cesspool just got a check and balance.
    12. Re:Code monkeys don't need degrees by TsuruchiBrian · · Score: 1

      If a degree provides an assurance of a "very low" skill level then your schools are either not very good or then they're just letting students pass courses they have no right to pass with their knowledge and skill level.

      I wouldn't say a school is necessarily "not very good" if it passes incompetent people. They could do a very good job of teaching, but a very poor job of things like testing, and detecting cheating. I guess it depends on what you thing the primary job of a school is. Some might want a school's primary job to be effectively teaching people who are willing and able to learn. Some (i.e. employers) might want a school's primary job to be weeding out cheaters and incompetent people with better testing, even if it comes at the expense of lower quality of education.

      A degree is supposed to guarantee an at least halfway decent skill level and a versatile foundation to build additional skills on. If a degree doesn't do this, then it's clearly not worth even the paper it's printed on.

      Indeed that is what it is supposed to do. But schools are for more than just handing out degrees. I went to a school where you could get a great education if you wanted one, or you could still get a degree without getting a great education, if you were willing to put your effort into getting a degree without knowing anything (e.g. cheating). I don't know how good my university is at mitigating cheating compared with other schools, but I know they were not perfect, and some incompetent people made it through.

      A degree is worth more than the paper it's printed on. It may or may not be worth the cost of tuition. It gets you a lot more interviews than you would get otherwise. That's not nothing, but it's also not everything.

    13. Re:Code monkeys don't need degrees by TsuruchiBrian · · Score: 1

      I'm counting "ability to learn complex skills" as a skill.

    14. Re:Code monkeys don't need degrees by TsuruchiBrian · · Score: 1

      The people that "work like a donkey" (not exactly sure what you meant by this, but I'll just assume it means working hard, correct me if I'm wrong) are basically people who are attaining much more than the minimum skill level guaranteed by a degree. At least this is the case if the certificate is from a reputable learning institution. What I am saying is that some people manage to get degrees without putting in the effort into learning the skills the degree tries to guarantee. This can happen for a variety of reasons (e.g. cheating). Even cheaters need to have a minimum level of proficiency to be effective cheaters, and this is the "very low skill level" I was referring to that a degree actually guarantees.

      I taught myself to code too. I also went to school and earned a computer science degree. Those are not the same thing. Just like earning an electrical engineering degree is not the same as teaching yourself to solder. I think I spent a few days total in university learning the basics of 2 or 3 languages, but for the message was basically "You can learn to code on your own time. Languages die, ideas are forever." We spent most of our time drawing boxes and arrows on paper and chalk boards and writing pseudocode and math equations.

      Knowing how to design software and knowing how to code are both important skills. You can teach yourself both, but one you can teach yourself in a few hours, days, weeks, and they other I think spending tens of thousands of dollars to having knowledgeable people explain it to you over the course of many years, is totally worth it.

    15. Re: Code monkeys don't need degrees by Anonymous Coward · · Score: 0

      I see you didn't bother with that English degree either. L2speelN00b!

  5. When you call those graduates "Coders" by Anonymous Coward · · Score: 0

    I'm not surprised.

    1. Re:When you call those graduates "Coders" by Anonymous Coward · · Score: 0

      This is dial-up BBS slang that somehow found its way into the American vernacular and it just needs to die. I'd rather they bring back k-rad.

      No, Mr. 50-year-old reporter, you don't sound "edgy".

  6. How by Anonymous Coward · · Score: 0

    Basically everyone I know in development is making over 100k, and I live in the midwest!

    1. Re:How by Anonymous Coward · · Score: 0

      time to move to the midwest.

    2. Re:How by computational+super · · Score: 1

      The article refers to England specifically - for some reason, developers aren't paid much in general throughout Europe. I don't know why.

      --
      Proud neuron in the Slashdot hivemind since 2002.
    3. Re:How by micahraleigh · · Score: 1

      In a Hobbesian state of nature, developers earn more than the general population.

      This is viewed as tyranny over in the EU.

      Developers of the world unite! You have nothing to lose but your comparatively higher salaries !!

    4. Re:How by mikael · · Score: 1

      Every country/city has a pecking order of who earns the most doctors/consultants, lawyers, estate agents, directors, managers, hardware/software engineers, architects. Then this is shaped according to the availability of different categories of housing. In an area where there is a housing shortage like university cities, the dual career-path option between management and technical gets eliminated, so the promotion path is purely into management, leading to tech flight into the rural areas.

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
  7. degree != goodCoder by Anonymous Coward · · Score: 0

    Too many degree mills just lead to absurd stats like these and this is the EU so....

  8. Now tell us the median employment rate... by Anonymous Coward · · Score: 0

    Similar salaries don't do you any good when no one will hire you without a degree.

    1. Re:Now tell us the median employment rate... by Ash-Fox · · Score: 1

      Similar salaries don't do you any good when no one will hire you without a degree.

      I don't have a degree and get paid a lot more.

      --
      Change is certain; progress is not obligatory.
  9. Computer science is not programming by Anonymous Coward · · Score: 0

    As somebody else put it: computer science is to computers in exactly the same way that astronomy is to telescopes.

    You learn a bunch of stuff in CS, only some of which is of relevance to software development, and even that is of marginal importance to typical, everyday software development. Consider: what's the big O efficiency of a particular algorithm? Now, how important is knowing that when you're writing a business application? Most of the time, having an efficient, or elegant, algorithm matters less than having something that does the job properly. The greater the degree of abstraction, the more likely that is to be the case.

    Which is not to say that a CS degree is useless, nor that efficiency is completely irrelevant. Only that the applicability of that knowledge, unless you're doing low level software development (embedded systems, OS kernel, that sort of level), is generally pretty low.

    I have a bachelor of computing, majoring in computer science, with honours. I learnt a lot in doing it. But the amount of actual application it's had to my employment since I completed it is virtually zero. I have no regrets about having done it, and I'd absolutely do it all again if I had the choice - but I'm also under no illusions that it plays (or played) a significant role in my professional career.

    1. Re: Computer science is not programming by Anonymous Coward · · Score: 0

      Somebody else put it? That's a quote from Dijkstra who is worth noting as the author.

      https://en.m.wikipedia.org/wiki/Edsger_W._Dijkstra

    2. Re:Computer science is not programming by JohnFen · · Score: 1

      Consider: what's the big O efficiency of a particular algorithm?

      When I do interviews, I have a couple of "sanity check" problems that I use to try to weed out the candidates who may be great at crafting code, but not great at designing software. A big-O problem is one of these.

    3. Re:Computer science is not programming by ebonum · · Score: 1

      How are a CS major and understanding big O efficiency related? A smart person will quickly grasp this concept. End of story.
      If you NEED a CS major to get such a simple concept, I really don't want you writing code.

    4. Re:Computer science is not programming by ebonum · · Score: 1

      Agreed. It is a good sanity check.

    5. Re:Computer science is not programming by Anonymous Coward · · Score: 0

      When is bubble sort better than quicksort?

      When the list is already mostly sorted and/or you are adding 1-2 elements. n is better than n*log*n (with an upper bound of n squared).

      big O is a 'decent' indicator of something is wrong. But if someone spouts out big O with out the +C you should chuck them out too.

    6. Re:Computer science is not programming by sfcat · · Score: 4, Interesting

      How are a CS major and understanding big O efficiency related? A smart person will quickly grasp this concept. End of story. If you NEED a CS major to get such a simple concept, I really don't want you writing code.

      You might think so, but in my experience this is simply not true. I've met many many many people who write code that purport to understand these topics (who can answer simple interview questions about this as well) but then write code that clearly indicates that they don't. CS majors with experience is the best filter I've found for understanding this topic and even that's a bit weak depending on the school. My hypothesis is that there is a certain number of iterations you need to do before you understand most topics and being self taught somehow doesn't ensure those number of repetitions. I do know however that the most efficient large pieces of code I've ever seen were all written by people with CS degrees and experience.

      --
      "Those that start by burning books, will end by burning men."
    7. Re:Computer science is not programming by Anonymous Coward · · Score: 0

      depending on how you phrase those sanity checks I think you are leaving yourself open, too many people rely on rote learning specific algorithms or efficiencies and if they do their research they will know you ask those sort of question and will be prepared to answer and it really doesn't tell you anything about how quickly they learn and adjust. usually I try and target how they handle a problem they won't have seen before. I usually arrange a few logic puzzles and even if they can't solve it I want to see that they can logically work through a methodology that leads them in the right direction rather than sitting their like a stunned mullet acting confused hunting in their memory for a previously learned response. you can teach algorithms, efficient coding techniques etc, it is much harder to teach someone to think logically through problems and this is what I am looking for in people that aren't going to be "just" coders.

    8. Re: Computer science is not programming by Anonymous Coward · · Score: 0

      In my experience, the same people who obsess about big-O also write hideous, muddleheaded, insecure, unmaintainable software. Moreover they tend to be obnoxious twats who alienate their colleagues.

    9. Re: Computer science is not programming by Anonymous Coward · · Score: 0

      It's frequently attributed to Dijkstra, but there's no evidence he said it.

    10. Re: Computer science is not programming by Anonymous Coward · · Score: 0

      the same people who obsess about big-O also write hideous, muddleheaded, insecure, unmaintainable software.

      So they should ignore big-O. Then several years after the system has been in use, they notice the system throughput is very low. Then they apply band-aids and other muddleheaded crap -- the true sign of mediocre programmers.

    11. Re:Computer science is not programming by Anonymous Coward · · Score: 0

      That's good. I've got twenty years of experience, and in my lowly BS in IT from podunk state we not only had to take DS&A (in C no less; manage your own memory, noobs!), but we had to take a class each in machine organization, statistics, and discrete math. I've also had a course in comparative programming languages. Big-O even to me is fundamental.

      I liked the program; not full-on CS but a few CS-like background courses along with a shitload of applied programming courses (C, C#, and Java) covering everything from Hello, World to multithreaded apps, with aspects like unit testing rolled in. Yes, it's an applied degree, but it's worked out well for me.

    12. Re:Computer science is not programming by Drethon · · Score: 1

      How are a CS major and understanding big O efficiency related? A smart person will quickly grasp this concept. End of story.
      If you NEED a CS major to get such a simple concept, I really don't want you writing code.

      You might think so, but in my experience this is simply not true. I've met many many many people who write code that purport to understand these topics (who can answer simple interview questions about this as well) but then write code that clearly indicates that they don't. CS majors with experience is the best filter I've found for understanding this topic and even that's a bit weak depending on the school. My hypothesis is that there is a certain number of iterations you need to do before you understand most topics and being self taught somehow doesn't ensure those number of repetitions. I do know however that the most efficient large pieces of code I've ever seen were all written by people with CS degrees and experience.

      My bent $0.02, having a CS degree is a better indicator of understanding these complex topics and not having it is a poor indicator as such. I think most (not all) people who understand complex topics, like big O, could be either CS graduates or non graduates. But the CS degree helps to indicate a person who can learn this. However there are people who don't understand it and skirt through graduation, just like there are people who never took a formal course but have the ability to learn these topics.

    13. Re: Computer science is not programming by JohnFen · · Score: 1

      The point isn't to find people who are really into big-O. The point is to find people who are knowledgeable about computer engineering. I don't expect a brilliant answer, I expect an answer that demonstrates knowledge of the subject.

    14. Re:Computer science is not programming by JohnFen · · Score: 1

      The sanity checks are usually in the form of giving a problem to be solved, not so much asking questions.

    15. Re:Computer science is not programming by JohnFen · · Score: 1

      How are a CS major and understanding big O efficiency related?

      They aren't. I'm not looking for degrees, I'm looking for expertise needed for the position being filled.

    16. Re:Computer science is not programming by Anonymous Coward · · Score: 0

      I've met many many many people who write code that purport to understand these topics (who can answer simple interview questions about this as well) but then write code that clearly indicates that they don't.

      This is what Richard Feynman called only having a fragile understanding. This is where a person can memorize a concept and regurgitate it back, but can't connect that to actual working examples.

    17. Re: Computer science is not programming by Anonymous Coward · · Score: 0

      Why would you have a "mostly sorted" list to begin with? Either spend the resources to fully sort it every time or to sort once and maintain order. This half ass sorted list floating around where you are debating using a bubble sort or a quick sort doesn't help anyone.

    18. Re: Computer science is not programming by Anonymous Coward · · Score: 0

      Changing a sort algorithm is EASY. If you consider that a bandaid that will mess up your code, you are doing it wrong. If you designed your program properly, using the wrong sort algorithm would be as simple as changing ONE small method. Lists and data change as a program ages. Do yourself a favor and design with ease of change in mind and a simple inefficient sort algorithm won't be much hassle.

    19. Re:Computer science is not programming by redmasq · · Score: 1
      In my experience, a person does not necessarily need to know or even understand Big O to write good code as long as they have been trained with good habits and this is more so if they can quote off that in most cases a quicksort averages better than a bubble sort (except when the list is mostly sorted and other similar bit of trivia).

      Of course, the above is specifically for your average day-to-day code in which performance and memory requirements are relatively loose. Regarding the ones in which I have trained, only half had even heard of Big O, and maybe two actually had a real understanding. That said, someone who does have the concepts at least internalized will overall produce more efficient code. Note that I did not say better in this case since efficient code is not necessarily maintainable code.

      I have found in a number of cases (training the incoming juniors; anecdotal) that many do not care about the "superfluous details" of what goes on "behind the scenes of algorithms" since there is the impression that the libraries are supposed to do the heavy lifting. In this case, I think there is a case of maturity; however, I found that plenty of repetition and reviews (not lectures, in spite of my verbose nature making me prone to giving them) will solidify (indoctrinate?) the concepts to the point they are accepted and appreciated.

      My hypothesis is that there is a certain number of iterations you need to do before you understand most topics and being self taught somehow doesn't ensure those number of repetitions.

      It may be to note, I was self-taught and understood those concepts prior to getting my original AS in computer science (which I got and later extended to a BS for career reasons). While I do not think this is untrue, I do not think it is always the case. My personal nature makes me a bit of a self-study and experimenter. The couple of trainees that I met that did already understand the concepts were pretty much the same.

      How are a CS major and understanding big O efficiency related? A smart person will quickly grasp this concept. End of story. If you NEED a CS major to get such a simple concept, I really don't want you writing code.

      I think this is a short-sighted point of view. Some people do need a bit of a shove to understand some concepts. Big O came naturally to me, but formal writing, the kind a project manager uses to communicate with the non-techies did not. I benefited greatly from being coached from my writing teachers in high school and college. In that area, I needed the extra push; some people are the other way around. In all honesty, I rather than writing efficient code, I rather have someone write maintainable code, i.e., code that is mostly easy to read, do not (excessively) rely on "tricks," and where "tricks" should be used, to have it well documented. I would also rather have someone that can work with the team. This does not, however, mean docile. One of my best subordinates challenged my instructions and design decisions daily, but he worked well with the team and his doing so helped to isolate edge cases which were otherwise invisible.

    20. Re:Computer science is not programming by Anonymous Coward · · Score: 0

      You realize most people applying for coding jobs can't write FizzBuzz, right?

    21. Re:Computer science is not programming by Anonymous Coward · · Score: 0

      It's a simple concept only if your understanding stops at "each loop means one n". I've had people using that rule and coming up with O(2n) (two loops over the input) and so on.

      A CS major would understand why these are not O(n), for example
      for value in array:
              if (k - value) in array:
                      do something

      or

      for value in sorted(array):
              if x > value:
                        print smallest item larger than x is value

      and so on

  10. Stupid study by kamapuaa · · Score: 3, Funny

    who gets paid in pounds lol

    --
    Slashdot: providing anti-social weirdos a soapbox, since 1997.
    1. Re:Stupid study by Anonymous Coward · · Score: 0

      who gets paid in pounds lol

      People in the UK, to hazard a wild guess.

    2. Re:Stupid study by Anonymous Coward · · Score: 0

      People who get paid in gum, obviously.

    3. Re:Stupid study by Anonymous Coward · · Score: 0

      American women, obviously.. :-)

    4. Re:Stupid study by Frosty+Piss · · Score: 1

      who gets paid in pounds lol

      I was going to say Civil Engineers, or maybe Tori Black...

      --
      If you want news from today, you have to come back tomorrow.
    5. Re:Stupid study by godrik · · Score: 1

      who gets paid in pounds lol

      If that's worth anything, my doctor says I should get rid of 60 !

    6. Re:Stupid study by Anonymous Coward · · Score: 0

      who gets paid in pounds lol

      Your mum.

  11. UK Salaries are trash anyway by Anonymous Coward · · Score: 0

    This study is moot. Everyone knows tech salaries in the UK are way lower than American salaries.

  12. CS degrees in job market aren't about pay scale by Ungrounded+Lightning · · Score: 1

    CS degrees in the job market aren't about the pay scale.

    They're about getting past the bureaucrats in the HR departments. So they're about being hired at all.

    You can make as much (or even more) if you're a substantial programming talent even without a degree. But that does you no good if you have no job and make nothing.

    Back in the late '60s (Minsky's "first period") a 4-year CS degree actually HURT employability. The schools were teaching a lot of stuff that wasn't really useful on a job (for instance: How often do YOU write a new compiler for some programming task?), and someone with a degree was viewed as having more to unlearn before he could focus on learning what the employer needed.

    About the turn of the millennium it was nearly impossible for someone without a degree, regardless of experience and other credentials, to get a job at a US corporation.

    Not sure what the situation is these days. (After a couple years out of work I helped found a startup. B-) )

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    1. Re:CS degrees in job market aren't about pay scale by JohnFen · · Score: 1

      Back in the late '60s (Minsky's "first period") a 4-year CS degree actually HURT employability.

      This was true all the way through the '80s.

    2. Re:CS degrees in job market aren't about pay scale by Antique+Geekmeister · · Score: 1

      A CS degree helped employability for _military_ work in that period. The money for leading edge research involved military work, such as guidance systems and cryptography.

    3. Re:CS degrees in job market aren't about pay scale by Greyfox · · Score: 2

      Once you have a few years of experience, they stop asking anymore. I dropped out of school in the '80s to take a programming job. I always thought I'd eventually get sick of the industry and go back to school. I guess after three decades it's silly to keep saying that. I'm frequently asked to weigh in on hiring decisions and personally put more stock in an active github account and a gung-ho attitude than I do some piece of paper. You can still get into the industry without a degree, as long as you can get your resume past HR.

      --

      I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

    4. Re:CS degrees in job market aren't about pay scale by micahraleigh · · Score: 1

      The claws are out between people with degrees and those who don't. Personally I like Boeing's approach where their HR looks at a CS degree as basically 2 years of experience.

  13. Name is a name is a title .... by Anonymous Coward · · Score: 3, Informative

    I have designed and developed software and have had many different titles.

    Programmer, engineer, analyst, systems analyst, software engineer, etc ....

    And all of them had the exact same duties: take specs, design an algorithm when needed, and implement it in a programming language.

    Some companies gave the title 'engineer' because that was how the pay grades worked.

    Titles are also used to boost people's egos while the company gets away with paying shit. "It's not in the budget for a cost of living increase, but you've been promoted to systems engineer."

    The worst one I've ever seen was someone who was promoted to 'scientist' - with just a BS.

    Whatever, my title is software GOD and I have a long white beard, white flowing robes, and rub my feet on the carpet so that I can give little static shocks and call it my 'lightening bolts'.

    1. Re:Name is a name is a title .... by Pseudonym · · Score: 1, Insightful

      And all of them had the exact same duties: take specs, design an algorithm when needed, and implement it in a programming language.

      Some companies gave the title 'engineer' because that was how the pay grades worked.

      My job title changed to "engineer" when my duties started to include things like:

      - Going through contracts and turning them into milestones.
      - Timeline and budget estimation, and tracking projects relative to the estimate.
      - Managing a team and mentoring other people.
      - Appraisal of and response to issues raised by professional ethics, safety, privacy, environmental impact, and other legal requirements and the public interest.

      You know, actual engineering.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    2. Re:Name is a name is a title .... by Richard_at_work · · Score: 4, Informative

      That all sounds like management rather than engineering...

    3. Re: Name is a name is a title .... by Anonymous Coward · · Score: 0

      Dude, you're a suit. Most of that shit is made up feel good MBA crap and if you ever knew how stuff gets made you'd know it.

    4. Re:Name is a name is a title .... by Anonymous Coward · · Score: 0

      Coder whatever name you call it STILL is not why you get a computer science degree. Also if you are calling Systems analysts and Software engineers as just coders then where you work is fucked up in the extreme. Systems Analysts should be writing those specs in conjunction with Business Analysts, Software Engineers should be designing the systems to meet the outputs of that process, The coders should be on the receiving end of that output where they produce the code based on specs and designs produced in the previous stages.

    5. Re:Name is a name is a title .... by Pseudonym · · Score: 1

      The key word here is "include". I still mostly write software, but now they make me understand everything from instruction timings to community outreach.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    6. Re:Name is a name is a title .... by PopeRatzo · · Score: 2

      My job title changed to "engineer" when my duties started to include things like:

      - Going through contracts and turning them into milestones.
      - Timeline and budget estimation, and tracking projects relative to the estimate.
      - Managing a team and mentoring other people.
      - Appraisal of and response to issues raised by professional ethics, safety, privacy, environmental impact, and other legal requirements and the public interest.

      Did they give you an additional title when you learned all the meaningless jargon?

      --
      You are welcome on my lawn.
    7. Re:Name is a name is a title .... by Pseudonym · · Score: 1

      Making things on time and on budget isn't meaningless,but it's surprisingly hard when you're doing actual research for a living.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    8. Re: Name is a name is a title .... by Pseudonym · · Score: 1

      I don't even work for a private company. Nice try though.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    9. Re:Name is a name is a title .... by slacktide · · Score: 1

      That sounds like the things I do at my job as a Lead Engineer at a large aerospace manufacturer. Mechanical and structural design engineering, primarily related to the installation of engines and APUs, if that makes it "real engineering." What you describe is the "Lead" part of my job, not the "Engineer" part of my job. Regardless of what your job title is, your job role is Lead Coder.

      Engineering is the professional art of applying science to the optimum conversion of the resources of nature to the uses of humankind.

    10. Re:Name is a name is a title .... by Pseudonym · · Score: 1

      The question of whether or not software engineering is really engineering is an interesting question. It's certainly applying science, you're certainly using (and, at its best, accounting for) natural resources, and you're really building things that could really hurt people.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    11. Re: Name is a name is a title .... by Anonymous Coward · · Score: 0

      Oh Jesus, are you making this up, or do you really work on massively over budget, billion dollar defense contracts? Costs too much and takes too long for almost all work.

    12. Re:Name is a name is a title .... by Anonymous Coward · · Score: 0

      engineering is the end to end development cycle, it will include many items that are management, especially if it isn't a very large project where you can have dedicated resources for those tasks.

    13. Re:Name is a name is a title .... by PopeRatzo · · Score: 1

      I was just kidding, man. No offense meant.

      Certain buzzwords, like "milestones" and "mentoring" just bring me back to the bad old days when I had to work for a living. Those words are as good as any others, I guess, and I'm sure you're really good at what you do. I'll bet you have a high level of core competency and are able to adapt to shifting paradigms, thereby meeting strategic aims by standardizing infrastructure and facilitating supply-based consolidation while developing robust and scalable platforms.

      Seriously, I'm sorry if I offended you.

      --
      You are welcome on my lawn.
    14. Re:Name is a name is a title .... by Njorthbiatr · · Score: 1

      My degree is in actual software engineering from an engineering college.

      Not only were the courses tougher than the CS program (with more math, more science), the focus on software is slightly different and more towards creating systems and solving problems using existing software rather than the actual solution. But that is the fantasy they sell. In reality you end up sitting in a chair writing the implementation eight hours a day (most of the time) out of school, even if you've been trained otherwise.

      It does still rub me the wrong way when people say they're software engineers. It's like calling yourself a computer scientist because you know web programming and got a BA in Computer Science and write front-end code.

    15. Re:Name is a name is a title .... by Pseudonym · · Score: 1

      I'm sure you're really good at what you do.

      I'm not so sure, but thanks for the kind words anyway.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    16. Re:Name is a name is a title .... by Anonymous Coward · · Score: 0

      That's project manager title stuff.

      It is funny how job titles and duties have changed. Years ago, a research scientist was the person who actually did the lab bench work. And the lab technicians would manage supplies and set up kit for experiments, while the research manager/director did all the project management work. Now it's the lab technician who does the lab bench work, the research manager has disappeared and the research scientist does the project management work.

    17. Re:Name is a name is a title .... by Darinbob · · Score: 1

      True. I started saying engineer about myself periodically once I was a member of the engineering departments, and I get "must attend" invites to hardware design reviews. I'm not really an engineer, not having the proper certificate. However, I asked around, and apparently most hardware and RF engineers don't have such certificates, it's only necessary when a name is needed on some official documents.

    18. Re:Name is a name is a title .... by Ol+Olsoc · · Score: 1

      However, I asked around, and apparently most hardware and RF engineers don't have such certificates, it's only necessary when a name is needed on some official documents.

      Exactly this. The certificate is important when one is called to testify as an expert witness in a court of law. But it has nothing to do with competence. It just means you have a certificate that lawyers have to accept. I'm a polymath, and while a lot of engineers and scientists want me on their teams, my testimony would never be accepted in court. That's not a bad thing, mind you.

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
    19. Re:Name is a name is a title .... by Ol+Olsoc · · Score: 1

      My job title changed to "engineer" when my duties started to include things like:

      - Going through contracts and turning them into milestones. - Timeline and budget estimation, and tracking projects relative to the estimate. - Managing a team and mentoring other people. - Appraisal of and response to issues raised by professional ethics, safety, privacy, environmental impact, and other legal requirements and the public interest.

      Did they give you an additional title when you learned all the meaningless jargon?

      When people ask me what I do, I tell them "I conceptualize, initialize and bring action items to fruition". The ones who think that gibberish is cool are permanently ignored

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
    20. Re: Name is a name is a title .... by Gr8Apes · · Score: 1

      Been through the mill in all stages of nothing to government contracts. If you're building real software for a growing business, you're better off writing specs at some point after the startup phase, and sometimes during it. Yes, it costs more and takes a little longer, but that's a whole lot better than having the house of cards come crashing down at an inopportune time, like when you're about to go public and people check out out because of the buzz.

      --
      The cesspool just got a check and balance.
    21. Re:Name is a name is a title .... by Anonymous Coward · · Score: 0

      Do you work for Tata Consulting by any chance? Next thing you'll be saying is that those coder work should be offshored to India.

    22. Re:Name is a name is a title .... by Anonymous Coward · · Score: 0

      I don't know. It sounds to me like Systems Engineering.

      True it's not bending metal or writing source-code. However, it is definitely a type of engineering as well, and people there can be very technical.

    23. Re: Name is a name is a title .... by Anonymous Coward · · Score: 0

      Dude, if you think all of that is just made up "shit", you're the one whose lacking any experience building something (of any scale or importance) that'll actually work.

    24. Re:Name is a name is a title .... by K.+S.+Kyosuke · · Score: 1

      Aren't cost estimates a necessary part of engineering? Designing things to do stuff is obviously a part of engineering, but oftentimes you come up with how to do an old thing in a new way that is cheaper or easier. But in order to do that, a grasp of costs seem vital.

      --
      Ezekiel 23:20
    25. Re:Name is a name is a title .... by K.+S.+Kyosuke · · Score: 1

      Engineering is the professional art of applying science to the optimum conversion of the resources of nature to the uses of humankind.

      So operational research is included?

      --
      Ezekiel 23:20
  14. Pounds? by mentil · · Score: 1, Funny

    only earn 3,000 British Pounds (BP) more a year

    Can someone convert this to something I understand, like Dogecoins per fortnight?

    --
    Corruption is convincing someone that the selfless ideal is the same as their selfish ideal.
    1. Re:Pounds? by hord · · Score: 1

      I think with the current Brexit exchange rate this equates to a large bag of candy. Higher skilled employees require more sugar for cognition and literally gain pounds.

    2. Re:Pounds? by bugs2squash · · Score: 1

      about $3000 post brexit. I'm not sure the students are hurting so much financially, many of them will have their debts automatically cancelled before they pay them off. There is a maximum payment per year that's low to nothing if the wages are low.

      --
      Nullius in verba
    3. Re:Pounds? by JasterBobaMereel · · Score: 1

      Current exchange rate 1 UKP = 1.35 USD ...

      --
      Puteulanus fenestra mortis
    4. Re:Pounds? by Mouldy · · Score: 1

      What is with the random currency acronyms in this story (and your comment) - are these Americanisms?

      £ or GBP are far more commonplace than BP or UKP - I'd never heard of BP or UKP in the context of British currency until today.

    5. Re:Pounds? by Anonymous Coward · · Score: 0

      True. I expect that if the story was about the US and used UD or AD (American Dollars) instead of USD, then the first few posts would have been rants about it and the quality of editing. I suppose that this just goes to show that there is a little truth in the cliche about people in the US not knowing much about the rest of the world.

    6. Re:Pounds? by mccalli · · Score: 1

      Well, as a British guy with twenty years of currencies experience I'd like to ask the same question. Never once seen Sterling referred to as BP before - GBP is the term, or Sterling, or Pound Sterling. British Pounds? The phrase just doesn't get used.

    7. Re:Pounds? by Anonymous Coward · · Score: 0

      Whose dollars are worth more than the pound? 9000GBP is worth well over 12000USD, if you want to compare with a major dollar currency.

    8. Re:Pounds? by Hognoxious · · Score: 1

      Some part of "post brexit" confusing you?

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  15. Ummmm.... by Zurkeyon3733 · · Score: 1

    Last time I checked, giving a dumbass the ability to code, simply results in dumbass code :-P

  16. Blame Open Source. by Anonymous Coward · · Score: 0

    I've spoken to hundreds of new grads and young developers and the cry is the same from many of them: the open source model of development has undermined the ability of good coders to earn. Developers are now expected to spend the most productive years of their lives developing software for free to be given away with so called "permissive" licenses such that corporations can simply use it without any kind of recompense. Only after those years of acting as essentially unpaid interns can a developer now hope to be hired. And then after years of toil, to be rewarded with outsourcing to cheap and incompetent Indian firms who charge pennies on the dollar for developers who don't have any qualifications other than learning how to compile code written by those self same developers when they were building their github portfolio!

    When you really look at the history of "open source" you start to realize how it was created by corporate masters intent on turning a well paid profession into just another low paying service industry, with jobs easily outsourced and discarded.

    1. Re: Blame Open Source. by Reverend+Green · · Score: 1

      The problem is the permissive licenses. I've made that mistake myself in the past.

      Now any Free Software I write is released under the Affero license (AGPL). Akaik that license is the most viral and the least prone to capitalist exploitation.

    2. Re: Blame Open Source. by Anonymous Coward · · Score: 0

      Not how I remember it, open source was a response to the dominance of Microsoft. Why should MS be the only option to run my computer? Also response to patents. Everyone needs to use X but some company has a patent on it. So roll your own version of X.

    3. Re: Blame Open Source. by TheRaven64 · · Score: 1

      I honestly can't tell if this thread is satire.

      --
      I am TheRaven on Soylent News
    4. Re: Blame Open Source. by Reverend+Green · · Score: 1

      I disagree with some of the OP's points, but I don't think it was satire; nor was my reply.

  17. Faulty comparison by holophrastic · · Score: 1

    Comparing the salary of a coder with a degree, to the salary of a coder without a degree, is apples to oranges. You want to compare the salary of an unemployed person to a coder without a degree. Most people go to school to learn the skill. A degree is nothing more than one type of proof-of-skill. Not every industry needs proof-of-skill to be hired.

  18. It was worth it by VocationalZero · · Score: 5, Insightful

    I can't be the only one who is proud of their CS degree. The courses I took challenged me greatly, and often taught me the answers to questions that I didn't even think to ask. Maybe I was lucky, but the professors I had helped me expand my knowledge far quicker than I could have done without them. Their dedication to education showed, and made it far easier to learn the concepts, history, and practical application of software development and computer science in general.

    I often hear that "I'd rather have a self-taught English major, because they show dedication and adaptability", and I respect that, but I this attitude also sort of dismisses the fact that CS students can be just as dedicated and adaptable, and also have a large amount of relevant knowledge on the subject. I have worked with people with and without degrees in the relevant field, and those with seem to lean on me far less than those without. Just my personal experience.

    I wouldn't say that I'd be lost without my CS degree, but I doubt very much I'd be able to get where I am today as quickly as I did, without it. Plus, I really did love my classes, so even if it isn't a "positive return on investment" (which I still kind of doubt is really the case), I do not at all regret earning the degree.

    1. Re:It was worth it by Anonymous Coward · · Score: 1

      Couldn't agree more. My CS degree was worth every penny and laid a solid foundation from which to build on. Not to mention that attending the university was a unique experience that I really enjoyed. Self-taught developers can be great too, but most of the ones I have met work on basic web development, and have a rather narrow understanding of computing in general. I think the old saying "You don't know what you don't know" applies here. Getting my degree expanded my mind in ways I never could have done on my own.

    2. Re:It was worth it by Anonymous Coward · · Score: 0

      perhaps you went to a uni with a very high standard of lecturers with a great CS course. Mine was a decent Uni with a well regarded course but Personally I found, with only a few exceptions, nothing in the CS degree was particularly challenging and if anything it was disappointing as it allowed me to comfortably cruise through the degree with distinctions as the courses were designed for the average student not for students with a good grounding or a penchant for the materials. At the end of my degree I had my piece of paper that helped me get my first job, but looking back on it my degree and the subsequent honours they convinced me to do were pretty much a waste.

    3. Re:It was worth it by Darinbob · · Score: 1

      Yes, the degree is highly helpful. It's just that today there is a very strong anti-elite element out there that is actively encouraging people to skip all education. I really don't know what the motivation is.

    4. Re:It was worth it by Anonymous Coward · · Score: 0

      I don't have a degree, but I've trained a number of people with them. I think decent CS programs usually provide *some* value.

    5. Re:It was worth it by Tablizer · · Score: 1

      I can't be the only one who is proud of their CS degree. The courses I took challenged me...

      The degree gave me an overview of hardware, machine language, and low-level algorithms that I probably otherwise would ignore if I jumped directly into "corporate" programming languages and tools. It can give one a better understanding and appreciation for performance and edge cases, like why floating-point numbers can mangle monetary values under some circumstances.

      And a well-rounded education makes one a better writer, communicator, and analyst.

      A better survey would follow people for a longer period of time as they move up the ladder into architects, analysts, and management.

    6. Re:It was worth it by gweihir · · Score: 1

      I teach on the side, and my current Software Security course is about half students that actually work 50-60% as....coders. Why are they going for a CS degree while already having a reasonable job? Most answer that they found they have trouble understanding the theory behind the stuff they work on and that this decreases the quality of their work and limits their future options.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    7. Re:It was worth it by gweihir · · Score: 4, Interesting

      I noticed the same thing. In the CS area, I think the mechanism is pretty clear though, all those no/wrong-degree coders are trying to make sure they are not seen as inferior (which they are, often grossly so, with a tiny number of exceptions). I run into this all the time with personnel of customers.

      The really problematic thing is that you usually only understand the worth of a degree several years after you have gotten it. That allows the anti-degree people to claim that those with degree are just lying about it and do not want to admit having wasted their time. In actual reality they are simply blind because they lack that experience and they are unwilling to believe otherwise. A Dunning-Kruger type of effect is at work here. Also, as they would have to acknowledge being wrong and possibly being inferior in the relevant skill space, it is quite understandable that many are unable to come to grips with that. Hence they claim "degrees are worthless" and such things.

      This is strong with self-taught coders here on /. as well. They are blind to their limits and claim these limits are irrelevant or do not exist. Do not listen to these people! Sure, a degree will not turn a dumb person into a smart person, and hence there are quite a few incompetents with degrees out there, but a lack of degree will severely limit even a smart person and that is a real problem.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    8. Re:It was worth it by AmiMoJo · · Score: 1

      The issue with low wages is that the UK in general is a low wage, high cost, low productivity economy.

      In the UK a lot of jobs do list a degree as a requirement. It's actually something that people without degrees complain about a lot because it locks them out, and that people with degrees complain about because it cheapens their expensive qualification when the assistant manager in a shop needs 3 years of full time study just to apply.

      Degrees are also insanely expensive in the UK. That's only going to get worse as the immigration situation deteriorates and the supply of full fee paying foreigner students dries up.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    9. Re:It was worth it by Anonymous Coward · · Score: 0

      I have worked with people with and without degrees in the relevant field, and those with seem to lean on me far less than those without. Just my personal experience.

      similar but different field, but around here those with tend to be seem to take a lot longer accomplishing a task than just getting on with it, and don't dare ask a question cause then they are forever up your shit all the time barging in on how much better it would be if one sat down and thought though every theoretical situation on something so dead simple that even a flunkie could do it

    10. Re:It was worth it by Anonymous Coward · · Score: 0

      I often hear that "I'd rather have a self-taught English major, because they show dedication and adaptability", and I respect that,

      I don't 'respect that'. I usually ask such people if they take the same view when seeing a doctor. Preferring someone with 'dedication and adaptability' over relevant education, heh?

      Of course, having completed the education isn't everything. Someone with several A's are usually much better than those with C's only. Some people want to learn stuff in university, others are just trying to get through and move on. Sure, the last group lack the dedication, but they are not the only kind you find in universities.

    11. Re:It was worth it by computational+super · · Score: 1

      I can't be the only one who is proud of their CS degree.

      I can never quite get my head around the anti-CS sentiment that pervades (and has always) Slashdot. I guess there's this group of people who managed to get into programming without any kind of degree who assume that everybody who does have one spent their teenage years smoking pot and playing video games and, when they turned 18, thought, "Oh shit, I'd better go to college and learn something useful so I can get a job - maybe I'll do one of those computer thingies!" On the contrary, though, when I was a CS major, most everybody I was in school with had already spent their teenage years teaching themselves to code and had gone to college to study computer science formally for a couple of reasons: a) you need a degree (or we thought we did) to get a good job and b) maybe there's a possibility that some of those egg-head college professor dudes might know a thing or two I actually didn't know and I might learn something I otherwise wouldn't have learned.

      --
      Proud neuron in the Slashdot hivemind since 2002.
    12. Re:It was worth it by computational+super · · Score: 1

      trying to make sure they are not seen as inferior

      I'd be more sympathetic if they weren't trying so hard to invert that sentiment - "If you had to go to college to learn to program instead of from 'teach yourself programming in 21 days', you're a retard" or "I'd rather hire somebody with 20 years of real experience than one of those computer science 'big O notation' snobs any day" (missing that you can actually do both) are pretty common Slashdot platitudes.

      --
      Proud neuron in the Slashdot hivemind since 2002.
    13. Re:It was worth it by computational+super · · Score: 1

      Mine required me to learn calculus, statistics, number theory, probability and linear algebra. Do I sit around and calculate eigenvectors or determinants or differential equations all day? No. Am I glad I learned all that. Hell yes. Would I ever have learned that if I'd skipped the degree? Definitely not.

      --
      Proud neuron in the Slashdot hivemind since 2002.
    14. Re:It was worth it by gweihir · · Score: 1

      Indeed.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    15. Re:It was worth it by Anonymous Coward · · Score: 0

      No it's more likely because they realized they are screwed without the degree if they want to get past a certain point at their current employer or past the HR filters if they are looking to get a new job. I'm not a coder, but I am IT and I'm basically as far as I can go without a degree, which is stupid because I can do the higher level jobs around here that those who have degrees seem to screw up in so often.

    16. Re:It was worth it by Hognoxious · · Score: 1

      Degrees are also insanely expensive in the UK.

      If the UK is insanely expensive I don't think there's a word to describe the situation in the US.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    17. Re:It was worth it by h4ck7h3p14n37 · · Score: 1

      Meh. I took a job at a web startup in 1996 while I was a sophomore studying computer science in the College of Engineering. I learned way more from that job than I did from my course work. I was the sysadmin, web master, DBA and application developer for that company. I learned Perl, how to admin an Irix server, DNS (named), Apache httpd and MySQL.

      I did learn quite a bit from my classes, I really enjoyed my technical electives in computer architecture and operating systems, but you're only learning maybe 25% of what you really need to know in order to work independently in industry. Then you've got all that time wasted on general education requirements; things that you should have learned in high school.

      I ended up dropping out of my college program when I did a graduation check and found I had a deficiency. I already had a job and was fed up with school at that point, so I just said to hell with the degree and went on with my life. You know what I discovered? No one (except large, rigid corporations) gives a shit about your degree, they only care about what you can bring to the table.

    18. Re:It was worth it by Tablizer · · Score: 1

      As more topics are piled on, perhaps some do need trimming since there's only so much room and time. The economy used to be geared around physical manufacturing. Perhaps the math education conventions need to adjust to this fact, and focus more on things like category theory and less on physics-related math.

    19. Re:It was worth it by swilver · · Score: 1

      I agree that everyone deserves a chance, and their CS degree should not be held against them.

    20. Re:It was worth it by Bengie · · Score: 1

      There's a lot of diploma mills mass printing CS degrees and the general populace is grouping in decent schools with the trash. Even within good Uni/Schools, there are a lot of people getting degrees that shouldn't. There's a group of Ivy league CS professors that have been working with psychologist for over 20 years trying to figure out why so many people are so bad at programming in general, not just CS.

      What they're currently seeing is 80% of student who apply fail in the first two semesters, 20% drop/fail for various reasons after the first two semesters, of the remaining 16%, 50% graduate only because of perseverance, not ability, and of the remaining 8%, they're on a power curve where 80% are below average. When taken as a whole, ~98% are below average. Does not seem to be a bell-curve at all.

      They have done all kinds of experiments, sourcing ideas from all over the world from many CS or psychology professions, but nothing has worked. They can't seem to make it any easier. So far they have only found one predictor that seems highly correlated are predicting if the student will graduate and be good. Logical consistency. They have some tests that are very hypothetical and require using abstract reasoning to solve for a fictional problem. Think of an abstract reasoning test with pseudo-code instead of visual patterns. They look for two things in these tests, logical dissonance and repeat-ability of getting the same answer some many months later. Even if the reasoning is wrong, as long as it's consistent and does not contradict itself, they have a very high chance of being good at CS+programming.

      The tests are "decent" at predicting if a student will probably be decent, but nearly perfect for predicting if they'll be a failure. Always easier to be the critic.

    21. Re:It was worth it by Darinbob · · Score: 1

      I spent 4 years trying to get a PhD but then dropped out; I did get a master's along the way luckily. There were some drawbacks to it, such as looking like an entry level employee to everyone despite having prior industry expereince. But I don't consider it a waste of time either. There were new things I would not have learned elsewhere, I had to really scrub out the cobwebs after being in industry and learn to think again, and doing the research and projects really is its own form of experience.

    22. Re:It was worth it by gweihir · · Score: 1

      I do agree to that.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    23. Re:It was worth it by Darinbob · · Score: 1

      I worked for a boss who used the "Learn C in 21 Days" book. He was horrible at programming. He used to do mainframe programming and he copied that style. He literally would use strncmp(str1, str2, 1) to see if two characters were the same; he was not a believer of writing a function if cut-and-paste could to the job instead, and when he did his cut-and-paste he would never re-indent the code afterwards.

      Today I've got a worker who is self taught. It's just horrible programming styles. Zero concept of software organization or engineering, it's all about whipping out code super fast and checking it in once it compiles. And manages to convince some people that he knows what he's doing so he retains his job.

    24. Re: It was worth it by Anonymous Coward · · Score: 0

      I have to say im sad to agree with you.

      I am self taught, never finished highschool.

      I've been working almost 20 years in the field, and have always considered my lack of formal education an advantage - i never jumped at a textbook answer too quickly for instance, or had the attitude that "if i wasnt taught X in school, then X is not my job, blank stare" (and i saw this a lot, especially with that wave of java kids). I started writing embedded systems as my first job as a script monkey, learned stuff from writing kernel drivers to implementing gui toolkits from scratch in C.

      I ended up doing a lot of FOSS, mostly with GNOME (I wrote Glade and helped maintain GTK+ fwiw)... And was astonished to find that when i finally met my FOSS peers which i greatly admired; literally ALL of them held some degree. This really surprised me, and yes i see self taught novices all the time writing crappy web frontend stuff.

      I have to admit, I always saw higher education as a sort of mafia; they want to charge you a ton of money, they want you to expand their knowledge base with your PhD, and then they want to be the gatekeepers of this knowledge, its completely offensive.

      That said i also always thought higher education was a great thing, in the cases that its really only about learning something, and not something petty like obtaining a certificate they are telling you that you need.

      Best Regards,
            -Tristan

    25. Re: It was worth it by Anonymous Coward · · Score: 0

      Same not very AC here (can't be arsed to sign up to this site, even if I've been reading it for over 15 years)

      @gweihir: I should elaborate on another statement in your post: 'Hence they claim "degrees are worthless" and such things'

      I have never said that, BUT, I have always been of a mind that degrees SHOULD be worthless. In fact the world would be a much better place if people DID attend university for the sake of learning something (which is not worthless), but that the concept of a "degree" just never existed.

      Unfortunately, degrees have everyone fooled into this game, universities would churn out much more talent if the attendees were just there to learn, at their own pace, and didnt expect any form of entitlement in return.

      As a side effect, those of us who have "rejected the system" are passed off and have to work twice as hard (in the early stages of our career), because everyone is drinking the university cool-aid, and accepting point blank that a piece of paper is the qualification for entry.

      I've borne a lot of resentment towards the education system of our time, I wish that it were different: I was offered a chance one time to possibly earn an honorary degree, and did not pursue it at all as a matter of principle, I dont want to reinforce the idea that these greedy gatekeepers of knowledge, hoarders, have any authority to dictate the worth of an individual.

      With that said, I have not borne any resentment towards degree holders, or ever said "degrees are worthless" (it's inaccurate, and sounds denigrating), however I can see how someone who lacks patience or who is generally insecure, might easily misconstrue my world view as one that is denigrating and insulting towards degree holders (just an observation, not an insinuation).

      Also; I should add that I agree that not having a degree is limiting. But I should stress that not having an apprenticeship is limiting. And not having spent your first years learning by yourself in your basement, pulling apart a linux system and toying around with svgalib or such is also limiting.

      All forms of learning are of value, and I dont believe that lack of one of them is necessarily more severely limiting than another. While I do my research and learn the materials I need for a given project, and may have not already encountered a piece of advice I might or might not have received in school, someone who has received the advice in school; might not have spent the years having to figure it out for themselves, either road you take, some compensation for the lack of the alternative road will be required.

      Cheers,
              -Tristan Van Berkom

      PS: If you have more conversations like this, and less about gun control, USA centric political rants, and fussing about SJW stuff; I might one day consider getting myself a username... I expect the user number will be very high right now ;-)

    26. Re:It was worth it by Anonymous Coward · · Score: 0

      That allows the anti-degree people to claim that those with degree are just lying about it and do not want to admit having wasted their time. In actual reality they are simply blind because they lack that experience and they are unwilling to believe otherwise. A Dunning-Kruger type of effect is at work here. Also, as they would have to acknowledge being wrong and possibly being inferior in the relevant skill space, it is quite understandable that many are unable to come to grips with that. Hence they claim "degrees are worthless" and such things.

      That's horrible reasoning - did you not have good classes to teach you critical thinking skills?

      The mere fact that some people do not appreciate their degrees when they first get them does not allow you to conclude anything about the value of the degree - even if people think the degree is valuable after a few years of reflection, you would still have to prove that they are correct in so thinking before you could legitimately conclude anything about the value of the degree. After all, people are mistaken about a lot of things.

      Unfortunately, the publish-or-perish system does tremendous harm to the quality of education. It creates enormous ethical conflicts of interest - and professors are in general no more capable of resolving those correctly than the lawyers or politicians.

      We have many people with degrees from top ranked engineering schools at my workplace - and a common theme in conversations regarding their schooling is that there were (and are) major problems with the higher education system. The consensus is that only a small percentage of professors are really doing their jobs - and students end up largely having to teach themselves.

      To make matters worse, very few professors in computer science are skilled at the art of coding - and it is an art. Many are mathematicians who were offered jobs when universities needed people in the computer science departments, and many of these people still do not understand the differences between the two fields. Both are arts, but the art is different from one to the other - and moving from one to another requires an enormous long term time investment for real skill.

      Other professors - the non-mathematicians - are simply unwilling to invest the time to learn the art of coding, for a variety of reasons, most of which seem to come down to conflicts of interest. Since they also seem unwilling to learn the art of teaching, we actually have two major failures which act to greatly reduce the value of a degree.

      The textbooks (and other books in the field) often have value. Learning from your peers and a good mentor can have a lot of value. But neither of these requires a degree. Dumb people will do coding badly, smart people will figure things out (with the help of many resources beyond themselves). There's just no reason to believe that the degree in and of itself is going to create higher skill or competence at coding than one would get through intelligent use of the available resources.

      Perhaps you've simply been exposed to too many dumb people?

  19. Please use the pound sign. by Anonymous Coward · · Score: 1

    Please use the £ pound sign, or use the exchange abbreviation GBP.

    1. Re:Please use the pound sign. by HxBro · · Score: 1

      the problem is, the Great British Pound has devalued so much, it's no longer great :(

    2. Re: Please use the pound sign. by Anonymous Coward · · Score: 0

      This! How do you even come up with shit like BP? Next time someone will use D for dollars?

  20. seems obvious by Anonymous Coward · · Score: 0

    seems pretty obvious, why do a computer science degree if all you want to be is a coder? that is like doing a forestry degree because you want to work as a tree planter or a mechanical engineering course because you want to work as a mechanic in a car service centre.

    1. Re:seems obvious by gweihir · · Score: 1

      Coders exist on many different levels. Depending on the work, a highly qualified engineer may well be coding his own software.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    2. Re:seems obvious by computational+super · · Score: 1

      why do a computer science degree if all you want to be is a coder?

      "All"? Code is all there is.

      --
      Proud neuron in the Slashdot hivemind since 2002.
  21. In other news ... by Qbertino · · Score: 5, Insightful

    Telescope Builders are often only mediocre Astronomers.

    Big surprise!

    --
    We suffer more in our imagination than in reality. - Seneca
  22. ^^ Not true in most of USA by Anonymous Coward · · Score: 0

    Nomsg.

    1. Re:^^ Not true in most of USA by mrsquid0 · · Score: 2
      --
      Just because you are paranoid does not mean that no-one is out to get you.
    2. Re:^^ Not true in most of USA by MightyYar · · Score: 2

      You don't need to become a PE in the US. In fact, it is highly unusual unless you are signing off on certain documents. I took the exam straight out of school, but in my company of hundreds of engineers only one is a PE - and he works for facilities! So I don't have my PE because there is a apprenticeship requirement that I can't meet. (Technically there is a way around that requirement, but it's simply not worth the effort.)

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    3. Re: ^^ Not true in most of USA by Anonymous Coward · · Score: 0

      "You don't need to become a PE in the US. In fact, it is highly unusual unless you are signing off on certain documents."

      Maybe for computer related work, however, in many traditional engineering professions, a PE is expected, if not required. The difference is often related to work that affects the public.

      As for NSPE, they wanted more members and saw an opportunity with computers, through hardware design, to capture a new field, as did engineering schools.

    4. Re: ^^ Not true in most of USA by MightyYar · · Score: 1

      Yeah, I'm in manufacturing (currently the R&D side, but involved a little more with production in the past when we still made things in the US). Not a PE in the whole building. My dad does civil stuff - they all have PEs. Building guys (structural, mechanical systems, electrical, etc) all have PEs.

      Anyway, the point remains - a PE is above and beyond an engineer in the US. You are still an engineer without a PE, just not a "Professional Engineer".

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    5. Re: ^^ Not true in most of USA by makerfixer · · Score: 1

      Any real world physical impact requires a PE involved. Fire alarms are just big computers and require a PE sign off in the process of design (usually at the initial layout design and sometimes at the shop drawing stage. A PE is a commitment and brings you into a different tier of engineering and professionalism. It is not easy to take or bought, being heavily supervised by other PEs and having the FE and PE exams having pass rates expecting people to fail. Getting the four years of experience in most states is difficult, as is getting character witnesses who are PEâ(TM)s to sign off on you to their possible detriment.

    6. Re: ^^ Not true in most of USA by MightyYar · · Score: 1

      But the point remains - you don't need to be a "Professional Engineer" in the US to be an engineer. They even make the distinction on their own website:

      What makes a PE different from an engineer?

      In the US, only about 20% of engineers have some kind of a professional license (including a PE).

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    7. Re: ^^ Not true in most of USA by Gr8Apes · · Score: 1

      "You don't need to become a PE in the US. In fact, it is highly unusual unless you are signing off on certain documents."

      Maybe for computer related work, however, in many traditional engineering professions, a PE is expected, if not required. The difference is often related to work that affects the public.

      As for NSPE, they wanted more members and saw an opportunity with computers, through hardware design, to capture a new field, as did engineering schools.

      I can attest that a PE is not required unless you're signing documents certifying them and the work they represent for certain entities. Construction and related industries are really the primary driver for PEs, and the majority of engineers working in those industries are not PEs. You only need 1 PE within a company, as long as they have the ability to review and approve the designs, etc. I don't recall running into many PEs in automotive or aerospace related industries, although I am sure there were a few, just given the era that occurred in.

      Most coders are not engineers, whatever their title may say. Most software architects aren't engineers either. And no, having a CS degree definitely doesn't make you an engineer.

      --
      The cesspool just got a check and balance.
    8. Re: ^^ Not true in most of USA by datavirtue · · Score: 1

      Unless you are getting paid...then you are a professional.

      --
      I object to power without constructive purpose. --Spock
    9. Re: ^^ Not true in most of USA by MightyYar · · Score: 1

      Well, you'd be a professional engineer and not a "Professional Engineer", TM, all rights reserved.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    10. Re: ^^ Not true in most of USA by SandWyrm · · Score: 1

      My father was a very good electrical engineer who was never certified. Usually, the companies he worked for would have one or two PEs (usually the owners) that would simply sign off on everyone else's work. It just wasn't worth the cost for all of them to get individually certified.

    11. Re:^^ Not true in most of USA by K.+S.+Kyosuke · · Score: 1

      A straw man. We were talking about the word "engineer" and now you come up with something called "Professional Engineer" that is obviously applicable to a limited number of domains and places (apparently it's about US electricians and such).

      --
      Ezekiel 23:20
    12. Re: ^^ Not true in most of USA by Puls4r · · Score: 1

      He may have worked in a position that called for an electrical engineer - but without a degree, he wasn't. There's a distinction between being in an engineering position and being an engineer. And people who have called themselves engineer but aren't have lost in court over that fact. But hey - in a pinch I know emergency first aid. Guess I'm a doctor.

    13. Re: ^^ Not true in most of USA by Anonymous Coward · · Score: 0

      Right, because there were NO engineers before John Smeaton founded the Society of Civil Engineers in 1771...

  23. Coders, not exactly - architects, yes... by SuperKendall · · Score: 1

    Computer Science degrees aren't supposed to lead to jobs as "coders".

    The thing is, for most people they still do - but what it should help with is getting to some kind of architecture position a bit faster. I don't think most people would want architects that had not done substantial coding though, right? I believe the term we had for that at one place I worked was "Architecture Astronaut" because the were so far out of touch with how real projects worked...

    I do wonder if the huge cost of college these days makes it worth getting a CS degree anymore... but there is a pretty high intangible value to a lot of what you get from a CS degree, so I'd say that answer is probably still yes if you are at all interested in theory.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
    1. Re:Coders, not exactly - architects, yes... by Maxo-Texas · · Score: 1

      Number of senior programmer analysts required at my last place-- 300.
      Number of architects required-- 3 (it was briefly 5-- for maybe 6 months one time).

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    2. Re:Coders, not exactly - architects, yes... by SuperKendall · · Score: 1

      Sure, but that also goes in line with the percentages of developers who actually have CS degrees...

      That said I don't think you have to have a CS degree to be an architect, but that background is helpful and sets you up to be reasonably good at it. As long as you have practical experience to back it.

      --
      "There is more worth loving than we have strength to love." - Brian Jay Stanley
    3. Re:Coders, not exactly - architects, yes... by Maxo-Texas · · Score: 1

      Almost every senior programmer analyst there (all 300ish) there had CS degrees.

      One architect had an architect degree. Two had CS degrees + 15 years experience with the system.

      Maybe it's different out on the west coast.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
  24. Welcome to programming... by Anonymous Coward · · Score: 0

    Almost all employers want you to work long hours and learn all the latest tech on your own time, self-teaching.

    You have to look long and hard for the places with a reasonable work schedule. These places tend to use a bit older technology and value stability and predictability over the latest fad, although there still is some amount of fad chasing there too. You also need a big enough contract that it's not just you and one other guy who are responsible for *everything*.

    1. Re: Welcome to programming... by Anonymous Coward · · Score: 0

      Also, forget quality as an ideal.

      The code has to be high quality WHERE IT MATTERS, and less than pretty is OK elsewhere. Demand perfection and you'll never go home.

  25. Re:Stupid study (35k vs 38k) by angryargus · · Score: 1

    who gets paid in pounds lol

    More like who only gets paid 5 figures in pounds, euros, or US/OZ/NZ dollars? The results talk about 35k vs 38k when the starting base salary for a new grad in Silicon Valley is at least 6 figures. Apparently location is roughly an order of magnitude more important than this survey's concern about a degree.

  26. I've got karma to burn by rsilvergun · · Score: 1

    so I'm gonna ask: If we know a CS degree is a poor return on investment doesn't that put it in the same boat as a liberal arts degree? e.g. something you do for fun that you probably shouldn't have?

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
    1. Re:I've got karma to burn by Antique+Geekmeister · · Score: 2

      If I may disagree? A CS degree may be a poor return on investment, but it generally _has_ a measurable and positive return on investment.

    2. Re:I've got karma to burn by Anonymous Coward · · Score: 0

      What is the difference between a research mathematician and a large pizza?

      A large pizza can feed a family of four.

      People who pursue these types of degrees (usually) don't do so for the sake of financial gains. It's for the love of the material and for the skills your earn along the way.

      And what do you mean by saying you "probably shouldn't have" a liberal arts degree?

    3. Re:I've got karma to burn by udachny · · Score: 0

      Did you take into account student sebt?

    4. Re:I've got karma to burn by micahraleigh · · Score: 1

      If snails can move does that put them in the same boat as a cheetah?

      If it's a really, really big boat.

  27. Math by Tony+Isaac · · Score: 1

    Well, I have a computer science degree, AND a math minor. I detect a math problem here.

    Average salary with degree: 38,000
    Average salary without degree: 35,000
    Difference: 3,000

    Cost of a degree (according to the article): 50,000
    Divide 50,000 by 3,000, and you get 16.67.

    So in 17 years, a degree DOES pay for itself, even if one accepts all the numbers as fact.

    1. Re:Math by bugs2squash · · Score: 1

      they pay back 9% of everything they earn over 21k. all remaining debt is cancelled after 30 years. So ignoring wage inflation and government rule changes, they'll only pay back 45,900 and inflation will take a bite out of the real value of that.

      In other words, they'll earn 3k extra and their degree financing will cost them 1530 so they are 1470 up on the deal every year.

      Now if you assume they could have been earning 35000 per year instead of attending university then that opportunity cost starts them $105k in the hole - they'll not see that back

      But there are a lot of assumptions there, and actualy getting a degree is life changing and fun in its own way

      All in all I'm glad I did it

      --
      Nullius in verba
    2. Re:Math by Anonymous Coward · · Score: 0

      Don't forget that the non degree worker gets 4 years of salary before the graduate gets income, so its not a 3,000 difference,

      the college graduate must make up the cost of 50k tuition + the 4 years of lost wages. 50,000 + 4*35000

      That's 190k to make up.

      At a difference of 3k salary per year, that is now 190,000/3000 = 63 1/3 years.

      So the degree DOES NOT pay for itself...
      Sorry man... but you are incorrect.

    3. Re:Math by Hognoxious · · Score: 1

      Pity you didn't take Economics as a minor. You might understand things like discount rates/time value of money and opportunity cost. Then you wouldn't make such an ass of yourself.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    4. Re:Math by swilver · · Score: 1

      A 17 year return on investment, wow, where can I sign up?

    5. Re:Math by Tony+Isaac · · Score: 1

      Do you believe the numbers? Only £39,000 a year average for programmers with college degrees? That's about 54K US. It only took me 4 years out of college, in the 80s, to make 54K, and it only went up from there. These days, you can make 54K immediately upon graduating.

      Despite the hype, AVERAGE US college tuition is still only about $9,000 per year. I suspect that the real ROI is greater than purported by the article.

  28. CS = Software Developer/Engineer by Anonymous Coward · · Score: 0

    A computer scientist is assumed to be able to write high-quality software. But to them, that is just a tool - a means to an end. They aren't just trained to solve problems like "I need a C function to parse user strings". They solve problems like, "I'm thinking of using this new locking structure. Could you quick check it for possible deadlocks. Also re-implement it efficiently using hardware primitives." Or perhaps "So we just produced an algorithm for solving X. Check it for correctness and do a running time and space analysis." Maybe something like "so our kernel's TLB will use a given data structure. Is this a good choice? What are the performance implications? How much space will it occupy in memory? Can we improve it?". Or "We need you to do an audit of our proprietary compiler for possible performance/security issues."

    Also more specialized problem areas like graphics, machine learning, programming languages, theory, optimization.... These areas are not for the mere mortal. These problems are reserved for the computer scientists.

    So you see.... a computer scientist isn't a software developer. A computer scientist is a mathematician who specializes in discrete math, logic, and mostly abstract problem solving. If your university taught you anything less, you were short changed.

  29. So do liberal arts degrees by rsilvergun · · Score: 1

    just as the ex-CSO of Equifax. She did pretty well for herself until something major blew up on her watch. And I've known lots of PMs making 6 figures with liberal arts degrees. Often being good at talking your way into a job is worth more than being able to do the job.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
  30. Project Euler by Anonymous Coward · · Score: 0

    https://projecteuler.net/

    THESE are the problems computer scientists are trained to solve. But also they are trained in modeling. As in, taking a "real life" problem and framing it in something resembling a problem for project euler.

  31. I'm no math wiz by Anonymous Coward · · Score: 0

    But if the average college grad makes 3,000 more a year and had to pay 9,000 a year for 4 years that = ROI of 12 years. That may be bad but if you plan on working in a field for 12 years + it seems like a no brainer to me. This is assuming of course that you are working while going to college which I've done and is a breeze.

    1. Re:I'm no math wiz by Anonymous Coward · · Score: 0

      A coding career only lasts 12 years, then you get fired and never find work again. So a degree is still a bad deal since you can only hope to break even before you become too old.

  32. Re:Computer Science is Completely Worthless by Anonymous Coward · · Score: 0

    A job meeting your qualifications: Sit down @ a stall in a local gaybar lavatory & open "Jowie's suck service" - you will make the MOST INCOME you've ever made + you'll love your work!

  33. Re:Computer Science is Completely Worthless by Anonymous Coward · · Score: 0

    I knew I should have majored in cocksucking to get ahead.

    Still no jobs for computer science graduates.

  34. Re:Computer Science is Completely Worthless by Anonymous Coward · · Score: 0

    In other fields you suck it too. Get real. Suck is what you do. You suck at computers so try use your skills as suggested.

  35. Re:Computer Science is Completely Worthless by Anonymous Coward · · Score: 0

    On the contrary, you condescending piece of shit. I'm great at computers. I've written plenty of software and I've debugged even more. I've coded open source projects, and I've submitted patches to open source projects. No, you fucking turd, I what I suck at is sucking.

    Every time I interview, on those rare occasions some moron with a job decides to abuse the jobless to fill an interview schedule, every moron always chants the same fucking thing every goddamned time: "soft skills, soft skills, soft skills, soft skills, soft skills, soft skills." Hard skills aren't fucking good enough for you scum! Well fuck you! My hard skills just keep getting better and better as I learn more hard skills. Still not good enough for you scum.

    Soft skills, soft skills, soft skills, how the fuck would I ever learn soft skills when the only time I ever talk to anyone is when some moron invites me to a job interview to reject me for soft skills.

    Well, you know what, asshole? FUCK!! YOU!!

  36. Not making less due to paying back the loan(s). by Athanasius · · Score: 1

    We can do better than that. Any recent UK graduate who took out the loans for going to Uni will be paying it back directly from their wages. You can use a site like https://listentotaxman.com/uk-... to work out what this means for their income.

    If I put in 35k without any student loan it comes out to 27,081.48 per year (2,256.79 pcm), after all deductions. For 38k with the 'Plan 1' (higher %age paid back per month) student loan repayments it comes out to 27,301.23 per year (2,275.10 pcm). Note that the amount taken out in loans doesn't affect how much is paid back per month, that's purely based on how much you earn over certain thresholds. And these loans are forgiven after 30 years if not already paid back. It's more like a tax targeted at those who took the loans in return for the education.

    So the 'coder' with the degree and loans to pay back just barely makes more money on that median salary. Mostly my point is that it's not like they're netting less due to loan repayments.

  37. Re:Computer Science is Completely Worthless by Anonymous Coward · · Score: 0

    Hahaha. Got a rise out of you. You're projecting. Software you ought to write is automating "Jowie's suck service" (lmao) & incorporate it (Boston Dynamics = good choice). We have no doubt of your hard skills hahahaha! Arduino and servos is another (lol).

  38. Re:Computer Science is Completely Worthless by Anonymous Coward · · Score: 0

    Kill yourself.

  39. Re:Computer Science is Completely Worthless by Anonymous Coward · · Score: 0

    RoTfLmAo https://developers.slashdot.org/comments.pl?sid=11141491&cid=55236697/ & just think: YOU could've been rich!

  40. Re:Stupid study (35k vs 38k) by Anonymous Coward · · Score: 0

    Most new UK graduates working in this field won't be getting £38k either. Outside London a senior software engineer wage tends to top out at £50k, or around $65k at current exchange rates.

    Anyway, I don't understand the article as £3000 is about £2000 per year, meaning that there is a return, meaning student debts coukd be cleared using that extra alone in twenty years.

  41. Re:Computer Science is Completely Worthless by Anonymous Coward · · Score: 0

    Disrupt the fleshlight industry with your innovative suckbot. You forgot to mention how suckbot will be controlled by a shitty app. Fuck you, millennial hipster troll.

    No what I should do is build a killbot to kill your fucking ass.

  42. Get rid of the guest workers. by edgedmurasame · · Score: 1

    Remove an avenue of fraud/abuse and you might see a bit more value in that direction.

    --
    "Forget the engineers." -Carly Fiorina, briber of MIT Technology Review.
  43. Re:Computer Science is Completely Worthless by Anonymous Coward · · Score: 0

    Easier to do than you think. Superior product, rules. Fact alongside it makes it so. I squash advertising + malware this way & above all - give the consumers what they ask for (more than want). Has to create a need. You = guaranteed wealthy @ some point.

  44. Hmmm.... by The+Cynical+Critic · · Score: 1

    Well that's a bit odd seeing how when I put in my situation, a CS equivalent degree with one year of full time experience post graduation (didn't include the year of full time employment I got before graduating), into the StackOverflow salary calculator released a few days ago the calculator gave me an average salary of 54.000 GBP. Contrast that with the 35.000 GBP salary (which isn't too far off from what I'm actually making here in Finland) being reported here and I get the feeling that either the calculator is badly overestimating salaries or then salaries in the London area are way higher than in the rest of the U.K (which I guess is possible having heard of how expensive it is to live there).

    --
    "Why should I want to make anything up? Life's bad enough as it is without wanting to invent any more of it."
  45. when coders don't have a broad understanding by Chrisq · · Score: 4, Funny

    A degree guarantees a broad understanding of computing related issues. Of course some people without a degree may have this, but these are a few of the things I have seen:

    A business rule that had been modified a number of times by requests from the business; "do X when Y", "do X when Z but not A", "Assume A is false when not Y", and so on for many years. The result was a huge condition with brackets that could not easily be understood. Writing it as a boolean expression and simplifying it revealed that several of the variables in the conditions were not relevant (it did the same thing when they were true or false), much of the complexity was because some test was being applied in multiple conditions and the whole lot simplified down to a short clear expression.

    A coder had produced a phenomenal amount of code, counted by lines. In peer review it turned out he didn't understand how to call library classes, and copied the library code into every module which used it

    A coder defined a macro defining the boolean "or" "|" as "and"! It turned out that he was totally confused by an expression opening a file as F_READ | F_WRITE, and thought that the compiler writers and everyone else in history had got "or" and "and" the wrong way round.

    A definition which was obviously a finite state machine written as spaghetti code, where all that was needed was a table of state, event, action, new-state

    This is a legend in our company. An Array copy function defined, despite one being available as
    # This function only works on arrays up to size of three elements
    A[0] = B[0]
    if (B.size > 1)
    A[1] = B[1]
    if (B.size > 2)
    A[2] = B[2]
    if (B.size > 3)
    A[3] = B[3]
    And yes, the language had loops and a built-in array copy function.

    1. Re:when coders don't have a broad understanding by Anonymous Coward · · Score: 0

      It doesn't guarantee shit. Even PhDs (and in fact, they more often than not) can write horrendous code that only happens to work by sheer luck.

    2. Re:when coders don't have a broad understanding by gweihir · · Score: 1

      Yes, I have seen numerous similar things from non-degree coders as well.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    3. Re:when coders don't have a broad understanding by gweihir · · Score: 1

      Not having that degree basically assures really bad coding, in more hidden form for the smarter non-degree coders. The converse is not true, i.e. a degree does not assure good code.

      That you apparently do not understand the direction of the implication is a pretty sure sign you are one of those without a degree.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    4. Re:when coders don't have a broad understanding by Drethon · · Score: 1

      Yep, good computer scientists need very broad understanding of software development. Unfortunately many companies prefer a very specific understanding optimized to the current job and dropped as soon as the job is complete for someone else with a very specific understanding of the next job.

    5. Re:when coders don't have a broad understanding by Anonymous Coward · · Score: 0

      I've seen similar from people with masters degrees in CS, too. Bad programming skill sadly doesn't disappear with additional education.

    6. Re:when coders don't have a broad understanding by Anonymous Coward · · Score: 1

      No, they're just not that closely correlated. A degree does not mean good development skills (coding or other), nor does not having one imply low-skills, either. That you infer a lack of a degree means lack of ability simply means you're an idiot.

    7. Re:when coders don't have a broad understanding by Attila+Dimedici · · Score: 1

      A business rule that had been modified a number of times by requests from the business;

      And right there is where you are misunderstanding this. Not only was the rule changed a number of times, but the programmer was almost certainly asked to implement the change on the fly ("We need this new rule in place by Monday."). Further they were almost certainly never given the time to go back and fix the kludge they had created to get it out the door ("Why are you working on that? It works. We have this other project that we need finished. Work on it. You can go back to that later.")

      And, BTW, needing the new rule in place by Monday was often a real requirement, failing to meet that deadline might cost the company significant fractions of their yearly revenue.

      --
      The truth is that all men having power ought to be mistrusted. James Madison
    8. Re:when coders don't have a broad understanding by gweihir · · Score: 1

      No. But really bad programming skills are much, much more prevalent without that education and many of those without that education think they are actually pretty good at what they do when they are anything but. That is a serious problem and it becomes worse when these people move into management.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    9. Re:when coders don't have a broad understanding by gweihir · · Score: 1

      Says the AC. Alternatively, I have seen a lot of the field and noticed said strong correlation you would like to wish away. My guess would be you are one of those that lack said degree and are desperately trying to cover up the problems in your skill-set that cause. Not that over-inflated sense of ones own skills is rare among students. But they do run into an enforced reality-check: Exams and thesis work. Self-taught coders do not have that benefit and routinely massively overestimate their skills.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    10. Re:when coders don't have a broad understanding by Anonymous Coward · · Score: 0

      Yes, I've seen these sorts of things too.

      Problem is, I've seen them from people -with- CS degrees as well.

      Having a CS degree doesn't guarantee anything other than you know how to school, as is the case with any non-doctorate degree (or specialty like medicine or law - and hell, we all now crappy doctors and lawyers too!). That said, better to go through the degree experience than not because it TENDS to help, I'd agree with that statement. But it's not a guarantee, just like NOT having a degree isn't a guarantee that someone doesn't know what they're doing.

    11. Re:when coders don't have a broad understanding by Anonymous Coward · · Score: 0

      Employed programmers get the same feedback - it's called keeping a job, and having to clean up whatever messes your inexperience cause. There are bad developers at all levels, and education doesn't fix it. I have probably seen quite a bit more of the field than you have - I've got 40 years employed, and yes, I still write code. And probably make quite a bit more than you do.

    12. Re:when coders don't have a broad understanding by Anonymous Coward · · Score: 0

      Your comment, "Not having that degree basically assures really bad coding", flies directly in the face of what the OP wrote, "some people without a degree may have [...] [a] broad understanding of computing related issues." Are you sure you want to add rude criticism to that? Are you _really_ sure? That's not a good look, man.

    13. Re:when coders don't have a broad understanding by Anonymous Coward · · Score: 0

      Having a CS degree doesn't guarantee anything other than you know how to school

      This. College basically teaches you one thing: how to jump through hoops. If you manage to learn something while jumping, consider yourself lucky.

    14. Re:when coders don't have a broad understanding by Chrisq · · Score: 1

      A business rule that had been modified a number of times by requests from the business;

      And right there is where you are misunderstanding this. Not only was the rule changed a number of times, but the programmer was almost certainly asked to implement the change on the fly ("We need this new rule in place by Monday."). Further they were almost certainly never given the time to go back and fix the kludge they had created to get it out the door ("Why are you working on that? It works. We have this other project that we need finished. Work on it. You can go back to that later.") And, BTW, needing the new rule in place by Monday was often a real requirement, failing to meet that deadline might cost the company significant fractions of their yearly revenue.

      Really, how much longer would it take to write it out in boolean algebra and simplify it? Ten minutes perhaps. If you don't what are the chances that your change won't apply in all circumstances that it should and none that it shouldn't? You could easily spend longer if it fails tests. If you are suggesting that applying a change to an expression that you don't understand is the best approach to editing a business rule that could cost the company a significant portion of their revenue then maybe you should have gone to college.

    15. Re:when coders don't have a broad understanding by Attila+Dimedici · · Score: 1

      You are assuming that the person had ten minutes to spare and/or that this was the only change needed before the deadline. I am not a programmer, but I shared an office with one.

      Further, when I started my current job, the people running the IT Department were big believers in degrees. One of them was just finishing his Masters degree. Shortly after he finished it we had a Departmental team building meeting where the alcohol flowed freely. He griped about how throughout his Masters degree studies they spent a lot of time making sure that students thoroughly understood a particular approach, one that he said no one actually used anymore, while at the same time barely mentioning the approach that everyone actually uses. He interacted with numerous vendors, that interaction was his basis for his claim.
      As a general rule I will take the guy who learned it by doing the job over the guy who learned it in the classroom every day.

      --
      The truth is that all men having power ought to be mistrusted. James Madison
    16. Re:when coders don't have a broad understanding by gweihir · · Score: 1

      Well, first invalid "ad Hominem" argument, because you have no idea how long I have been doing this or how much I make. Also, salary is not necessarily related with skill. The problem with employed coders is that they are in a filter-bubble. If an employer only hires/bad cheap coders, he will never see what actually good ones can do. In such environments, still pretty terrible people can rise to the top and be regarded as really competent. I have seen it happen more than once.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  46. Ummm by Anonymous Coward · · Score: 0

    'BP' is British Petroleum. You meant GBP. Or you could just say £.

  47. H-1B outsources education and reduces real growth by SysEngineer · · Score: 1

    In the 1980 America outsourced manufacturing over seas. Now, the H-1B program is the outsourcing of education. The loss of manufacturing jobs has created social unrest, just think what the loss of education will do to developed countries. But not only is it bad for the people, it is bad for the economy. GDP is calculated as C + G + I + (E - M) where M are imports. As we bring is H-1B workers that imports both Labor and Knowledge reducing the GDP. And Solow's growth model is Growth = is a function of both Labor and A(knowledge). Again H-1B program reduces real growth by reducing real labor and knowledge with imported labor and knowledge. Growth is now a function (L -import-L, A - import-A). And most companies want code monkeys, someone that does not have a broad range of computer knowledge but know how to do one thing. With higher education costing so much, the student debt make it hard for native computer majors to compete. Nike in Beaverton Oregon is laying off 800 people, but still hiring H-1B workers.

  48. True. by Anonymous Coward · · Score: 0

    That's why get a degree in Software Engineering instead.

  49. Currencies by Hognoxious · · Score: 2

    BP my arse.

    "pounds sterling", "GBP" (that's the ISO code) or just plain old "pounds" are all acceptable.

    You could use the symbol (the one that looks like a curly L, not the one like a sharp sign), but slashdot would probably convert it to [(*Ä*)] or something.

    Chunter chunter comprehensives chunter chunter Wilson.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    1. Re:Currencies by Anonymous Coward · · Score: 0

      Maybe they were going for "Brexit Pounds"?

    2. Re:Currencies by Anonymous Coward · · Score: 0

      what do you have against British Petroleum?

  50. On the minus side by gweihir · · Score: 4, Insightful

    Once, management finally realizes to that coders without a degree are in most cases actually far more expensive due to lack of skill and limits in what they can do, those without that degree will find themselves unemployed pretty fast and pretty permanently. The funny thing is that the coders without degree do not realize what they miss. Sure, as long as it is simple business logic, almost anybody could do it. But as soon as it gets more complicated, I have yet to find a coder without CS degree that actually gets it and that is really expensive in the long run.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    1. Re:On the minus side by swillden · · Score: 1

      I have yet to find a coder without CS degree that actually gets it and that is really expensive in the long run.

      I know a few. I know one who doesn't even have a high school diploma

      But the thing is, in order to be a really competent programmer without a formal education you have to get equivalent education informally, meaning self-education. In theory, it's possible for anyone to learn anything on their own. In practice, it's a lot of hard work, and relatively few people have the gumption to do it. In my experience, the only successful autodidacts are extraordinarily brilliant, and they're really, really rare.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    2. Re:On the minus side by FlamingGuts · · Score: 1

      That actually gets what?

    3. Re:On the minus side by Anonymous Coward · · Score: 0

      They're no more expensive than their degree-holding compatriots, once they've attained a few years experience. Frankly, once you have 5 years or so in the field, the degree is rather pointless, since the field changes so quickly. CS degrees exist to get you a job coming out of school; at 5 years in, what you've done since school is far more important. Many of the best developers I've worked with (at ALL levels) didn't bother with a CS degree (in many cases, they had no degree at all). And my career has included a great deal of work that wasn't "simple business logic".

    4. Re:On the minus side by gweihir · · Score: 1

      I agree to that. These people do exists but their number is very, very small. The number of people that falsely believe they are one of these exceptional people is pretty high though.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    5. Re:On the minus side by gweihir · · Score: 1

      If you have to ask...

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    6. Re:On the minus side by gweihir · · Score: 1

      Bullshit. And Bullshit again. These developers you think are "the best" are just an example form the class of people that screw more complicated things up badly and then people like me have to come in to fix it. I see this time and again. Oh, sure, some actually manage complicated things from time to time, but they do not really understand what they are doing and they take really long too do it and in the end their solutions quite often cause significant problems down the road. Of course, that happens with people with CS degree as well. But it is basically assured for those without as they do not have a reasonable overview over the CS field.

      The advice to prospective employers these days must be a) do not hire people without a relevant degree and good grades b) look very carefully at all others. The average level of skill of today's coders is shockingly low and coders seen as really competent by their co-workers are often still pathetically incompetent (even if still above average).

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    7. Re:On the minus side by swillden · · Score: 1

      I agree to that. These people do exists but their number is very, very small. The number of people that falsely believe they are one of these exceptional people is pretty high though.

      Classic Dunning-Kruger effect.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    8. Re:On the minus side by Anonymous Coward · · Score: 0

      You think there will come a day when "management finally realizes" something?

      Look, "management" is not one set of people: it's a whole revolving roster of people, mostly with random degrees quite unrelated to management or the industry they're in. The day a manager finally "realizes" what you want them to, it's odds on they've already left the company anyway. And their replacement has got it all to learn over again.

      Don't wait for it to happen. Do something about it.

    9. Re:On the minus side by jeff4747 · · Score: 1

      Once, management finally realizes to that coders without a degree are in most cases actually far more expensive due to lack of skill and limits in what they can do, those without that degree will find themselves unemployed pretty fast and pretty permanently

      One of the things you get when you don't work within your degree is having to analyze how things work instead of relying on what you were taught about how things should work.

      Companies are spending a fortune fixing the output of H1B/offshore developers. Much more than what they spent using onshore developers and getting it right the first time.

      What should happen is companies abandoning these developers that turned out to be much more expensive in the long run. What actually happens is even more reliance on H1B/offshore developers. Because management doesn't want to admit they were wrong, management is rewarded more for the low up-front cost, or management has another agenda (such as driving overall wages down).

      Same with degrees versus non-degrees. Management is not going to abandon non-degree developers anytime soon, because it's not quite as straightforward as you seem to think.

  51. LOL by Anonymous Coward · · Score: 0

    Heh, heh, computer "science."

  52. What subjects define CS? by helga+the+viking · · Score: 1

    I don't know there are a lot of assumptions about what is CS degree, its probably different now. Eg: version control software, mobile phones+software development were not in the course.

    This was my CS degree in a nutshell from early 2000's. The Software engineers did 80% the same subjects.

    There were plenty of electives: eg: i could add subjects for math, ethics, or neural networks, video games, social-science, electrical engineering, operating system design and probably few more.

    1st year undergrad:

    *Some sort of introduction to SWE: usually java/c++ (or both).

    *Some sort of SWE #2 course. (bring in the algorithms, more Object Oriented concepts)

    *Discreet maths.

    *Ethics course.

    *Basic start on Web stack, usually the fundamental ideas of networking + HTML, CSS, Javascript.

    *Basic EE logic gates, basic components of computers.

    2nd year undergrad:

    *Introduction to graphics course, rasterise objects how frame buffers work, bottom up understanding of graphics and some specific low-level graphics programming.

    *SWE #3 course: more algorithms, more on how to tackle problems transforming requirements into code.

    *Database theory, learn one of the major DB systems out there. SQL.

    *Formal modelling of logic for critical areas of the code (where an error could cause physical harm to someone).

    *Computer architecture intro: how IO works, how compilers work,assembly language.

    *Algorithms course, Big/little Oh, Turing, types of computation, many may algorithms, new and old, fast and slow. Build your own.

    *Ties together full web stack for writing deploying web pages. server side/client side, setting up a web server, security, was basically LAMP plus multiple physical computers/load balancing/fail safe.

    3rd year:

    *SWE #4, The big software project: Working in teams, development paradigms, writing code with other people, documentation at a professional level. (Usually went into another part of the Uni and helped another field eg: write medical software/bioinformatics)

    *Comparative languages. A variety of languages eg: scheme/lisp stuff through to perl, python etc.

    *Concurrent programming: fine-course grained parallelism, threads, breaking apart problems to make them concurrent, debugging, signals/semaphores, the tradeoffs.

    *Compiler design: write a compiler, design a language.

    *3d computer graphics course. Basically understanding stuff the the level of quake video game. Build a 3d engine.

    *All the security/software vulnerability, history of malware, almost up the the point how to write a virus/virus scanner/. Test code for security issues.

    *Machine Intelligence, theory of AI, neural networks, use machine learning to solve a problem + integrate into a SW project.

    What is the CS degree like now?

    I think the register article is looking at a very narrow requirement which could be satisfied by non-degree but that misses the point.

    You could train for job X and just follow the branches off a tree of skills that fit exactly what job X requires. Juxtapose that to CS/Engineering degree and its the whole gaumut/scope of that field. Its the platform on which you stand to THEN specialise to fiat any such job.

    The larger issue is as long as there is involuntary employment with the inherent instability of market based solutions you're guaranteed to have a 'working' skills shortage. The graduate is not enough because the company does not want to take a graduate and develop their skill into the specific tools set instead they want a ready made person who by sheer coincidence uses every little tool they currently develop software with.

  53. But why is that? by Anonymous Coward · · Score: 0

    London is swimming in finance money, right? Why such low salaries? Eastern European immigrant labor? What's the deal?

  54. What is 'BP'? by Anonymous Coward · · Score: 0

    Do they mean £ ?
    Or 'GBP' if you really have to? The Great British Pound is never referred to as 'BP' - except in Slashdot, of course...

    Sorry - 'Climatedot'.

  55. The UK broke their colleges too? by sabbede · · Score: 2
    50,000BP of debt for 3000BP more a year? I know college in the US is increasingly expensive and decreasingly useful, but I didn't know the UK had the same problem.

    I guess it's good to know it isn't just us, but it's also sad to know it isn't just us.

    1. Re:The UK broke their colleges too? by DanJ_UK · · Score: 1

      No, we didn't, the article is complete and utter tripe in every sense from the use of BP to refer to 'G'BP currency right the way through to the alleged devaluation of a degree here.

      Several of the top 10 universities in the world have and will always remain here, Oxford / Cambridge / Imperial / UCL et al.

      Also, I don't know a single software engineer here that doesn't earn over £100k+, so that's another bullshit argument.

      --
      - Dan
    2. Re:The UK broke their colleges too? by Anonymous Coward · · Score: 0

      Yeah, we got really screwed over the last 20 years.

      My brother started university in 1997, paid no tuition fees, had a government grant towards living expenses and left university with less than 5,000 GBP in debt, and that was mostly due to spending his grant money in the student union bar.

      I start university in 2000, paid tuition fees of about 1,000 GBP per year, had no government grant and graduated with 12,000 GBP of debt, despite working part time jobs and taking a paid corporate placement year (total earnings over my degree course were about 20,000 GBP over 4 years). I finished paying that debt off in 2013, and the interest rate on it peaked at 2.5% APR (it was originally pegged at 0.5pp over Bank of England base rate, but they bumped it up in 2007 I think)

      A student starting university this year will pay tuition fees of just under 10,000 GBP per year, gets no government grant and will graduate with between 40,000 and 50,000 GBP in debt. That debt will have a starting interest rate of over 6% APR, and will only increase when the base rate goes up later this year. They will never pay off these loans, and the arrangement with the Student Loan Company (a terribly managed private company that issue the loans) means that in 2065 the government at the time will have to pay off the outstanding debt as this generation of graduates hit 65.

      The Labour government that came in to power in 1997 with Tony Blair as PM basically screwed the country over to save money in the short term. They basically punted the problem of paying for the increase in student numbers (they had an campaign pledge to get 50% of school leavers to go to university) 47 years into the future.

    3. Re:The UK broke their colleges too? by Anonymous Coward · · Score: 0

      Also, I don't know a single software engineer here that doesn't earn over £100k+, so that's another bullshit argument.

      Ahh, you live in the central London microcosm. No-one outside the M25 is earning that much as a software engineer. In Berkshire/Hampshire you're looking at £40k for a regular level engineer, and £60k for a senior. In the West Midlands, you're looking at £30k and £40k respectively.

    4. Re:The UK broke their colleges too? by sabbede · · Score: 1
      I would have used "£", but my keyboard doesn't have it so I just followed the article. I did think something seemed odd about that, but I couldn't put my finger on it.

      But I don't think you followed my meaning about "breaking college". Yes, the UK has some of the top universities in the world. The US has most of the rest. Apparently in both cases the cost of attending has skyrocketed and the benefits from attending have been declining.

      Now I can't speak to much about the UK's system, but in the US we're sending people to college who shouldn't even have graduated high school (don't meet basic standards), and those that do graduate come away with a degree that ends up only being worth what a high school diploma was worth in the 80's. They end up in jobs that you don't need a degree to get (or didn't until college turned into the place you finished high school), with massive debt that puts them at a permanent disadvantage.

      We broke college by trying to send everyone, regardless of whether they were qualified to go, driving up demand far too fast for supply to keep up. Naturally, this drives costs waaaaay up, and drives quality down. I could go on for a while, but I have work to do. Work that, like 75% of college graduates now, has nothing at all to do with my degree.

    5. Re:The UK broke their colleges too? by DanJ_UK · · Score: 1

      To be fair, the cost of tuition fees going up is the reason the system hasn't broken, yet; it inevitably will though because the nature of the student loan system and the way that it works in this country is ridiculous an unsustainable.

      I don't particularly care though, the UK is killing itself with Brexit and a host of other stupid things at the moment.

      --
      - Dan
    6. Re:The UK broke their colleges too? by sabbede · · Score: 1

      You could still be talking about the US system. Student loans went from helping students afford college to helping college be unaffordable without taking out a mortgage on one's future. It wouldn't were it not coupled with a misguided social agenda that sees college as a way to erase inequality as if it magically made everyone smarter for attending, and used as a way to cover up the failures of the primary and secondary education systems. If a high school can say that 50% or more of their students go on to college, it looks like they're doing a great job even though the students can't read. The colleges provide "remedial" classes, at full price, to cover up the fact that the incoming students weren't qualified to graduate, let alone move on to college. If half of them flunk out, that's fine. The college made a bundle, the lender makes a bundle, and the high schools still get to fake their numbers.

    7. Re:The UK broke their colleges too? by DanJ_UK · · Score: 1

      I'm Scottish but have spent my life in London and other EU countries after my child years in Scotland, I regret not moving back up to Scotland to do something in applied sciences and to take advantage of having zero tuition fees for higher education. People in England / Wales have to fork out a debt that will take them 20 years to pay off. Personally I skipped it and paid privately myself whilst working, it's been a lot of work and I don't think I really learnt anything more than I've learnt from pure work experience in my field. I think it would have been quicker to develop my experience in my field with that initial degree though but I don't think that applies to everyone.

      --
      - Dan
  56. Wrong question by Anonymous Coward · · Score: 0

    Programming can be learned either in school, or by personal study.
    On average, school may make a more complete understanding, but at the edge of the distribution there are some outstanding folks who learned on their own.

    This study assumes that each person can learn either way and it's just a matter of cost to get to a job.
    The proper question is how many of the schooled programmers could/would have figured it out on their own?
    My guess is that once you remove the outliers, you would have a lot of table waiters instead of programmers if you took out school.

  57. Re:Computer Science is Completely Worthless by Ash-Fox · · Score: 1

    I have multiple computer science degrees, and I have applied to thousands of job openings. The number of offers I have received in my entire career is the number zero.

    My company has many openings, but we want certifications of practical work, not computer science degrees. Computer Science degrees are for research institutions, that also expect you have degrees in mathematics and the sciences, possibly an engineering degree too.

    Fuck you lying sacks of shit who claim anybody ever gets paid anything. Expected salary is zero, and return on investment is negative.

    I never fell into this trap because when I finished high-school, I called up various company recruiters for jobs I wanted in the future and told them that I don't have any qualifications or such right now, just finished school, but I will go do the courses/training they're looking for. I got told to do CCNA, MCSE etc. No university work. I did about 2-3 months of studying various certifications, it took about another month for my certifications proper to come in and I got into the industry instantly after that, no problem.

    Computer science is a dead field, you goddamed lying trolls. Fuck you!!

    No it isn't. you just didn't go to the institutions that want it, nor did you get all the per-requsits necessary for it that I noted above.

    --
    Change is certain; progress is not obligatory.
  58. That's because most often CS is the wrong degree by jeff4747 · · Score: 3, Insightful

    The vast majority of the time, you don't need a CS degree to write a business application. These days it's mostly CRUD operations using some web stack and database, governed by some business logic. You don't need a CS degree to effectively do that.

    We need to take a lesson from the material world. We have materials scientists who invent new materials and do some engineering when an extremely deep understanding of the underlying physics and chemistry is needed. But 99% of the time, a structural engineer is the one who designs how to build a building/bridge/whatever. And typically that structural engineer has a much better understanding of how to put the pieces together in a far more practical way.

    We should be aiming for a similar split in computers. We need computer scientists who advance what computers can do and deal with very hard problems. But the vast majority of the time we need a software engineer to assemble what the computer scientists invent into a business application that is secure and just keeps working even when the shit hits the fan.

    For example, a computer scientist would generally not need to worry that much about things like failover and automatic recovery since they're primarily building prototypes and testbeds. Just like a materials scientist doesn't spend much time considering "what if a hurricane struck my lab during this test?".

    But a software engineering degree could focus a great deal on writing software the just keeps working in very adverse conditions just like a structural engineer has to consider a natural disaster striking the building.

    Over my 20 years doing this, I've come across a lot of very elegant systems that are wonderful computer science....and they instantly exploded as soon as they had to deal with something slightly outside what the developer considered.

  59. Longevity, Upward Mobility? by smithmc · · Score: 1

    I wonder how well the degreed developers do vs. the non-degreed ones, when it comes to career longevity, opportunities for advancement to lead or management positions, more deeply technical positions involving system architecture, etc. Computer science isn't all about coding JavaScript.

    --
    Downmodding is the refuge of the weak. Don't downmod, make a better argument!
    1. Re:Longevity, Upward Mobility? by swilver · · Score: 1

      I'm 42, no college degree, started programming at age 12, learned several assembly languages and C before finishing high school, got a job at age 20 for some helpdesk company, worked there for 9 years, then went freelance working at a dozen companies over the last 13 years (which means I seen quite a few different ways of working).

      I now still earn about 150k/year doing what I love (programming, mostly Java nowadays), which is easily double of salaried employees with the same skills. I mentor other developers and am usually the lead on the project (it depends on if I'm working with a team of less experienced developers or a team of peers).

      This is in europe.

    2. Re:Longevity, Upward Mobility? by jeff4747 · · Score: 1

      Anecdotally, the degree doesn't matter much after a few years of experience.

      After 5 years or so, the practical part of the degree is obsolete. The abstract parts aren't, but the abstract parts are also not that hard to learn well enough to be a good developer. Since both the degree holders and non-degree holders have to effectively teach themselves a new degree's worth every few years, the differences should get smaller over time.

      Though part of that is in order to stay in the pool takes a fair amount of effort, with or without a degree. There's going to be a fair amount of self-selection via people no longer writing software.

      But I have not seen any statistics to back this up.

  60. Correlation != Causation by Anonymous Coward · · Score: 0

    Thing is, the people who got jobs as developers without a degree are a subset of driven and talented programmers. Those with degrees on the other hand include some people who aren't as good but the degree helps them get their foot in the door anyways. The guys with no experience and no degree have to be the able to really demonstrate skills to get an entry level position.

    Its not as simple as "degree not worth it"

    1. Re:Correlation != Causation by DanJ_UK · · Score: 1

      ...and this is the case with most professions, degrees open doors, doesn't mean you're going to be good at the job.

      --
      - Dan
    2. Re:Correlation != Causation by Anonymous Coward · · Score: 0

      Driven and talented people who got degrees aren't any good. You just know they got degrees because they weren't good enough to get jobs. If they say they're passionate and skilled, but they have a degree, that's how you know they're lying. Only fools get the piece of paper that screams do not hire.

  61. Currency abbreviation, much? by DanJ_UK · · Score: 0

    FFS it's GBP, not BP. Who wrote this?

    --
    - Dan
  62. Of course not. by Anonymous Coward · · Score: 0

    I'm a network engineer with over 30 years of experience in I.T.

    Of course the degrees are not providing a return on investment. That's because the I.T. industry is mostly experience driven.

    If you apply for a job with me, I will give you a written test and a hands on test, and the person that successfully passes the tests the quickest will get the job, and I don't care if you have a high school diploma or a PhD in Computer Science. The piece of paper does not generate me results.

    Mostly it's schools that insist you have a degree, but they are kidding themselves, and paying a premium for a piece of paper. Knowledge is knowledge regardless of by what means it was obtained.

    Don't worry about the stupid computer science degree. Just train and practice your skills and self teach and get specialized product education from those that manufacturer the products themselves (Microsoft, Cisco, Intel, etc.)

  63. Re:Computer Science is Completely Worthless by Anonymous Coward · · Score: 0

    My company has many openings, but we want certifications of practical work,

    Cocksuckers, got it.

    I never fell into this trap because when I finished high-school, I called up various company recruiters for jobs I wanted in the future and told them that I don't have any qualifications or such right now, just finished school, but I will go do the courses/training they're looking for.

    You sucked cock to get a job, got it.

    No it isn't. you just didn't go to the institutions that want it, nor did you get all the per-requsits necessary for it that I noted above.

    Didn't suck cock. There are always jobs for cocksuckers. Cocksucker.

  64. jobs advertised on Stack Overflow by Anonymous Coward · · Score: 0

    ... it's shocking that no one has called out the "jobs advertised on Stack Overflow" part, since who knew SO even had jobs? who advertises jobs on SO? can these jobs be representative of jobs on real job boards people actually know about and linkedin?

    1. Re:jobs advertised on Stack Overflow by Anonymous Coward · · Score: 0

      Yes, Stack Overflow has a job board. If you don't know about it, you're too old for tech.

  65. Re:Of course by Anonymous Coward · · Score: 0

    The autistic loner stereotype is a decade out of date. Successful computer experts today are purple haired lesbians who spend their entire lives on social media, twittering away while they commit code to git every day. Autistic white male nerds have no chance of getting jobs, not even dead end jobs.

  66. Re:Computer Science is Completely Worthless by Anonymous Coward · · Score: 0

    I don't give a shit about what consumers want. The only product I want to make is a product that genocides your fucking ass. Die, all of you, die.

  67. Re:Computer Science is Completely Worthless by Anonymous Coward · · Score: 0

    Untrue! You're too lazy to start Jowie's suck service (hahaha) for yourself so I doubt you can threaten anyone (other than yourself).

  68. My experience by Anonymous Coward · · Score: 0

    Once i saw my BS degree dribble, i specialized in other fields where programming made a good suppliment to the role. Making 150 to 160k per year in 3 different fields i would have never considered after college. More time off than i expected as well (work only 4 days each week or less)

  69. BP? by Anonymous Coward · · Score: 0

    50,000 BP

    BP? British pounds? You mean £50,000? That's how I was taught to write it in school.

  70. Re:Computer Science is Completely Worthless by Anonymous Coward · · Score: 0

    It's not that I'm lazy. I just don't care.

    I can suck my own cock just fine. I don't care about your cock.

    Because I don't need Jowie's suck service for my own benefit, I sure as hell am not going to start Jowie's suck service for anyone else's benefit.

    Fucking die and reduce my overcrowding, you useless lumps of shit.

  71. No Computer degree != less knowledgeable by Anonymous Coward · · Score: 0

    as mark twain puts it, "I don't let my knowledge interfere with my education"

    I do understand that a CS degree will give you very important basic knowledge to succeed in a CS related career. However, that does not necessarily mean that not getting one will make you less competent.

    I started coding at age 15 and pretty much was self taught from there. It was really hard in the beginning - getting picked for jobs without a degree but I pretty much worked my *** off a few years.

    Even though I don't have a degree but I have read most books a CS grad will typically gone through. I started without a theoretical knowledge of algorithms, architecture, design patterns, best practices (among others) but I learned on the lot as I went along - through self paced courses, books but have been raising the complexity ever since

    As a result, I am paid today more than a lot of engineers with more advanced degrees because of all the practical knowledge I amassed along the way. I even manage a few with a an advanced degree and their theoretical knowledge is not always necessarily better than a person with considerable experience who learned on the job.

    I am not saying a degree won't teach you anything useful. However to make a blanket assumption that people without a degree will not have the same knowledge

    people will often ridicule people without a degree by talking about the specific case of a person who went through a single short bootcamp... and I agree, this will not make you all of a sudden a master developer . This ignores the people who are self taught, went through multiple classes informally and end up with the same knowledge... if not even better.

    1. Re:No Computer degree != less knowledgeable by Anonymous Coward · · Score: 0

      I started coding at age 15 and pretty much was self taught from there.

      What a coincidence. I started coding at age 5. Programmable calculators at first, then I learned Basic, then I learned Pascal, then I learned HyperTalk (who remembers that?!), then I learned C++. By age 11, I was writing drivers for printers, and I had built an email delivery tool for an ancient LAN system which no longer exists.

      I was in all the accelerated math classes in school, skipped a grade, entered high school a year early, entered college at age 15 to study computer science. I had an A- grade point average throughout, and graduated with honors.

      As an adult I went on to write open source software for Linux. Why I bothered, I have absolutely no idea.

      Are there any jobs for me? Of course not.

      THERE ARE NO JOBS. THERE ARE NO JOBS ANYWHERE.

      I was advised to supplement my resume with a portfolio of my work, by lying recruiters who lie out of their assholes. Never has any portfolio project gotten me a job. Recruiters are shit. Hiring managers are shit. Your entire industry is shit. All of it.

      Degree? I did that. Worthless.

      Self taught? I did that too. Still worthless.

      Fuck you all.

  72. Re:Computer Science is Completely Worthless by Ash-Fox · · Score: 1

    Cocksuckers, got it.

    No, it's just a policy to look for people with practical skills. If you're coming with zero experience and just a Computer Science Degree, you'll still go through the practcal interview process, but likely to fail because you have no knowledge of MCSE, CCNP practical knowledge, even though is is an 'openbook' practical, meaning you're free to Google and use any common operating system (in the clould) and tools accessible to you (hint: most people who just a CS degree fail).

    You sucked cock to get a job, got it.

    I trivially found the requirements for the industry I want to be in and got into it, didn't waste eight years studying. Cry some more.

    --
    Change is certain; progress is not obligatory.
  73. Business is Business by Anonymous Coward · · Score: 0

    So, nobody mentions that it's cheaper to higher some company in India to do the coding than it is to higher local workforce. Doesn't matter how skilled you are. The business man's skills are always for the shareholders benefit no matter how dumb it is.$$$$

  74. Re:Computer Science is Completely Worthless by Anonymous Coward · · Score: 0

    Computer science is a dead field, you goddamed lying trolls. Fuck you!!

    With a charming personality like that, I don't understand why you weren't their first choice?

  75. Re:Computer Science is Completely Worthless by Anonymous Coward · · Score: 0

    you'll still go through the practcal interview process, but likely to fail because you have no knowledge of MCSE, CCNP practical knowledge, even though is is an 'openbook' practical, meaning you're free to Google and use any common operating system (in the clould) and tools accessible to you (hint: most people who just a CS degree fail).

    So you memorized all the bullshit answers to all the bullshit questions to bullshit your way into the social club. Meanwhile those CS people you deride have more depth and breadth of knowledge about the rationale behind your canned bullshit answers than you will ever have. But CS people haven't memorized the answers to your practical interview test word for word. Rote memorization is the only way to pass. Understanding is irrelevant.

    I trivially found the requirements for the industry I want to be in and got into it, didn't waste eight years studying. Cry some more.

    Cry? No. How about I just murder you? You know, back in high school, I was voted most likely to be the next Charles Manson. Maybe my peers were right. I should follow my calling. There's nothing for me in this world, except to kill overpaid shit like you.

  76. Re:Computer Science is Completely Worthless by Anonymous Coward · · Score: 0

    Soft skills Soft skills Soft skills Soft skills

  77. per cent lmao by Anonymous Coward · · Score: 0

    whyyyyyyyyyyy

  78. Re:Computer Science is Completely Worthless by Ash-Fox · · Score: 1

    So you memorized all the bullshit answers to all the bullshit questions to bullshit your way into the social club.

    Memorized? Nope, I could just do the job with the practical work right there and then, including things that I didn't have training for because I understood the software well or intuitively apply what I learned from one peice of software to another.

    But CS people haven't memorized the answers to your practical interview test word for word.

    I'll give you an example of a practical I give to someone who is applying for a job that deals with webservices and SSL management:

    This is a 40 minute practical, you're free to use google and look up anything you need. Please tell me which operating system you'd like to use, Windows or Linux and I will spin up the cloud server for you. You are free to download and use any tools you want to accomplish this.
     
    Generate a SSL certficate for a webserver.
    Install the SSL certificate on the webserver.
    Generate a Certificate Authority.
    Sign the SSL certificate with the Certificate Authority.
    Install the SSL certificate into the system's certificate store.

    You will find most certifications actually don't cover this, nor do CS courses usually. However certifications for adminstration familarize you with operating systems and tools sufficiently that you can actually figure out more or less what you need to do, to get the job done and understand how to use Google to figure out what you need. So, memorisation isn't really a thing here either.

    This is what the practical it self tests, whether you're able to actually get the job done, because with an ever changing IT landscape, being able to do the work in an environment that is changing due to disruptions constantly in the industry.

    Understanding is irrelevant.

    It is relevant, that's why they don't get the job most of the time. The vast majority I interact with can't even grasp what 'strace' is or how to debug a userland application with it.

    No. How about I just murder you?

    Let's meet and talk first. Front entrance, Belfast City Hall, Belfast, Northern Ireland. 12:00, October 5th.

    There's nothing for me in this world, except to kill overpaid shit like you.

    The only reason why I get paid well is because there are so few people in the industry that can actually do the work I do (I'm a heavy generalist - I can do development in x86 asm, m68k asm, c, c++, c#, java, python, perl, rust, go to a very senior level. I can do system administration/devops to very senior level. I do reverse engineering work on protocols, software and hardware. I can build custom embedded platforms from scratch. I can do project management, bid work and architect work. I can do datacenter work, including architecting etc - I didn't learn any of this from certifications) do it well, do it quickly and relatively future proof it.

    --
    Change is certain; progress is not obligatory.
  79. Shocker by Anonymous Coward · · Score: 0

    Who would've guessed spending years in an institution learning outdated programming languages would be a waste of time. Meanwhile you can get better courses online for fraction of the price and still hold a job without killing yourself with stress.

    1. Re:Shocker by Anonymous Coward · · Score: 0

      That's right, you fucking liar, keep the myth alive. Keep telling the myth about how there are jobs.

      THERE ARE NO JOBS.

  80. No CS Demand in UK? by finkusmcguber · · Score: 1

    Is there no demand for computer scientists in the UK? That 35000 GBP is only $47377 USD. I wouldn't intern for that salary! Someone was saying that can't find a job but I can't even look at my LinkedIn without stirring the dust for recruiters. I'd think this is the same for any other US software engineer. Is there really not tech demand over there? I worry for my brother-in-law finishing up school! He might have to come over here.

  81. What about hidden costs? by s31523 · · Score: 1

    What about the cost of scrappy hacked up software? I find computer science degrees valuable because practioners understand algorithms, good construction practices, and general computing terms better than other generic IT workers. Especially true in embedded software design. The cost to maintain code written by hacks, and potential bugs might not be considered at this point. Pay will eventually work out over time, and, I think CS degree holders might find work easier when economy slows.

  82. Re:Computer Science is Completely Worthless by Bengie · · Score: 1

    I do a lot of work with 3rd-parties and SSL. One of the issues that happens time and again is when I ask for the public key to install, they send me the private+public pair unencrypted via email and now I have their wild-star EV private cert that expires in 2 years. Just because someone can do the job doesn't mean they're competent.

  83. Re:Computer Science is Completely Worthless by Ash-Fox · · Score: 1

    One of the issues that happens time and again is when I ask for the public key to install, they send me the private+public pair unencrypted via email and now I have their wild-star EV private cert that expires in 2 years.

    I can imagine. I've worked with a few companies that specialize in security and had my fair share of ridiculous experiences.

    Just because someone can do the job doesn't mean they're competent.

    I would argue if they aren't competent, they can't do the job.

    --
    Change is certain; progress is not obligatory.
  84. 3,000 BP extra annually *is* a good ROI by Anonymous Coward · · Score: 0

    3,000 BP annually is 90,000 BP more over a career! That seems like a great ROI to me.

    Taken another way, the average degree is 9,000 BP per year, then it would be 36,000 BP it you complete in 4 years. 3,000 BP per year / 36,000 is 8.33% ROI. I would take that return any day of the week.

  85. Re:Computer Science is Completely Worthless by Bengie · · Score: 1

    I would argue if they aren't competent, they can't do the job.

    Ideally, yes. The problem is they seemingly can do their job. Most people's competence are gauged by how quickly they can make a symptom go away, not how correctly they fix the root problem. Like a hospital that ranks doctors by how quickly they get through patients, and a doctor just hands out pain killers like candy. All they did is externalize the cost.