Slashdot Mirror


The Rise of Developeronomics

New submitter Geist3 writes "Forbes has an article by Venkatesh Rao asserting that the safest investment for both corporations and individuals is in software developers. Throwing money at talented coders now — even on random projects — will build relationships that are likely to pay off big in the future. 'In what follows, I am deliberately going to talk about the developers like they are products in a meat market. For practical purposes, they are, since the vast majority of them haven't found a way to use their own scarcity to their advantage.'"

253 comments

  1. Great a new boom. by jellomizer · · Score: 4, Insightful

    A bubble in Developers! Developers! Developers!
    That means we will get a bunch of snot noes guys jumping into Computer Science who are in it just for the money. It will create the .COM boom all over again... Then it will crash and half of the idiots will stay and they will lay off half of the skilled workers.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    1. Re:Great a new boom. by gatkinso · · Score: 1

      So cash out before the crash. Barring that, be part of the upper half.

      --
      I am very small, utmostly microscopic.
    2. Re:Great a new boom. by Anonymous Coward · · Score: 0

      if only computer science was easy enough for the average money hungry bear to just "jump" into...hahaha

    3. Re:Great a new boom. by mario_grgic · · Score: 3, Insightful

      Overproduction of developers/comp.sci. graduates does not create a bubble. Perhaps a lot of miserable people, but not an economic bubble like the .com bubble of the late 90s. The most likely economic impact overproduction of qualified people will have is the cheapening of labor i.e. lower pay rate for developers.

      --
      As the island of our knowledge grows, so does the shore of our ignorance.
    4. Re:Great a new boom. by AtlantaSteve · · Score: 5, Informative

      Umm... were you around during the 1990's?

      Even in a normal market, tons of hiring managers don't understand enough to separate the wheat from the chaff anyway. In an overheated market, when hiring managers have to take what they can get if they want to fill a position at all... it is STUNNINGLY easy for workers with zero aptitude to jump in.

    5. Re:Great a new boom. by mwvdlee · · Score: 1

      No but a excessive demand of developers (the bubble) might create an overproduction of CS graduates. I think that's the causal order the GP had in mind.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    6. Re:Great a new boom. by BadPirate · · Score: 3, Insightful

      Seems to me that there is miles of difference between a born Engineer (a smart, logical thinker who loves tinkering and solving problems), and a sold Engineer (someone who has no inclination or desire towards engineering, but simply wants to make as much money as possible).

      I don't think there will be a Boom of engineers, because what any decent company is trying to do (and what this article is referring to) is get their hands on GOOD engineers... a product that you cannot commoditize.

      --
      - Holy crap, I've got MOD points! Who thought that was a good idea.
    7. Re:Great a new boom. by luis_a_espinal · · Score: 2

      if only computer science was easy enough for the average money hungry bear to just "jump" into...hahaha

      Where the hell have you been in the last 12-15 years? CS curricula has been watered down all across many universities, supposedly to churn graduates to meet industrial demand (with the predictable drop in quality.) I see your comment, and all I can think of is "wtf?"

    8. Re:Great a new boom. by naughty-timbo · · Score: 1

      Already happening, my friend.

      --
      you are what you is -- FZ
    9. Re:Great a new boom. by Aladrin · · Score: 2

      Actually, I'm a lot more worried about the bubble bursting than I am about the "snot nose guys".

      Right now, I make nice money. If this is a bubble, that will go up. And I'll get comfortable with that, and adjust my life to suit. When the bubble pops, my income will go way back down again, and that is going to hurt.

      --
      "If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
    10. Re:Great a new boom. by Anonymous Coward · · Score: 5, Insightful

      You misunderstood. First there is a bubble. A bubble is when the price of a good keeps rising because it has risen in the past. Then there will be people who want a piece of the pie but aren't actually developer material. The bubble may burst sooner due to demand side changes or it will burst later due to the supply side flood.

      I believe that developers are exceptionally undervalued. So much so that drastic raises would not be a sign of a bubble but a necessary correction. If you haven't noticed, the importance of software keeps growing, and writing good software is a hard problem that requires lots of experience and knowledge in difficult abstract fields in addition to application specific knowledge. Currently software quality is a major inhibitor of economic growth. Just look at how often you have to update software to fix security bugs.

    11. Re:Great a new boom. by luis_a_espinal · · Score: 3, Insightful

      Overproduction of developers/comp.sci. graduates does not create a bubble. Perhaps a lot of miserable people, but not an economic bubble like the .com bubble of the late 90s. The most likely economic impact overproduction of qualified people will have is the cheapening of labor i.e. lower pay rate for developers.

      It will create a bubble in the sense that morons will invest tons of money in developers, with salaries and benefit packages increasing until economic realities force their fist down their throats, with companies that existed solely for hoarding talent folding down as they should.

      Granted that this is harder to happen than in the dot-com era (where the plan was to hoard anything with e- or www in it, hoping to bail out and cash in or be bought by Yahoo or what not.) It is harder, but not impossible. In fact, given the penchant for speculative stupidity displayed by humanity in general (and us Americans in particular), it is highly possible. I cannot wait to see the debacle unfolding as it will be quite hilarious. Yes, it will be hilarious.

    12. Re:Great a new boom. by Maximum+Prophet · · Score: 4, Insightful

      ... In an overheated market, when hiring managers have to take what they can get if they want to fill a position at all... it is STUNNINGLY easy for workers with zero aptitude to jump in.

      It's often easier for the worker with near-zero aptitude. Someone who's spent time studying how people interact will always get ahead of someone who's only studied how *things* work.

      --
      All ideas^H^H^H^H^Hprocesses in this post are Patent Pending. (as well as the process of patenting all postings)
    13. Re:Great a new boom. by luis_a_espinal · · Score: 1

      Seems to me that there is miles of difference between a born Engineer (a smart, logical thinker who loves tinkering and solving problems), and a sold Engineer (someone who has no inclination or desire towards engineering, but simply wants to make as much money as possible).

      I don't think there will be a Boom of engineers, because what any decent company is trying to do (and what this article is referring to) is get their hands on GOOD engineers... a product that you cannot commoditize.

      Yes, and we can see that right now as companies are becoming, out of necessity, far pickier than before in their hiring process. Having said that, this particular tidbit of truth will be missed by the perennial speculator. You can count on seeing a lot of morons and moronic companies hoarding on software developers, missing completely on the fact that this does not equate to software development talent.

    14. Re:Great a new boom. by dkleinsc · · Score: 1

      Or, if you're part of the group that is getting hired due to the overheated market, just enjoy that nice fat paycheck (which means you're effectively cashing out every 2 weeks) until it ends. Don't spend it all in one place.

      --
      I am officially gone from /. Long live http://www.soylentnews.com/
    15. Re:Great a new boom. by Anonymous Coward · · Score: 0

      Yes, but I don't think there is miles difference between someone who is a born developer a logical thinker and highly intelligent but largely uninterested in computers, who decides to go that route for the money.

    16. Re:Great a new boom. by Timothy+Brownawell · · Score: 4, Insightful

      Right now, I make nice money. If this is a bubble, that will go up. And I'll get comfortable with that, and adjust my life to suit. When the bubble pops, my income will go way back down again, and that is going to hurt.

      Sign up for direct deposit, with a fixed amount (not percentage) going to your checking account, and the rest going to a savings account that you never look at.

    17. Re:Great a new boom. by Curunir_wolf · · Score: 4, Insightful

      Umm... were you around during the 1990's? Even in a normal market, tons of hiring managers don't understand enough to separate the wheat from the chaff anyway. In an overheated market, when hiring managers have to take what they can get if they want to fill a position at all... it is STUNNINGLY easy for workers with zero aptitude to jump in.

      Well that's the difference, isn't it? That's why it's important to locate and invest in the good developers now. In the speculated wave of developer bubble, it will be the difference between being the next Amazon or being the next Pets.com.

      --
      "Somebody has to do something. It's just incredibly pathetic it has to be us."
      --- Jerry Garcia
    18. Re:Great a new boom. by Anonymous Coward · · Score: 0

      In IT, school gives you only the starting skill set. To become one of those great, talented, well paid developers you'll have to learn a lot of things on your own, and not once in a while, but constantly.
      So, schools will turn out well papered, poorly skilled labour.

    19. Re:Great a new boom. by jellomizer · · Score: 1

      Schools adjust the difficulty of their classes to meet demand.
      Those tough to pass professors get pushed to those fancy Grad school classes. And the easy to pass gets pushed to into and get the BA in CS with some BS.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    20. Re:Great a new boom. by Anonymous Coward · · Score: 0

      This is a critical mistake a lot of software people make. People *are* things. A social system can be manipulated to give the most-positive outcome the same way a computer system can.

    21. Re:Great a new boom. by mrchaotica · · Score: 1

      a savings account that you never look at

      Better yet, an investment account, and look at it (to rebalance the portfolio) occasionally.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    22. Re:Great a new boom. by Tomato42 · · Score: 1

      Only few of us are blackhats...

    23. Re:Great a new boom. by Tomato42 · · Score: 4, Insightful

      that requires lots of experience and knowledge in difficult abstract fields in addition to application specific knowledge

      Yes, many don't see that real world IT is a interdisciplinary field. You need to take at least accountancy 101 if you want to know what accountants want from your software, let alone how to implement it, and implement it correctly.

    24. Re:Great a new boom. by PerfectionLost · · Score: 4, Informative

      Honestly, over the last 10 years my checking account has out performed my investment accounts.

    25. Re:Great a new boom. by smooth+wombat · · Score: 2

      Oh come on, that makes too much sense.

      We're talking about developers here. People that think you can always throw more RAM or disc space at a problem rather than keep their code neat and clean.

      --
      We will bankrupt ourselves in the vain search for absolute security. -- Dwight D. Eisenhower
    26. Re:Great a new boom. by Anonymous Coward · · Score: 0

      Developers and those developing relationships with them will succeed to the extent they together remain focused on producing value through their endeavors. When either gets greedy or unfair, they disadvantage themselves and any attached to them. Any impoverished behavior is a liability subjecting one to culling when a reckoning occurs.

    27. Re:Great a new boom. by syousef · · Score: 2

      Actually, I'm a lot more worried about the bubble bursting than I am about the "snot nose guys".

      Right now, I make nice money. If this is a bubble, that will go up. And I'll get comfortable with that, and adjust my life to suit. When the bubble pops, my income will go way back down again, and that is going to hurt.

      Then learn to manage your money. Otherwise you are arguing for everyone being on subsistence wages, which is going to hurt you, and everyone else a lot more.

      --
      These posts express my own personal views, not those of my employer
    28. Re:Great a new boom. by Anonymous Coward · · Score: 5, Insightful

      >So cash out before the crash. Barring that, be part of the upper half.

      I hate people who say this kind of thing. It's like telling investors: Buy low, sell high!

      There is no "upper half" that is fairly and reasonably chosen. I have a lot of experience in the field, and politics, knowing your manager's favorite flavor of ice cream, and selling your work to everyone is worth a lot more than actually being the talented guy who delivers rock solid work. Work environments are full of politics. It's wrong, and it's lame, but it's true.

    29. Re:Great a new boom. by Anonymous Coward · · Score: 0

      Thus, be a psychopath with regard to your job, and you'll be rewarded. (ie. be plotting, planning, walk on people if necessary, kiss up appropriately, set others up for failure, etc. to be the guy who looks great all the time).

      Someone make a company where there are systems in place to shut these people down and reward real talent.

    30. Re:Great a new boom. by Slime-dogg · · Score: 1

      Those aren't "CS," though. There's a guy here who never would have survived standard CS, but got his degree in something like MIS or BIS... he insists his degree is more essential to business than CS. Sad to say, he talks up a storm, but is incapable of following through on what he's promising.

      It's the "IT" specific degrees that will flood the market. The Information Systems, Business Systems, and so on, because those are where the math and logic requirements are minimal. They deal with people, and how people relate with computers. It isn't unimportant, but it also doesn't produce very good developers, either.

      --
      You need to restart your computer. Hold down the Power button for several seconds or press the Restart button.
    31. Re:Great a new boom. by Anonymous Coward · · Score: 0

      mod parent up!

      For line of business apps, this (real world familiarity with subject "X") is a key ingredient to project success, and the main difference between systems that meet the requirements doc on paper only, and those that -really- meet the requirement. (because no one's ever written a requirements doc that's 100% right, at least not in my line of work)

    32. Re:Great a new boom. by Anonymous Coward · · Score: 0

      I certainly hope so. I was about 2 years too late to truly take advantage of .com. I'm in a much better position to cash in this time.....let it happen!!!

    33. Re:Great a new boom. by rubycodez · · Score: 1

      be smart, save up for hard times. I like bubbles, can do well during and after them.

    34. Re:Great a new boom. by Toonol · · Score: 1

      Manipulating a social situation is not evil. It can be a simple as smiling at appropriate times. It can be showing to others that your presence can make a day more enjoyable. It is a valuable skill, that many programmers not only lack... they deny it's a valuable skill at all.

    35. Re:Great a new boom. by Anthony+Mouse · · Score: 1

      People that think you can always throw more RAM or disc space at a problem rather than keep their code neat and clean.

      I think you're confusing "think you can" with "have to."

      Writing clean code takes longer. The developer generally isn't the one who decides how long he gets to spend on something.

    36. Re:Great a new boom. by tompaulco · · Score: 1

      That's nothing. Throwing away money on frivolous toys has outperformed my investment accounts.

      --
      If you are not allowed to question your government then the government has answered your question.
    37. Re:Great a new boom. by greg1104 · · Score: 1

      You've missed the real implication that comes from realizing good software developers are actually worth more than just about anything else. The right answer to your thought experiment problem is to find/make an accountant who knows enough about software to write useful specifications, then put them to work on testing the results too. That's cheaper than trying to turn a good developer into a entry-level accountant, which isn't very likely to go well anyway.

    38. Re:Great a new boom. by somersault · · Score: 2, Interesting

      It's not evil, but it is kind of sociopathic if it's not within your nature to do these things. I'll smile when I'm happy, or perhaps instinctually when others smile at me, but I don't go around smiling at people for no reason. I can tell when people are just faking their smiles, and I hate it. It definitely doesn't make my day feel more enjoyable, it just creeps me out.

      --
      which is totally what she said
    39. Re:Great a new boom. by Anonymous Coward · · Score: 0

      difference between being the next Amazon or being the next Pets.com.

      No, it will not. The difference between Amazon and Pets.com is management, not developers. You can have the best or crappiest developers in the world, but if the company does not know what they are doing and where they are heading, developers can't save it.

      Developers are the engines on a boat. They can make things go. Where the boats heads is up to the navigators or the executives. You need *both* - the engine and a navigator.

    40. Re:Great a new boom. by greg1104 · · Score: 1

      For the next ten years, the real question in the US is which of investment and cash accounts will lose value slower, relative to what you can buy with the result. Just like real estate, the idea that the stock market has any sort of consistent return is a myth that came about from 20 years of general US prosperity (1980 to 2000) where that was usually true--and that relatively short trend is completely busted now.

    41. Re:Great a new boom. by Anonymous Coward · · Score: 0

      Well said. I know what happened in the 90's. It was inevitable though as computers evolved from beast that could be maintained by mechanics (non certified wild west mechanics) to beasts that needed to be maintained by engineers.
      The globalists smeared it as they wanted it centralized, like everything

    42. Re:Great a new boom. by JonySuede · · Score: 2

      I sadly agree, kicking ass helps but it is not even necessary nor sufficient to rise to that hypothetical upper half, however being good at politic is a sure prerequisite to rise in the upper half of any organization composed of more than 100 persons.

      --
      Jehovah be praised, Oracle was not selected
    43. Re:Great a new boom. by JonySuede · · Score: 1

      what you are talking about is a fake smile, what Toonol is talking about is sounding more like a natural "joie de vivre", some-people radiate with happiness and I agree with him, it is a valuable skill.

      --
      Jehovah be praised, Oracle was not selected
    44. Re:Great a new boom. by Tomato42 · · Score: 1

      You need a programmer that knows about accounting and a good accountant working as a team at least at the design stage, all your programmers need to know a bit about accounting, either they will learn as they go, or they won't be wasting the lead time and take a course at the time the software is designed. That's if you're making accounting applications. The same goes for any other field: healthcare, banking, storage management. If you don't understand the industry (what can be made by computers and what can't) you won't be able to make good software for said industry.

      Good developer is not somebody that can output 1kLOC of bugfree code daily, it's somebody that can learn new things daily and apply them in his work. That includes understanding what accounting is really about, what a healthcare unit receptionist needs from software and how to calculate lease rates. If a programmer doesn't understand the industry, you'll have lot's of functionally wrong code because of errors in specification, corner case bugs discovered after the code was shipped and all the other assorted niceties.

    45. Re:Great a new boom. by Gorobei · · Score: 2

      There is no "upper half" that is fairly and reasonably chosen. I have a lot of experience in the field, and politics, knowing your manager's favorite flavor of ice cream, and selling your work to everyone is worth a lot more than actually being the talented guy who delivers rock solid work. Work environments are full of politics. It's wrong, and it's lame, but it's true.

      To be fair, the article was more talking about the "upper 1%" rather than the upper half.

      If you are really a 10X contributor, you just leave environments that are too political.

      Screw the ice cream, if you are in a serious group, you all have a company credit card and can get it delivered. If senior management is doing their job, they will fire any middle manager who is not rewarding/promoting his talent based on results.

      I love my job :)

    46. Re:Great a new boom. by mjwx · · Score: 1

      A bubble in Developers! Developers! Developers!
      That means we will get a bunch of snot noes guys jumping into Computer Science who are in it just for the money. It will create the .COM boom all over again... Then it will crash and half of the idiots will stay and they will lay off half of the skilled workers.

      Been saying this for a while. This is the part of the bubble just before it bursts.

      I call this .bomb 2.0 or iBust in homage the most ridiculously overvalued company.

      Inevitably the overpriced companies will lose a lot of their share price, Apple, Zynga, Twitter, Facebook (if they are smart enough to get their IPO sorted before the crash), even Google's going to lose a fair chunk although not the 60-80% I'm predicting for APPL, Zynga and Facebook.

      The rush in hiring developers means we've moved into the late adopters stage. Everyone and their dog is saying "look at Facebook" and "Me too". They are creating web services and portals (in the Cloud) not realising that the ship has sailed. Look at FB, they already losing value before their IPO, if Zuckerberg is smart he'll sell out before the crash is imminent and FB loses most of its value. Much in the same way MySpace's creators sold out to News Corp (MySpace is now worth what fraction of what News Corp paid for it). Once this happens, developers become useless and overpaid. I think this is going to come as a big surprise to many developers. When push comes to shove, Devs will be the first to go in most tech companies. During the GFC, my company of 95 ish staff sacked 12, 9 were developers and Australia weathered the GFC _a lot_ better then most western nations.

      --
      Calling someone a "hater" only means you can not rationally rebut their argument.
    47. Re:Great a new boom. by PimpDawg · · Score: 0

      People like to pretend that CS grads are working on operating systems kernels and developing new algorithms, but the reality is that most people on a day-to-day basis are working on a typical line-of-business record keeping system with reports that used to be done in Excel.

    48. Re:Great a new boom. by benjamindees · · Score: 2

      Good developer is not somebody that can output 1kLOC of bugfree code daily, it's somebody that can learn new things daily and apply them in his work.

      I have experience in lots of different jobs in several different industries, and this statement right here hits the nail squarely on the head.

      The problem is, even though it is true, you will never be able to convince anyone of this. There are still far too many companies that simply don't want to hire any developers, period. They have absolutely zero clue how to deal with someone who applies software development to his daily work. Tell a recruiter that you are a quick learner and have worked in several different industries, and they will think you are an unspecialized flake. Tell an employer that you can easily write some custom code, and they will worry about maintainability and interoperability and tax implications. Tell your boss that you can automate a task, and they will wonder why they hired you, begin to fear for their own job and budget, steal your work, and find a way to get rid of you.

      And I'm speaking from experience. I watched a start-up go down the tubes partly because their developers sat in their cubicles month after month producing code that consistently failed in the field, and they never knew it until the very end. But the investors ended up with exactly what they wanted: no business, no customers, no capital resources, just a few questionable pieces of "intellectual property". The most successful job I've had was one in which I quietly automated all of my work without telling anyone. When I asked for more work, they fired me. No shit. On the other hand, I've also seen a company built around perfectly bug-free, perfectly usable in-house software that was a total waste of time and resources because it relied on the most labor-intensive way to accomplish the task at hand. Try to point this out, though, and you will be attacked like the monkeys in the cage who beat any monkey that reaches for a banana.

      Frankly, I don't see any of this changing any time soon. The entire structure of modern business, from education to finance, is completely hosed. There is a blind worship of specialization, even though most workers and managers are incapable of recognizing it without seeing degrees hanging on a wall. There is an implicit belief in the labor theory of value. There is almost total ignorance of the practicalities of software development, and it's potential benefits. And there are powerful forces with aircraft carriers and money-printing presses who want to keep it that way.

      --
      "I assumed blithely that there were no elves out there in the darkness"
    49. Re:Great a new boom. by tomhudson · · Score: 5, Insightful

      Overheated market?

      What overheated market?

      When I see stupidity like this:

      A software developer on the other hand, can float free on the Internet, making money in mercenary ways, with no deep loyalties, if he/she so desires

      ... it's like this guy has never heard of outsourcing to cheap 3rd-world and eastern European countries and crap sites like elance.

      Or this ...

      An ex-Microsoft engineer is valuable anywhere in the economy if he voices support for buying Microsoft wherever he goes.

      He's never read the posters on the minimsft blog, all swearing that after being "managed out", they will never, ever recommend Microsoft products.

      A talented high-school kid who starts hacking away at an iPhone app at 14 is likely to stay in orbit around Apple for his/her entire career.

      Really? So none of those iPhone or Android devs got their start on anything but Apple or ... what? Gmail?

      Of course, it's all based on a false premise:

      Today, this abstract point specifically translates to: people who can invest in developers, developers, and everybody else. This means that if you are in apparently more fundamental professions - perhaps you are a baker with a small business - you are effectively useless, not because bread isn't important, but because surviving in the bread business is now a matter of having developers on your side who can help you win in a game that Yelp, Groupon and other software companies are running to their advantage. If your bakery doesn't have an iPhone app, it will soon be at the mercy of outfits like Yelp.

      And god forbid, if you donâ(TM)t have a skill, like baking, which the developer-centric economy can actually use, you are in deep trouble.

      The bakers and butchers will still be eating when Groupon is bankrupt. And almost nobody gives a crap about Yelp. They get their recommendations from friends, not strangers trying to game the system. And certainly not from an iPhone app spamming them with "Eat at Joe's".

      Like so much from Forbes, this is just more idiot drivel!

    50. Re:Great a new boom. by idontusenumbers · · Score: 1

      CS curricula is also quite disconnected with what employers are having CS graduates do.

    51. Re:Great a new boom. by datavirtue · · Score: 2

      Bullshit, it works. You can practice your fake smiles. It is called acting. I'm not one for bullshitting and spending energy manipulating people, but I would have to be stupid not to recognize the craft. I see people who do not play because they think they have enough power or ability to overwhelm the need for this dynamic; these people have no idea how lame they are or how much power they negate because of it. Institutional power melded with people skills and genuine concern can do wonders for the world.

      --
      I object to power without constructive purpose. --Spock
    52. Re:Great a new boom. by datavirtue · · Score: 1

      I have run into former machinists at the college where I work and they were all practically forced to "study" computer science. They tried to diverge and were refused funds from the programs they were under. There are certain programs paid for by some companies and the government (can't recall the designations but they were instituted when certain companies relocated over seas), but in my conversations with these people they made it very clear they were forced to pursue a certain line of study or they would have been refused funding for college. They were given a "test" to see what field they would be "good" at and subsequently forced to follow what was dictated by the "results" of the test. I shit you not. As far as I know they could have refused the funding and used Pell Grant and regular student loans but the program ALSO included living pay AND they had nothing to repay afterwards---but to get it they had to finish network tech degrees and such (not really comp sci but that is what most colleges call it).

      --
      I object to power without constructive purpose. --Spock
    53. Re:Great a new boom. by datavirtue · · Score: 1

      The people who flock to those degrees would never have been developers. Hell, they aren't even interested in IT that much. I have met a bunch at the college. I met a guy in Computer Arch & Design class, I noticed that he finished his project (single board 8085 trainer, binary assm, etc...) far ahead of everyone so I asked him if he was going into embedded systems or going to play with more low-level stuff and he said: "no...I'm in for networking, I'm a plug n' play guy." This was the most likely of the 20 something people besides myself (a life long programmer, network engineer, admin, etc..) in the class who could actually do anything of significance with what they were learning (or hopefully learning). I studied outside of class and was totally consumed with the project, everyone else just showed up and went through the motions. A lot of them were just clueless, even at the end. I have learned that if you show up and slouch around at school and get C's you really get nothing out of it. School is what YOU make it.

      Maybe those people will graduate and compete with you for jobs, but the chances of them building something on their own (becoming a real developer) are nil.

      --
      I object to power without constructive purpose. --Spock
    54. Re:Great a new boom. by datavirtue · · Score: 1

      On my first day at community college in Psych 101 the adjunct professor got up int front of the class and said: "We had our meeting and decided how many A' we were going to give out in this class..." This professor gave us all the questions AND the answers for all of the tests. All you had to do was study them and the A was yours. Almost half the class failed. The other half was a smattering of A's B's and C's. I knew there was a problem when I talked to a class mate and found they were struggling. I was shocked. I got an A, but I used my excess time to study the material and learn what I wanted to learn from the class. I basically took notes about AI the whole time.

      --
      I object to power without constructive purpose. --Spock
    55. Re:Great a new boom. by Jeppe+Salvesen · · Score: 1

      Amen.

      And: Excellent developers require excellent leadership to perform well! Without excellent leadership (that understand what system development is, how to separate the wheat from the chaff and how to organize system development), the effort of developers will go to waste.

      The magic happens only when excellent developers are managed well.

      --

      Stop the brainwash

    56. Re:Great a new boom. by The+Grassy+Knoll · · Score: 1

      You know the score: write code, keep a low profile, go undergound for a bit, create new identity, apply for new jobs, rinse and repeat... .

      --
      They will never know the simple pleasure of a monkey knife fight
    57. Re:Great a new boom. by somersault · · Score: 1

      these people have no idea how lame they are or how much power they negate because of it.

      Maybe those people don't care about "power"?

      Thinking back on all the coworkers I've had, it's the power hungry ones that are the most fake - that have the most desperate smiles. Thankfully the worst offenders got made redundant or fired. For the most part I love the atmosphere here. The engineering department is full of genuine people who I can get on well with. The other departments, not so much.

      --
      which is totally what she said
    58. Re:Great a new boom. by somersault · · Score: 1

      I'd say it's a valuable trait, but I don't see how you can think of it as a skill without it turning into something fake.

      --
      which is totally what she said
    59. Re:Great a new boom. by killmenow · · Score: 1

      Your post is both reasoned and articulated well. Unlike the Forbes article. There's a reason I don't click Forbes URLs. Since I'm fresh outta mod points, I'm replying to basically agree with you.

    60. Re:Great a new boom. by tomhudson · · Score: 1

      [southern_drawl]
      What yur fancy-pants degrees really mean ...
      First, there's yer basic Bee Ess. Y'all know what Bee Ess stands for, right, honey?
      Then you got yer Em Ess. That there's jus' More of the Same Bee Ess.
      And for those who really like to shovel it, you got yer Pee-Aich-Dee - that's like More of the Same Bee Ess, but now Piled Higher 'n' Deeper
      [/southern_drawl]

      grade_inflation + for_profit_colleges = education_debt_bubble. People now owe more in student debt than all other forms of consumer debt combined.

    61. Re:Great a new boom. by PerfectionLost · · Score: 1

      Personally, I am falling back on two fairly basic investment notions:

      1) You should buy a house, because you want to live there, or because you want to become a slum lord.
      2) You should buy stock because you want to own the company, or they pay substantial dividends that you will use as income.

    62. Re:Great a new boom. by tehcyder · · Score: 1

      I love my job :)

      As you said, you're talking about the lucky 1%.

      Meanwhile the other 99% fucking hate their jobs and bosses, except in countries like the US where people have been brainwashed into thinking they're all part of a big happily competitive family..

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    63. Re:Great a new boom. by tehcyder · · Score: 1

      People like to pretend that CS grads are working on operating systems kernels and developing new algorithms, but the reality is that most people on a day-to-day basis are working on a typical line-of-business record keeping system with reports that used to be done in Excel.

      Or they're working out ever sneakier ways of mining personal data from users/customers without their knowledge.

      *cough* google *cough* facebook *cough* groupon *cough*

      Truly a noble vision of the future.

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    64. Re:Great a new boom. by tehcyder · · Score: 1

      There is an implicit belief in the labor theory of value.

      You lost me there. Are you seriously suggesting that most organisations are Marixst?

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    65. Re:Great a new boom. by tehcyder · · Score: 1

      Actually, I'm a lot more worried about the bubble bursting than I am about the "snot nose guys".

      Right now, I make nice money. If this is a bubble, that will go up. And I'll get comfortable with that, and adjust my life to suit. When the bubble pops, my income will go way back down again, and that is going to hurt.

      Try doing a proper job for a proper company. If you are working in a bubble company, your work is by definition without value, so why should anyone care?

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    66. Re:Great a new boom. by tehcyder · · Score: 2

      I spend half my enormous salary on coke and hookers, but admittedly I do waste the rest.

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    67. Re:Great a new boom. by tehcyder · · Score: 1

      You should buy a house, because you want to live there, or because you want to become a slum lord.

      Why can't you just be a reasonable landlord?

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    68. Re:Great a new boom. by tehcyder · · Score: 1

      be smart, save up for hard times. I like bubbles, can do well during and after them.

      People like you should be punitively taxed when the companies they work for go down the pan.

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    69. Re:Great a new boom. by Anonymous Coward · · Score: 0

      sadly, people do use yelp

    70. Re:Great a new boom. by s73v3r · · Score: 1

      I'd say being able to keep up that jolly attitude, and not letting things get you down, or at least projecting that image, is a skill.

    71. Re:Great a new boom. by somersault · · Score: 1

      I'd definitely agree that it's worth the time cultivating your viewpoint such that you have some perspective on your problems. It's not worth letting problems get you down, it's better to focus on how you can best manage the situation. I'm not a particularly jolly person as such, but then again I'm a lot more resilient when I have problems due to the things I've gone through in the past, and I seem to be good at helping others handle stressful situations too.

      --
      which is totally what she said
    72. Re:Great a new boom. by s73v3r · · Score: 1

      That's assuming that even non-bubble companies won't feel pain.

    73. Re:Great a new boom. by s73v3r · · Score: 1

      Care to give your reasoning why Apple and Google are "overpriced"? They consistently deliver good profit margins, and have good advantages over their competitors that they are able to leverage.

    74. Re:Great a new boom. by hazah · · Score: 1

      Don't forget, that pointy haired boss may not be all that honest. Going down in flames for someone else's decisions is only deserved if you had knowledge and a say.

    75. Re:Great a new boom. by Anonymous Coward · · Score: 0

      I understood the comment to mean that the more labor intensive something is, the more valuable it is....

    76. Re:Great a new boom. by Anonymous Coward · · Score: 0

      +1

      Seriously. I met a guy once at a conference who used to be a reverse 10-key type accountant, who now made a living rewriting accounting inputing systems. He was saying that most accounting software is awful, that it doesn't take accountant mindsets and typical workflow into account. He's been able to use his knowledge of accounting to create UIs that make data input at least an order of magnitude faster.

    77. Re:Great a new boom. by Eli+Gottlieb · · Score: 1

      I agree with the epithet "iBust". I completely disagree with the notion that Apple or Google will go under.

      Google is now the world's premier advertiser. Apple has more cash-on-hand than any government on the planet, all from product revenues. The rest might crash and burn, but these two have sustainable business models based on selling stuff to people who want it.

    78. Re:Great a new boom. by benjamindees · · Score: 1

      Marx didn't conceive of the labor theory of value, though he did expand it to ridiculous levels. It was a prominent feature of classical economics, and is even still espoused by modern Keynesian economists *cough*. It can probably be traced to Thomas Aquinas.

      --
      "I assumed blithely that there were no elves out there in the darkness"
    79. Re:Great a new boom. by dkleinsc · · Score: 1

      And certainly not from an iPhone app spamming them with "Eat at Joe's".

      That's better than a busted neon sign that flashes Ea a oe's.

      --
      I am officially gone from /. Long live http://www.soylentnews.com/
    80. Re:Great a new boom. by tomhudson · · Score: 1

      And certainly not from an iPhone app spamming them with "Eat at Joe's".

      That's better than a busted neon sign that flashes Ea a oe's.

      False dichotomy. Those aren't the only two choices, so it's wrong to argue that an iPhone App spamming people is somehow good, for "any" value of good.

      One guy had a sign in his window with a typo - people would come in to tell him about it, and he'd say "I know - it gets people in the store who wouldn't ordinarily stop in." They'd talk for a bit, and often ended up becoming repeat customers. All because of a cheap sign with a typo. Ingenuity and understanding human nature - in this case, that people want to have some sort of connection with the people they do business with, even if it's just some chit-chat over a badly-worded sign - beats spam every time.

    81. Re:Great a new boom. by dkleinsc · · Score: 1

      You are taking my reply way too seriously. The video is of a song by the Folksmen, played by the same actors who created Spinal Tap (Christopher Guest, Michael McKean, and Harry Shearer), that just happens to use that exact phrase.

      --
      I am officially gone from /. Long live http://www.soylentnews.com/
    82. Re:Great a new boom. by tomhudson · · Score: 1

      Sorry about that - I never heard of them.

  2. Wait wait wait! by Anonymous Coward · · Score: 1

    Are you saying that if you invest in highly skilled staff there are benefits?

    This person is clearly a quack and has no fundamental understanding of IT stereotyping. The longer you've been somewhere the more useless you are (sheesh, we all know this right guys? Guys?)

  3. Profit!!! by gti_guy · · Score: 1, Funny

    Step 1. Pay Developers - Step 2. ??? - Step 3. Profit!!!

    1. Re:Profit!!! by Anonymous Coward · · Score: 2, Insightful

      Step 1 Pay Devs
      Step 2 Release Product
      Step 3 Get sued into Oblivion by a hundred patent trolls
      Step 4 go out of business

      There, fixed the business model for you.

      Yours,
            A recently laid off Developer.

    2. Re:Profit!!! by jd2112 · · Score: 1

      Step 1 Pay Devs Step 2 Release Product Step 3 Get sued into Oblivion by a hundred patent trolls Step 4 go out of business

      There, fixed the business model for you.

      Yours, A recently laid off Developer.

      The moral of this story is go into law school instead of CS.

      --
      Any insufficiently advanced magic is indistinguishable from technology.
    3. Re:Profit!!! by Anthony+Mouse · · Score: 1
  4. Unionize by dcollins · · Score: 2, Insightful

    "...the vast majority of them haven't found a way to use their own scarcity to their advantage."

    The way: Unions.

    --
    We know where leadership by an anti-intellectual "strongman" who scapegoats minorities and likes boisterous rallies goes
    1. Re:Unionize by AtlantaSteve · · Score: 4, Interesting

      About half the politically-minded people I run across in IT are hardcore Ron Paul types, and the other half are Karl Marx types. Both of those groups are annoying in different ways, and tend to ruin any conversation that they barge into.

      However, I do have to say... at least the Ron Paul types are often competent and good at their jobs. I have NEVER , during 15 years in the field, EVER encountered a competent IT professional who dreamed of being in a union. Union culture is pretty much the antithesis of what makes a good engineer tick. I clicked on and briefly skimmed your profile, and could not help but notice that not a single one of your comments over recent months has anything to do with technology or IT work.

    2. Re:Unionize by PoolOfThought · · Score: 5, Insightful

      "...the vast majority of them haven't found a way to use their own scarcity to their advantage."

      The way: Unions.

      No, that's how the non-scarce resources create an advantage for their collective selves. If you're not scarce you make yourself scarce by joining a group that then says "well, we're it" so you must treat us as if we are scarce. Sort of a "you don't like what I want... well guess what... you have to give it to me anyway because all my buddies are going to hold out for the same and no one will do you work if you don't meet my demands".

      Scarce resources have power individually, through simply being scarce. Sometimes it takes a while for someone to realize just how scarce they actually are. Scarce resources are special. They might be really close to the only one who can do the job required job in the required amount of time to the desired degree. That's what makes them scarce. They have the right experience, with the right knowledge, and the possibly even right background for the exact work that needs to be done. Truly scarce resources are capable of getting more than they would be unionized because they are not lumped in with the not quite so scarce.

      --
      My present is the activity I am currently engaged in with the purpose of turning the future into a better past.
    3. Re:Unionize by Anonymous Coward · · Score: 0

      Yes, let's create artificial barriers to entry into the engineering fields! The last thing the world needs is more engineers. And I'm sick of having my compensation tied to my performance---from now on it's seniority or nothing.

      We don't need a union, we need to teach each other how to fucking negotiate. The startups out in silicon valley are dying for good engineers. If you've got the skills and are willing to play hardball you can have anything you want, but you've got to be willing to do the negotiation. "Sorry, I've got a better offer from so and so. I need a higher salary, larger stake in the company, etc." And there are plenty of companies where the engineers are doing the evaluations. In fact that's the norm in my experience. If you're being interviewed by folks who don't know their shit then try somewhere else.

    4. Re:Unionize by Anonymous Coward · · Score: 0, Informative

      that's some pretty good nonsensical generalizations there br0

    5. Re:Unionize by ByOhTek · · Score: 1

      Umm, you are insinuating that it's "be a Ron Paul" type, or want to join a union in the first two sentences of the last paragraph. I'd rather have my testicles eaten off of me by fire ants, than join a union, but I sure as hell am not a Ron Paul type.

      (Unions do have some advantages, but for me, personally, they have tended to be more counterproductive).

      --
      Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
    6. Re:Unionize by PoolOfThought · · Score: 1

      Great point! 'Round these parts (Tennessee) I have known only one developer that I can think of who believed that unionizing programmers was a good idea. And I'm not so sure he didn't state that in a more "tongue in cheek" kind of way. He's french and would always throw out the occasional "in france.... bla bla bla" comment. He also used to laugh and joke about how American's didn't have a clue on how to go on strike. "Now the french? Oh yeah... we are the KINGS of striking!".

      But other than my french friend I have no one that even joked about "organizing" software developers.... would love to hear well thought out arguments in its favor though. Don't mind reading an opposing point of view. Maybe I'll learn something...

      --
      My present is the activity I am currently engaged in with the purpose of turning the future into a better past.
    7. Re:Unionize by Anonymous Coward · · Score: 0

      Um I was the branch secretary for connect (father of the chapel) and I was one of the first 5 webmasters in BT I also worked on key web projects for BT as well as representing members my best success was getting a better pension for 1100 people worth around $20,000.

      Other Connect members have been CTO's of mobile telcos and the CEO of one uk FTSE100 company was an activist in his younger days.

      Oh and earlier this year I diagnosed a problem (worthy of a mention on the daily WTF) with a major site - which had a major impact (id get sacked if I told you how much that cost over only 5 days - hint I could buy a house and an Audi R8 and have change left over)

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

      I dearly wish I had a mod point for you right now.

    9. Re:Unionize by AtlantaSteve · · Score: 1

      Perhaps I should have explicitly said "blowhards" rather than "political-minded people" in the opening sentence, but I was trying to start off on a polite note! :)

      Either way... I was speaking about two opposite extremes. It seemed pretty clear that my perspective was somewhere in between the two (along with yours, and probably the majority).

    10. Re:Unionize by PoolOfThought · · Score: 1

      I didn't see a single generalization there. He specifically stated that he was talking about the ones that he runs across in IT. I would say he's got every right to say how he sees that group without that same commentary being attached to everyone in IT. Did I miss something?

      --
      My present is the activity I am currently engaged in with the purpose of turning the future into a better past.
    11. Re:Unionize by PoolOfThought · · Score: 1

      No, he said that the people he has dealt with have come across either one way or the other. Not that those are the only two options.

      And, as unwilling as I am to join a union, I would probably do so if the only other option available was to have my testicles eaten off of me by fire ants.

      --
      My present is the activity I am currently engaged in with the purpose of turning the future into a better past.
    12. Re:Unionize by Curunir_wolf · · Score: 1

      "...the vast majority of them haven't found a way to use their own scarcity to their advantage."

      The way: Unions.

      Face palm

      --
      "Somebody has to do something. It's just incredibly pathetic it has to be us."
      --- Jerry Garcia
    13. Re:Unionize by ByOhTek · · Score: 1

      Nope, the two sentences I specifically mentioned do not do that at all, in or out of context with the rest of the post.

      --
      Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
    14. Re:Unionize by jeffmeden · · Score: 1

      But other than my french friend I have no one that even joked about "organizing" software developers.... would love to hear well thought out arguments in its favor though. Don't mind reading an opposing point of view. Maybe I'll learn something...

      Step 1: realize that the hypothesis of the article in question (that developers are scarce and valuable) and the hypothesis of the GP (that the solution to the problem of capitalizing on scarcity is unions) are completely opposite. Unions serve one purpose, to take a large number of otherwise indistinguishable (and therefore disposable) employees and make them distinguishable again by the sole method of giving each one a (identical) contract with the employer that contains certain advantages for the employee (stable hours, stable wage, etc.) Also, it works better if the employees are otherwise not savvy when it comes to contracts (they will rely more on the union's efforts). Therefore to say that the way for a "good developer" to take home an appropriate wage (above-average, according to the article) is to unionize is completely wrong.

      Software developers, to date, fall into none of these buckets; good ones are still hard to come by, it is easy to tell the good ones from the bad ones (at least any good company does so, or perishes) and they are generally educated and therefore can recognize a fair/unfair deal when it comes to being employed. In the next 50 years, the trade of software development will likely have grown to become an interchangeable quagmire and it's constituents would benefit from unions, but it is certainly not today. Unions have no part in the current system, plain and simple.

    15. Re:Unionize by AtlantaSteve · · Score: 2

      Perhaps I should have explicitly told you to piss off, and that you're being a ridiculous goober. Sorry for also failing to make that message obvious in context.

    16. Re:Unionize by xero314 · · Score: 5, Interesting

      I have NEVER , during 15 years in the field, EVER encountered a competent IT professional who dreamed of being in a union.

      Now I can't prove my competence in a slashdot post, but I am a software engineer that fully supports unionization.

      I am fairly compensated, as I do a good job of negotiating what I believe I am worth. But there is more to unionization than compensation. Though I do support collective bargaining (which does not need to be seniority based, and can be performance based).

      Unionization can be used as a tool to bring product quality back into the hands of those that produce the product. Having a union to collectively support only quality changes should improve overall product quality.

      Unionization is a tool that can be utilized. I would much rather have more tools at my disposal than less (though we need not use every tool for every task).

      Just remember that the corporation is bargaining against you, as there goal is to maximize profit, and they are doing it collectively. If you want to even the score you do your bargaining collectively. But corporations have also done a great job to convince the American people that Unions are bad and lazy, so I doubt I'll be changing any minds here.

      Lastly, Unionization is fully in-line with Libertarian ideology, even the Neo Libertarians of the US Libertarian party, and the likes of Ron Paul. Collective bargaining is an important tool that allows capitalism to be successful.

    17. Re:Unionize by PoolOfThought · · Score: 1

      In the context of the rest of the post he has obviously limited his discussion to those that he has dealt with. Specifically, as he has now clarified even further, the "blow hards". If you're talking about the people you know and you have qualified it then it isn't a generalization beyond that group. He didn't say everyone is either ron paul or carl marx and that the ron pauls are better programmers. He said that those that he has come across and that he would classify as ron paul types are generally competent about their jobs. He MIGHT have insinuated (by leaving out the same statement about the marx group) that they were not as competent. He did not insinuate that all developers who are not of a ron paul type mindset suck at programming. I mean, this is pretty simple discreet math (logic / set theory) and if you're "reading into it" or adding "facts" then you're going way beyond what is needed to understand his comment within the context it was made.

      Out of context is, well, out of context. Not much to discuss there since someone who is taking things out of context wouldn't be worth have a discussion with. Those type of people just hear what they want and ignore everything else that was said.

      --
      My present is the activity I am currently engaged in with the purpose of turning the future into a better past.
    18. Re:Unionize by syousef · · Score: 2

      Gotta love slashdot. A personal attack based on skimming this guy's profile for 5 minutes qualifies as interesting.

      I've not known software engineers who wanted to be in a union either....but that is primarily a cultural thing. In other engineering disciplines unions are the norm. Also I make a lot of wise arse remarks. The days of slashdot being primarily a discussion board for serious topics is long over. Why don't you go ahead and take a look at my profile then malign me. Your ridiculous bad behaviour glorified on this board and you don't even see the irony of looking at how serious someone's comments are on that same board. I'd love to have you on my team. NOT.

      --
      These posts express my own personal views, not those of my employer
    19. Re:Unionize by Have+Brain+Will+Rent · · Score: 1

      I don't think it has to be an either-or situation. The classic professions - doctors, lawyers, architects, engineers (other than "software engineers") etc. - have managed to structure things so that they gain most or all of the benefits of unions with few of the drawbacks.

      --
      The tyrant will always find a pretext for his tyranny - Aesop
    20. Re:Unionize by Anonymous Coward · · Score: 1

      Unions do have some advantages, but IMHO unions work best for minimally skilled laborers. Guilds work best for skilled groups like developers. I.E. software devs working within a guild would be self organizing and policing, set their own standards, and companies that need work done would have a single place to go to negotiate the work they want done. They'd have the benefits sought after by unionization, while maintaining standards themselves, instead of the PHB forcing what buzzword bingo entry of the week down their throats.

    21. Re:Unionize by ArhcAngel · · Score: 1

      When companies act badly enough to their employees unions can be a great way to flex a little muscle to get them to straighten up. If a union would disband once the situation that necessitated it is abated I would gladly advocate and join. What we see today is unions that have lived long past their original charter and are in some cases worse than the companies they seek to extort.

      Add to that the fact that organizing developers into a cohesive group is akin to herding cats and you start to see how hard unionizing would be.

      --
      "A person is smart. People are dumb, panicky dangerous animals and you know it." - K
    22. Re:Unionize by Sponge+Bath · · Score: 3, Insightful

      No mod points today, so I'll post to keep your reasonable, polite and on-topic post from being buried by the "mod down anything supportive of unions" brigade. To the person modding the OP flamebait: If it's an echo chamber you want, there are plenty of other sites that will meet your needs.

    23. Re:Unionize by swillden · · Score: 3, Insightful

      Lastly, Unionization is fully in-line with Libertarian ideology

      Voluntary unionization, yes. But voluntary unions don't last; if the union is at all successful it begins to focus on perpetuating itself and its lock on the labor side of the bargaining table. In some cases scabs get beaten, maimed or killed. In other cases, the unions champion changes in the law that make non-union labor effectively illegal. Even when those extremes are avoided, intense peer pressure is applied to those who don't want to join the union.

      The biggest problem with unions and collective bargaining, though, is hidden in your parenthetical comment "which does not need to be seniority based, and can be performance based". No, it can't be performance based, because that requires an objective way to measure performance. The normal employer/employee relationship has a lot of fuzziness that allows hard-to-quantify performance factors to be taken into account. But unions need to establish clear rules and structures that can be written into the collective bargaining agreement, at least if the agreement is going to do anything more than specify minimums. That's why so many collective agreements end up being purely seniority-based: because it's about the only thing that can be objectively measured.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    24. Re:Unionize by Anonymous Coward · · Score: 1

      I have NEVER , during 15 years in the field, EVER encountered a competent IT professional who dreamed of being in a union

      I'm pretty damn competent and I've always dreamed of being in a union.

      In particular, I'd like to be part of one like this:
      SELECT firstName,lastName FROM account WHERE balance > 10000000
      UNION
      SELECT firstName,lastName FROM mortgages WHERE balance=0 and total>5000000;

    25. Re:Unionize by Anthony+Mouse · · Score: 2

      In other cases, the unions champion changes in the law that make non-union labor effectively illegal.

      That is really the problem with unions: If employees can choose whether to join or not, they can go to the negotiation with the employer as a non-union employee and take the union package as the starting point for the negotiation, with nowhere to go but up because the employee has the alternative of joining the union. So non-union employees will always be able to negotiate better compensation than union employees, and nobody will join the union.

      But if you're required to join the union then the union is in the position of a monopolist, and the entirely expected thing happens: It turns into a lazy, incompetent bureaucracy more interested in perpetuating itself than doing what it was created to do.

    26. Re:Unionize by Eli+Gottlieb · · Score: 1

      That sounds wonderful, but is it actually legal in the modern world?

    27. Re:Unionize by Eli+Gottlieb · · Score: 1

      You're not as scarce as you think you are. I'm not as scarce as I think I am. And if you look into me, I think you'll find I'm reasonably scarce.

      Union? If that's what it takes. Guild or professional organization? Preferably. Unorganized? It sucks.

    28. Re:Unionize by Anthony+Mouse · · Score: 1

      Truly scarce resources are capable of getting more than they would be unionized because they are not lumped in with the not quite so scarce.

      That's not it at all. You can create a union that has only in-demand members. Then they can negotiate to be paid $250,000/year instead of $100,000.

      The reason that doesn't happen is that smart people realize what happens when everyone in the market is being paid more than they're worth: You create a market incentive for oversupply. Do you know what happens when a job pays $250,000/year? Everybody who is even remotely capable of learning how to do it does so, and the market is soon flooded with qualified workers. Five years later your scarcity is completely extinguished and unemployment in the field creates a ready market for scabs which destroys your union. Then you're either left without a job or with one that pays $40,000/year instead of $100,000.

      The unions for unskilled labor have learned this the hard way: A union job is fat city for a few years, until the factory you're working in is due for renovation and instead of renovating it the company just closes it and builds a new one in China. (The exception is government employees unions, which become powerful lobbyists that can fend off their destruction through politics regardless of market forces.)

    29. Re:Unionize by xero314 · · Score: 1

      Voluntary unionization, yes.

      As far as I am aware, and I could be wrong, all union membership is voluntary in the United States. Membership in certain trade organizations, like Professional Engineering, is not, but that's another issue entirely. But let us not limit a collectives capabilities to bargain. If they have the strength to negotiate a contract with a corporation that says the company can not hire non-union workers, then more power too them.

      In some cases scabs get beaten, maimed or killed.

      Harm is amoral and illegal, and also is no more a side affect of unionization than it is a side affect of any other activity.

      No, it can't be performance based, because that requires an objective way to measure performance.

      Before becoming a software engineer I worked in a Union shop that included in it's compensation performance based reviews (I chose not to be a union member but I was still subject to the same compensation regulations). Seniority is a valid basis, as you shouldn't be keeping people that are not affective, but performance can easily be included as well.

      The normal employer/employee relationship has a lot of fuzziness that allows hard-to-quantify performance factors to be taken into account.

      The fuzziness in the normal relationship is what causes compensation to be based off of personal interactions and socialization, rather than based on performance. And though I have spent a lot of time perfecting the art of communication, I disagree with compensation being based on friendliness, when high performing individuals are lesser compensated because they lack certain social skills.

    30. Re:Unionize by mjwx · · Score: 1

      I have NEVER , during 15 years in the field, EVER encountered a competent IT professional who dreamed of being in a union. Union culture is pretty much the antithesis of what makes a good engineer tick.

      About both unions and engineers. The idea of labour unionism is the ability to negotiate as a whole, I cant see who a proper engineer sees that as counter productive. Most of the hate of unions is based on political scaremongering, not actual fact. Germany survives quite well on collective bargaining, the ability for workers to act as one whole gives them power equal to the company ensuring that neither side can effectively abuse a stronger position.

      Now the problem with getting IT workers to organise is the same as getting IT workers to decide what to have for lunch. Every one has a separate want and agenda, being engineers means they'll argue for what they want and not necessarily negotiate very well. I often use the joke "the last time IT tried to unionise, we met for 3 days and in that time we couldn't decide whether we should be a Union, Guild or Clan."

      --
      Calling someone a "hater" only means you can not rationally rebut their argument.
    31. Re:Unionize by Anthony+Mouse · · Score: 1

      But let us not limit a collectives capabilities to bargain. If they have the strength to negotiate a contract with a corporation that says the company can not hire non-union workers, then more power too them.

      The flaw in your thinking is that unions aren't just normal organizations. They have their own laws. They get exceptions for things that would otherwise violate the antitrust laws. You aren't allowed to just refuse to negotiate with them. If your argument is that we shouldn't treat them differently than other organizations, businesses will agree with you. But then they wouldn't exist because half of today's union activities would be illegal and nobody would negotiate with them without being obligated to by law.

      Harm is amoral and illegal, and also is no more a side affect of unionization than it is a side affect of any other activity.

      This is a pretty ridiculous statement. Unless it is your contention that unionization has resulted in less violence than, say, entomology, you know that it's wrong. You're very casually dismissing a hundred years of violence and intimidation.

      Seniority is a valid basis, as you shouldn't be keeping people that are not affective, but performance can easily be included as well.

      Seniority is not a valid basis. It's the root of the problem. People get seniority, then stop trying because they can't be let go.

    32. Re:Unionize by PoolOfThought · · Score: 1

      Anybody that tells me that I should research them is almost guaranteed not worth researching, and probably not that scarce. However, just in case I was wrong I went ahead and checked you out. My goodness I'm getting old, and I'm not that old....

      You know, when I got my BS degree in CS I knew I was scarce. I had done some pretty cool stuff and had been doing it longer than anyone I knew. Then I got a job and with it I got a clue (well it took a while actually) . After a while I found I wasn't actually that scarce - or not in ways that mattered. I went back to school while still working this same job and got my masters in CS. I did more cool stuff in grad school and was making serious enhancements (we were making things happened that weren't even hoped for when we got started) on the systems I was building at my j-o-b and I just knew once again that I was one scarce dude. The funny thing is I didn't know why I was scarce until I got an offer for my next job.

      Part of what makes me scarce has nothing to do with what I know about computers per se. It's what I know about the industry in which I work. It's having built a system from the ground up multiple times and for more than one company. You better believe I'm the right guy to build this type of system. There may only be 10 guys in the US that know what I know about the types of systems I've built. It's about knowing the history of that industry and all the little gotchas that come along with it. It's knowing exactly what the type of people that want to hire me need and it's having the ability to come in and do it. It's not that I have a degree. It's not that I've been programming at some level for 20 years. It's not the programming languages I've learned. It's that I'm the right guy for the right job. Not for every job, but for the right job. A lot of people know more about programming in the newest languages than me, but very few can say they can do what I do and could provide results right away. They would take several months to even understand (not KNOW deeply; just understand) the industry... forget about the programming. They would take longer than that to figure out what they need to know in order to understand WHAT they should be programming.

      Until someone has been doing the work for some time they probably don't have a clue about what they do or don't know yet. They don't know if they are scarce or not. One doesn't simply become scarce when they learn to program, they become scarce because of the jobs they can do - the tasks they can get done. Some might be born scarce, but unlikely.Most will become scarce because of what they pick up along they way. And you can be both scarce and useless (for example, being the only one that knows some language nobody needs). The sooner you realize that the better it will be for you.

      Now get tf off my lawn!

      --
      My present is the activity I am currently engaged in with the purpose of turning the future into a better past.
    33. Re:Unionize by russotto · · Score: 1

      But there is more to unionization than compensation. Though I do support collective bargaining (which does not need to be seniority based, and can be performance based).

      But oddly enough, always seems to have seniority as the major component.

      Unionization can be used as a tool to bring product quality back into the hands of those that produce the product. Having a union to collectively support only quality changes should improve overall product quality.

      Having a bunch of politically-oriented greybeards who once (or currently) held the title "developer" decide on the contents of the three-ring binder one must follow is not much better than letting the pointy-haired boss with the latest management book do it.

      Just remember that the corporation is bargaining against you, as there goal is to maximize profit, and they are doing it collectively. If you want to even the score you do your bargaining collectively.

      Except that I can't. No matter what I do, I'm an individual. Bringing a union into it just makes it a three-way bargain, and assuming the union is on my side is a good way to lose.

    34. Re:Unionize by Stiletto · · Score: 1

      So non-union employees will always be able to negotiate better compensation than union employees, and nobody will join the union.

      Not necessarily. Company: "Your performance this year does not qualify you for more than the compensation you'd make in the union. Take the union package or leave."

    35. Re:Unionize by Stiletto · · Score: 3, Interesting

      I am fairly compensated, as I do a good job of negotiating what I believe I am worth. But there is more to unionization than compensation. Though I do support collective bargaining (which does not need to be seniority based, and can be performance based).

      The collective bargaining aspect alone would be a huge boon to Software Engineering and IT salaries. It's appalling how IT workers (who tend to be introverted and lack negotiation skills) are routinely fucked in terms of compensation.

      It's both sad and funny--the engineers who believe they are being fairly compensated and who are confident that they're paid "above average" tend to be the ones getting royally screwed.

    36. Re:Unionize by Anthony+Mouse · · Score: 1

      How does that make it more advantageous for them to join the union? Even if it's only the same compensation, the employee can take it without joining and get out of paying union dues.

      Plus, it isn't exactly common for a company to give an employee an ultimatum to join the union or quit. Notwithstanding laws to the contrary, it's pretty difficult to be so useless that they won't at least give you half the money it's worth to them to not have another union employee.

    37. Re:Unionize by xero314 · · Score: 1

      As I said above I previously worked for a union shop but was not the member or the union. I received the same compensation as the union employees and even received union representation if needed such as for disciplinary action. But there are things I did not get because I was not a union member. I was not eligible to receive compensation during a strike, and I had no say in the union negotiations.

      The only reason I received those benefits is because the union negotiated them and made it contractual that the company could not hire non-union members fro less than union pay. Had the union not negotiated such then the company would have hired lower quality, lower cost, resources. So I did reap the benefits of unionization without being a member. That actually makes me even more supportive of unions, since there is no way a corporation would have worked on my behalf for free.

      And just a tid-bit for those that don't know, 22 US states have right-to-work regulations. What this means is that the Union and companies can not enter into contracts that force union membership.

    38. Re:Unionize by xero314 · · Score: 1

      The flaw in your thinking is that unions aren't just normal organizations. They have their own laws.

      This is not a flaw of unionization or a valid argument against unions, but go ahead and argue against the regulations. I personally would support removing any laws that protect unions specifically, as many states have done with their right-to-work laws, but if and only if we also remove corporate personhood and other corporate protections. But that is beside the point, since supporting unionization has nothing to do with supporting current regulation.

      You're very casually dismissing a hundred years of violence and intimidation.

      If you were to add up the total number of deaths directly linked to unionization it would considerable lower than many other organizations and actions. The most obvious is the military, and few people would support a wholesale disbanding of the military. Second would be corporations, with disasters like that caused by Union Carbide out numbering the union actions in one incident. Nuclear power, the war over oil, tobacco, alcohol, suicides from the stress of higher education, and these are just a few off the top of my head. These are a mix off good and bad things. The point is that unionization is not amoral, any more than say something like religion. Sure the inquisition killed numerous people, but the quakers and the Mennonites have not hard any one (with a couple rare notable exceptions). The unions of today are not the thugs of the industrial revolution, and even then most union members where moral and law abiding citizens. And that's not even talking about the number of lives saved through improved working conditions that was brought about by unionization.

      Seniority is not a valid basis...because they can't be let go

      Your are mixing up loosely related issues. Seniority is a valid basis if you chose to only keep competent and productive employees. The fact that getting rid of incompetent employees might take a bit of a paper trail is no reason to argue that seniority is invalid. In most states you don't even need a paper trail. Sure the unions are there to protect employees from wrongful termination, but trust me, if the person deserves to be let go the unions will not protect them. The idea that unions protect incompetents is a myth, intentional or otherwise, that undermines the reality of unionization.

      Keep believing the myths if you must, but I would suggest that you educate yourself, with first hand experience if possible, before dismissing the benefits of unionization.

    39. Re:Unionize by tomhudson · · Score: 1
      It's called a professional corporation.

      Nolo: Your Legal Companion. Retrieved 2008-06-26. "A legal structure authorized by state law for a fairly narrow list of licensed professions, including lawyers, doctors, accountants, many types of higher-level health providers and often architects. Unlike a regular corporation, a professional corporation does not absolve a professional for personal liability for her own negligence or malpractice. The main reason why groups of professions choose this organizational structure is that, unlike a general partnership, owners are not personally liable for the malpractice of other owners. In some states, limited liability partnerships offer this same benefit and may be more desirable for other reasons."

      Engineers have to be a member of their state or provincial professional order or corporation to practice, same as lawyers, etc. Of course, the day that software programmers have to adhere to the same code of ethics as professional engineers is the day that they'll have to tell their bosses that it would be both unprofessional and unethical to do 50% (conservative number) of what they're being asked to do in the way that they're doing it, because of lack of proper resources and poorly documented procedures.

    40. Re:Unionize by stanlyb · · Score: 1

      Just like the teacher's union? It all started well, and look now what a monster we have. As a long time IT professional, i realized that my biggest asset is flexibility, or with other words being able to work for many different companies in many different areas, which have only one thing in common: they all need software developers. If there was this monster, the UNION, i would not be able to compete with all the crap they produce, and with all the idiots that are already there, and whose only advantage is that they are already unionized. And just for the record, it could become more clear for you if you think in terms of "bazaar and the cathedral". One only, the "cathedral" is the union.

    41. Re:Unionize by tehcyder · · Score: 1

      Union culture is pretty much the antithesis of what makes a good engineer tick

      Proper mechanical, electrical or civil engineers have to belong to professional bodies the same way that lawyers, architects or doctors do, and those bodies are just a posher and more restrictive version of a union.

      I see no reason why "software engineers" shouldn't do the same. You're not rock stars or poets, OK?

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    42. Re:Unionize by Eli+Gottlieb · · Score: 1

      You seem to have missed my point and gone off on a big crotchety rant. My point was: I'm scarcer than a lot of the hot-shots who think they're scarce, but on a conscious level I'm not scarce. If I'm scarce, I'm artificially scarce: I invested time learning things that other people could learn (or if someone actually trained them at their job), and I did things that other people could do -- all if they had the time from earning this month's rent. People could do the same with your skills and experience, I guarantee it. I'm not scarce. You're not scarce. No mere laborer is so scarce that he can't be replaced if the need is dear enough. If your employers felt they needed to, they would throw you out on the street and train me or some other monkey to take your job.

      Welcome to capitalism.

      And you can be both scarce and useless (for example, being the only one that knows some language nobody needs).

      Oy mate, I'm the only one who knows the language I'm creating. No shit. I don't expect others to know it, or consider it a job skill. Lay off that one.

    43. Re:Unionize by s73v3r · · Score: 1

      Doesn't that mean that developers would have to be licensed by the state? And that the developers would be required to write bug-free code or be held responsible?

    44. Re:Unionize by PoolOfThought · · Score: 1
      We're not talking "everyone is different just like the snowflakes so everyone is scarce and yet no one is because there are lots of snowflakes". We have an actual frame of reference for this conversation and it is based on the value of IT people in the business world.

      All you have said as far as I can tell is that no one is special. And that's true... and not. Some people have a skill set and an existing knowledge base WAY more valuable than others. But only in certain circumstances. Take that person and put them somewhere else and they'll be f-ing useless for quite a while. They won't have the background knowledge they'll need to do the work that needs to be done for the person that needs it done. Please think about that for a minute and I just truly can't imagine you not seeing it.

      Sometimes people need work done RIGHT NOW. Like... you know... they are competing against another startup and first one there wins. Or they are about to lose a major customer and they need someone to build what they need right now. You can't walk in the door and do that job just because you have an IT degree. It's just not happening. I can't walk in the door and do certain work. I would have neither the experience in the particular technologies nor the background to understand wtf they want me to do. People that have those... they're scarce. Many many programmers know code and could give a shit about the business they support. For that reason, they're not scarce to their employer. Or to any other employer.

      Oy mate, I'm the only one who knows the language I'm creating. No shit. I don't expect others to know it, or consider it a job skill. Lay off that one.

      For someone who claims that noone is special you're pretty damn vain. I wasn't even making a reference to your project. I was actually referencing my own graduate work in AI involving PROLOG and a custom language we created to assist in non-routine problem solving within software agents. You know how much anyone cares about that work right now (other than me and the others on the team)? It makes for interesting conversation sometimes, but that is about it. I still mess with it occasionally and I suppose in a certain world my involvment with it would make me more scarce in a way that adds value to someone's team. But in and of itself it's worth nothing NOW. In any case you're getting all upset as if I said your dog was ugly or something... and even if I did I don't know your dog... so why would you get pissed about that? If it makes you feel warm and fuzzy I can tell you your project looks interesting, but it has nothing to do with the context of the discussion.

      --
      My present is the activity I am currently engaged in with the purpose of turning the future into a better past.
    45. Re:Unionize by PoolOfThought · · Score: 1

      You seem to think of these people as skilled labor. I'm guessing it is only because "smart people do it" or because "only those willing to take the time to learn it do it". IT is probably more skilled labor than some other sorts, but as you pointed out it's not all THAT skilled.

      Most valuable will be those that understand the industry and the company that they are supporting. It's not being able to build to a spec (that's important too), but it's being able to UNDERSTAND why. To be able articulate other options rather than just "do the job" or argue and sound like some snooty dev that knows everything. Those who truly know what is going on within the company they work for are scarce and they're going to succeed. They aren't going to need a union to help them earn their magic number. And unionizing them would be weird because their actual value to most other employers in need of IT workers would be much less that with their current one. I suppose you could get real specific, but then you're missing out the numbers game that helps make unions work.

      Perhaps there is a need for a union for non-scarce IT workers - ones that just want to go whack on the keyboard and call it day when 5:00pm rolls around no matter what else is happening. There is certainly no shortage of them and they can therefore be abused as someone else will happily fill their role if they make a stink. But those that choose to be scarce on their own don't need a union to make them so.

      --
      My present is the activity I am currently engaged in with the purpose of turning the future into a better past.
    46. Re:Unionize by Eli+Gottlieb · · Score: 1

      I was actually referencing my own graduate work in AI involving PROLOG and a custom language we created to assist in non-routine problem solving within software agents.

      That actually sounds pretty cool. Got a publication link?

      Sometimes people need work done RIGHT NOW. Like... you know... they are competing against another startup and first one there wins. Or they are about to lose a major customer and they need someone to build what they need right now. You can't walk in the door and do that job just because you have an IT degree. It's just not happening. I can't walk in the door and do certain work. I would have neither the experience in the particular technologies nor the background to understand wtf they want me to do. People that have those... they're scarce. Many many programmers know code and could give a shit about the business they support. For that reason, they're not scarce to their employer. Or to any other employer.

      So custom-built commodities are scarce, while mass-produced ones are non-scarce? Amazing, why didn't I see it before?

    47. Re:Unionize by Anonymous Coward · · Score: 0

      Unfortunately, unions don't actually create collective bargaining. What they do is they create yet another powerbase for power-hungry sociopaths to cling to. What ends up happening is that there are a few people at the head of unions who make nearly all the decisions/negotiations and everyone in the union now must abide with those decisions.

      What's even more interesting was I was a student at UW when the teamsters were trying to unionize the grad students. You could see the divide between those who wanted it and those who didn't. That divide was typically whether or not the student was in a valuable field, and there was a strong line between the hard sciences and liberal arts. Basically the students who wanted to unionize were the ones who made less than union promised wages, and the ones who didn't were already making significantly more than said wage.

    48. Re:Unionize by PoolOfThought · · Score: 1

      So custom-built commodities are scarce, while mass-produced ones are non-scarce? Amazing, why didn't I see it before?

      My sarcasm detector is going off. I'll just assume you chose to miss the point again... I'm pretty sure I've been as clear as I'm willing to take the time to be right now, but sometimes it's best to just say "okay". So, thanks for the discussion opportunity. I atleast got the chance to put my own thoughts on the matter down so it was not a total waste. Good luck.

      --
      My present is the activity I am currently engaged in with the purpose of turning the future into a better past.
    49. Re:Unionize by tomhudson · · Score: 1

      Doesn't that mean that developers would have to be licensed by the state? And that the developers would be required to write bug-free code or be held responsible?

      They're licensed by their professional corporation, which sets the standards for practice in their state/province.

      And yes, they would be responsible for their code. So, no more "just f***ing push it out, we can patch it later" from bosses. Same as engineers, a company that insisted on that would find that they could no longer hire anyone.

    50. Re:Unionize by Anthony+Mouse · · Score: 1

      This is not a flaw of unionization or a valid argument against unions, but go ahead and argue against the regulations. I personally would support removing any laws that protect unions specifically, as many states have done with their right-to-work laws, but if and only if we also remove corporate personhood and other corporate protections.

      The entire concept of a union is a violation of the antitrust laws. They have a specific exemption otherwise they wouldn't exist.

      As for corporate personhood, I still have no idea what the crap the people who argue against it are talking about. Corporations don't actually exist. They're legal fiction. The idea that "Microsoft" can do anything is corporate personhood, because there is no person called Microsoft who you can go and punch in the face. When "Microsoft" ties Internet Explorer to Windows, there is actually a real human person in Redmond who writes the code tying Internet Explorer to Windows. What thing that "corporations" do would you expect eliminating "corporate personhood" would prevent? They don't do anything now, we just create the fiction that they do because it's easier to keep track of that way. I suspect that actually eliminating corporate personhood would make people very angry, because the result would be that some guy who makes $40,000/year and has a negative net worth is the one on the line when he dumps barrels of toxic waste in the river, instead of the corporation he works for that might actually have some assets to pay the victims.

      If you were to add up the total number of deaths directly linked to unionization it would considerable lower than many other organizations and actions. The most obvious is the military, and few people would support a wholesale disbanding of the military.

      You have changed your argument from "unionization causes less violence than stamp collecting" to "unionization causes less violence than all out war." Moreover, people are generally agreed that we should do whatever we can to avoid wars.

      You also ignore that different things have different values. You need the protection of a military a lot more than you need a union, because without a military the other guy's military will come and kill you. There is no thing a union does that can compare in the slightest with not being raped and murdered by an invading army.

      Seniority is a valid basis if you chose to only keep competent and productive employees.

      You're ignoring the possibility I already mentioned that an employee will become less productive over time once seniority makes their need to remain marketable decline.

      Sure the unions are there to protect employees from wrongful termination, but trust me, if the person deserves to be let go the unions will not protect them.

      Unions will only allow someone to be let go for cause. If you haven't done anything "wrong" even if you're lazy and stupid and you could be replaced with someone else who will do twice the work in half the time for three quarters of the pay, you can't be replaced. That makes the company less efficient, which reduces the amount of money they have available to pay other employees and makes everyone poorer.

    51. Re:Unionize by xero314 · · Score: 1

      I would suggest spending some time actually researching what happens in Union. You would probably even do well to work in a Unionized environment. Do yourself a favor and do so in a union that has members in both a right-to-work state and one without right-to-work regulations. Spending a little time in a union environment is leaps and bounds beyond anything you will ever see or read about labor unions. Mass media is very much biased against Unions, since unions have fought for their employees to be treated well and fairly compensated, but if you don't have the time or opportunity to be in a union environment I'm sure there are some good books out there that could explain the truth about unions (I don't know any because I lived it and never felt a need to read about it).

    52. Re:Unionize by Anthony+Mouse · · Score: 1

      Mass media is very much biased against Unions, since unions have fought for their employees to be treated well and fairly compensated

      You're resorting to conspiracy theories. I mean look at the media coverage of the Walker thing a few months ago. You had Jon Stewart on the television every night telling people that getting rid of collective bargaining for one state's public sector unions (and not even the union itself) is eliminating their "right to exist" as though they would somehow all be killed. And he's the reasonable one. Meanwhile a teacher who dared to go on television and agree with Walker was thanked for her opinion with union hate mail and efforts to take her job away.

      The problem is this: Look at some state-level Democratic politicians on opensecrets.org. See how many get paid by public sector unions. It's pretty much all of them. At the state level the unions are worse than the corporations. They've got a nice racket going: The union gives the politician money to get elected, the politician gives the union more tax dollars, which the union can launder part of back into the politician's campaign fund. The extra money comes mostly in the form of benefits and optional overtime so that if you compare base salaries to those in the private sector it always looks like public sector employees are getting ripped off, even though they aren't, so you can always rationalize giving them more tax dollars that way.

      What's worse is that public sector unions have no value, since the government they're negotiating with is the one that makes the law as to whether they can have a union at all. Which means that it inherently, necessarily has all of the negotiating power no matter what. If the government thinks government employees deserve more, they get more. If not, they don't. The union has no leverage as a union. Its only leverage comes in the form of campaign contributions. Which makes it not a union, but a taxpayer-funded lobby group that advocates against the interests of taxpayers.

      However, since the Democrats through this arrangement are dependent on the unions, you can't get rid of them. Because the Democrats will do everything they can to stop you, since you'll be preventing them from getting reelected by depriving them of campaign money. And since private pro-Democratic-party interests also know this, you get the media campaign against eliminating sycophantic public sector unions by Democratic-party-leaning media.

  5. Idiots by sexconker · · Score: 4, Insightful

    Well, then Forbes and Venkatesh Rao are idiots.
    The safest investment for corporations and individuals is corporations, as usual. They control everything and they're not going away.

    Nobody wants talented coders. People want cheap, get-it-out-the-door coders. And those are in India.
    People will buy any old fucking thing you slap a lower case i in front of. Why bother trying? Why bother risking a talented coder coming along and doing stuff on their own? Why, they could get the sense that have some sort of control over, or input into, the project. If they leave before we ship, no one will know how to fix everything. It's best to keep monkeys doing the monkey work, and to pay a "project manager" to vaguely tell them what to do.

    A "talented" coder is like a UFO. Everyone talks about them. Some of them say the place in the other business park has one. But no one's really sure what one looks like, or how to tell if one's real when it comes time to interview people for a position.

    Furthermore, coders, especially the "talented" ones, don't exactly fly the banner of allegiance. They'll leave at the first opportunity to make more money. If you don't let them take control of a project, they'll either do it their own way, or go somewhere else that lets them do it their own way. Have you heard of open source software? Nothing ever gets done because they keep "forking" things when they have their own ideas!

    If you give money and attention to talented coders, they'll think they're worth something, and then you'll have to compete for their work!

    No, thank you. I'd much rather we all agree to keep treating them like shit, paying them shit, and not really understanding what they do.

    1. Re:Idiots by Pope · · Score: 5, Funny

      People will buy any old fucking thing you slap a lower case i in front of. Why bother trying?

      Don't be silly; nobody bought an iPaq.

      --
      It doesn't mean much now, it's built for the future.
    2. Re:Idiots by Timothy+Brownawell · · Score: 2

      The safest investment for corporations and individuals is corporations, as usual.

      It's turtles all the way down?

      At some point the value in these investments needs to either come from making things, or doing things. This is saying that the (current) best investment is in doing/making things that make it easier (or cheaper) for others to do/make things.

    3. Re:Idiots by Maximum+Prophet · · Score: 1

      ...A "talented" coder is like a UFO. Everyone talks about them. Some of them say the place in the other business park has one. But no one's really sure what one looks like, or how to tell if one's real when it comes time to interview people for a position.

      You're just not looking in the right places. Once you've found one, you're certainly not going to tell the world about it. But, you're right that they can be difficult to control and even downright dangerous when spooked.

      --
      All ideas^H^H^H^H^Hprocesses in this post are Patent Pending. (as well as the process of patenting all postings)
    4. Re:Idiots by emuls · · Score: 0

      I did :(

    5. Re:Idiots by sexconker · · Score: 0

      The safest investment for corporations and individuals is corporations, as usual.

      It's turtles all the way down?

      At some point the value in these investments needs to either come from making things, or doing things. This is saying that the (current) best investment is in doing/making things that make it easier (or cheaper) for others to do/make things.

      That would be a good point if our economy was founded on value. But it's not. It's founded on debt.

      Even in a value-based economy, yes value comes from making things, but the corporations that use computers to make things have already know about outsourcing. It's already easy and cheap to make things.

      The article talks about "talented" developers as if anyone wants talented developers. They don't - they want labor. Even the huge success stories (facebook, angry birds, iThing) that everyone wants to repeat aren't about talented coders, they're about talented marketers.

    6. Re:Idiots by sexconker · · Score: 1

      ...A "talented" coder is like a UFO. Everyone talks about them. Some of them say the place in the other business park has one. But no one's really sure what one looks like, or how to tell if one's real when it comes time to interview people for a position.

      You're just not looking in the right places. Once you've found one, you're certainly not going to tell the world about it. But, you're right that they can be difficult to control and even downright dangerous when spooked.

      The problem is that by the time someone in HR learns of the "right places", they're no longer the right places.
      I remember when having a linkedin profile was considered the mark of a serious professional eager to make business contacts. Now it's just yet another site to check, like monster or dice.

    7. Re:Idiots by vencs · · Score: 0

      A "talented" coder is like a UFO. Everyone talks about them. Some of them say the place in the other business park has one. But no one's really sure what one looks like, or how to tell if one's real when it comes time to interview people for a position.

      Agree with this. 45 mins each with 4 strangers can be a better model for identifying talent in pros other than coders.

      Have you heard of open source software? Nothing ever gets done because they keep "forking" things when they have their own ideas!

      Disagree with this. Freedom in OSS lets you come up with innovation beyond deadlines, budgets, managers. Its not fast, but evolution wasn't either.

      --
      :wq

    8. Re:Idiots by msobkow · · Score: 3, Insightful

      Furthermore, coders, especially the "talented" ones, don't exactly fly the banner of allegiance. They'll leave at the first opportunity to make more money.

      Having repeatedly stayed on to try to deliver failing and late projects over the years in order to save a client's bacon, I find your comment not only insulting but dead wrong. I and many other people I work with actually have the integrity to do our level-headed best to get things done, even if management is pissed off because we couldn't get it done on their fantasy schedule or overly optimistic budgets.

      Real coders are ethical people who work on the code as much out of love of getting things done and the satisfaction of happy users as they are people who want to make money. Let's face it -- if you're only into money, this is the wrong industry to be in with all the fierce competition from cheap overseas labour constantly undercutting the rates.

      --
      I do not fail; I succeed at finding out what does not work.
    9. Re:Idiots by mdf356 · · Score: 2

      Don't be silly; nobody bought an iPaq.

      George Bush bought an iRaq, though.

      <rimshot>

      --
      Terrorist, bomb, al Qaeda, nuclear, yellowcake, kill, assassinate. Carnivore is dead... long live Echelon.
    10. Re:Idiots by Krishnoid · · Score: 1

      You misspelled it -- it's i-Rack. The similarities are unnerving, though.

    11. Re:Idiots by StikyPad · · Score: 1

      Furthermore, coders, especially the "talented" ones, don't exactly fly the banner of allegiance. They'll leave at the first opportunity to make more money. If you don't let them take control of a project, they'll either do it their own way, or go somewhere else that lets them do it their own way. Have you heard of open source software? Nothing ever gets done because they keep "forking" things when they have their own ideas!

      That's why The Fucking Article* says to invest in them by forming relationships, not by acquiring them as with traditional "human capital." The first project should be viewed as essentially forming that relationship, and any other value gained from it is superfluous. But after that, you let your team direct the company, not the other way around. Which makes sense really. If you have a product that looks and works like a really great shoe, then sell really great shoes. Don't throw it away because you wanted to sell hats. Likewise, if you have a team that can or does produce an awesome project that was outside of your initial scope, clearly your scope should be changed, not the project.**

      This is pretty much what Apple did with the iPod, leveraging that into their phone, tablet, STB, and possibly upcoming TV. They've made plenty of missteps over the years, but jumping on the success of the iPod was not one of them, at least from a profitability standpoint.

      * Thought I'd spell that one out for you too, just in case.

      ** Steve Jobs would probably say "Bullshit, micromanage your teams," but that's really only applicable if you're Steve Jobs, and then only if you believe he had more skill than luck in product design, and that his contributions in that respect were more important than his showmanship and marketing. In other words, don't do that.

    12. Re:Idiots by sexconker · · Score: 1

      Have you heard of open source software? Nothing ever gets done because they keep "forking" things when they have their own ideas!

      Disagree with this. Freedom in OSS lets you come up with innovation beyond deadlines, budgets, managers. Its not fast, but evolution wasn't either.

      -- :wq

      And from an HR / manager point of view, deadlines and budgets are more important than innovation.
      Perhaps you need to look up tongue in cheek.

    13. Re:Idiots by sexconker · · Score: 2

      Furthermore, coders, especially the "talented" ones, don't exactly fly the banner of allegiance. They'll leave at the first opportunity to make more money.

      Having repeatedly stayed on to try to deliver failing and late projects over the years in order to save a client's bacon, I find your comment not only insulting but dead wrong. I and many other people I work with actually have the integrity to do our level-headed best to get things done, even if management is pissed off because we couldn't get it done on their fantasy schedule or overly optimistic budgets.

      Real coders are ethical people who work on the code as much out of love of getting things done and the satisfaction of happy users as they are people who want to make money. Let's face it -- if you're only into money, this is the wrong industry to be in with all the fierce competition from cheap overseas labour constantly undercutting the rates.

      And by doing so you're seen as a mere laborer and you won't get management's respect, or money.
      If you got away and did something somewhere else, you're talented. If you stayed and did something successful, people will only notice how it was past the deadline, all the trouble getting there, etc. And they'll expect repeated success or better next time, for the same pay.

      Another person who needs to look up tongue in cheek.

    14. Re:Idiots by sexconker · · Score: 1

      Furthermore, coders, especially the "talented" ones, don't exactly fly the banner of allegiance. They'll leave at the first opportunity to make more money. If you don't let them take control of a project, they'll either do it their own way, or go somewhere else that lets them do it their own way. Have you heard of open source software? Nothing ever gets done because they keep "forking" things when they have their own ideas!

      That's why The Fucking Article* says to invest in them by forming relationships, not by acquiring them as with traditional "human capital." The first project should be viewed as essentially forming that relationship, and any other value gained from it is superfluous. But after that, you let your team direct the company, not the other way around. Which makes sense really. If you have a product that looks and works like a really great shoe, then sell really great shoes. Don't throw it away because you wanted to sell hats. Likewise, if you have a team that can or does produce an awesome project that was outside of your initial scope, clearly your scope should be changed, not the project.**

      This is pretty much what Apple did with the iPod, leveraging that into their phone, tablet, STB, and possibly upcoming TV. They've made plenty of missteps over the years, but jumping on the success of the iPod was not one of them, at least from a profitability standpoint.

      * Thought I'd spell that one out for you too, just in case.

      ** Steve Jobs would probably say "Bullshit, micromanage your teams," but that's really only applicable if you're Steve Jobs, and then only if you believe he had more skill than luck in product design, and that his contributions in that respect were more important than his showmanship and marketing. In other words, don't do that.

      And the article is wrong.
      How many startups failed miserably by betting everything on the up and coming celebrity developers?
      How many entrenched corporations crack the whip and get reliable results, minimal fuckups, and near-zero consequences for those fuckups?

      We're long past the point where a corporation has to give a shit about its laborers.
      Corporations want control, measured output, and measured profits. They don't want to innovate because that's risky. Let someone else innovate, and then copy them or buy them out. You may not like it, but that's how it is and it's not going to change.

      The latest corporate success stories are Google, Facebook, and Zynga. Everyone raved about how it's a dream job to work for those places and how they're so innovative. And now? Developers are on a leash, innovation is dead, and the whip is cracked, as usual.

      1) Do something people like
      2) Sell it
      3) Profit
      4) IPO / Get bought out
      5) Forget about #1 just cut labor costs to maintain #3

      No corporation in the history of the world has followed any other pattern after making it to step 3.

    15. Re:Idiots by Anonymous Coward · · Score: 1

      coders, especially the "talented" ones, don't exactly fly the banner of allegiance. They'll leave at the first opportunity to make more money.

      That's because coders that are ten times as productive as their peers think they're underpaid when the difference between their salaries is only ten percent.

    16. Re:Idiots by Anonymous Coward · · Score: 0

      This kind of thinking leads to

      A: In bubble times, you Hire lots of stupid people with no idea of what they are doing and don't care, who in turn make code that kinda-sorta looks like it works, but in fact doesn't. You hope to god when your employee's start using it that it does work. Why? Because you're paying your operations employee's 10% of market and for that price they don't care either. Thus, if the program has a bug; and since you aren't writing a business spec I guarantee you it will; that costs you $15k per day, you may not notice until 2 years after deployment.

      B: Your costs are always higher since you don't care if the code base is maintainable. So if there IS a bug after you've paid the contract, your you NEED a feature, you pay big bucks for it. Do you think the outsourcing company is going to hire someone to make a code base maintainable for anyone but them? Or the same developer that built your app is going to stick with that company or your project?

      C: Ensures a manager such as yourself has no idea of what a "great" developer looks like since great developers are smart enough to jump ship when they see a slave driver and if you happen to get talent you demotivate it into dust.

      D: Ensures you have ZERO Recourse when said outsourcing company screws you. You are too stupid to put in proper controls (e.g. source reviews by people who know what they are doing) into place and have zero control over the business processes that produce what you're getting. After all, those cost money; and if they scam you what are you going to do? Sue them? Pfft. The American subsidiary has zero capital on-hand, they transferred it all to India.

      Coders don't fly the banner of allegiance because management doesn't fly the banner of allegiance. They can't make long-term promises when it's possible they'll get bought up after 2 or 3 years. What can you possibly offer me aside from salary + Bonus? Stock? 401K? Incentive plan? Who even takes those seriously these days? Fact: If you aren't reviewing your employee's and asking them every 6-months to a year what makes them happy, don't expect to keep em'. You can only burn the smart ones once.

    17. Re:Idiots by vencs · · Score: 0

      ah.. you are here too!

      perhaps you need to look up the URL.

    18. Re:Idiots by Anonymous Coward · · Score: 1

      What you say might be true for short-term customers, but when you get into a long-term relationship with a customer, cheap stuff doesn't really pay off.

      I had worked at a place some years ago. It used to be a decent company and had some 'talented coders'. But then management started to think like you do and started reducing pay, laying off people with 'attitudes' etc. Everything went downwards after that. Most 'talented coders' left, leaving the place to low-pay monkeys.

      First, huge amounts of bug reports started coming from new projects. Customers wouldn't accept the product at all and refuse payment until the issues were fixed. This resulted in delayed payments, overtime, customer visits and more cuts from employee's paychecks. At some point, it became simply impossible to add a new feature to an older project because the new 'developer team' was too busy fixing bugs and creating new ones in the process. This resulted in more lost deals. After I quit, I didn't hear about them getting new deals for a long time. If these aren't concerns for a software company, I don't know what is.

      The problem with talented coders is only transient. When you hire a brat fresh out of college, of course he's going to think that he's the best thing ever around and knows better than anyone else. They will toil endlessly to make things 'better' since they're still in the exploring-and-learning mindset. A seasoned coder will not bother with that, he will have satisfied his hunger for exploring and will try to give you stuff that won't cause him headaches later. Talent is one thing, the ability to use it wisely is altogether another.

      When you don't have any talented coders, you will have the same problems as we had if the software you sell is supposed to work at all. You may gather 50 typists for the cost of a single good coder, but it can be the case that none of them can solve a critical problem the coder could easily solve.

      It's a simple principle. Garbage in, garbage out. As you start selling garbage, you will scare your customers away and you will downsize. As for the mandatory slashdot car analogy, think about a software company as a luxury sedan factory which needs talented workers to make sure everything is going smoothly. At some point you might say 'to hell with the talented workers, I will hire new people and pay them in nuts'. However, the guys working for nuts can make only bikes and soon you're trying to sell bikes to customers looking for luxury sedans. It just doesn't work. You're now in the bike market and there is huge competition there, let me tell you.

      If all you do is phone games or some website for small businesses, you will do better with the monkeys. They will work as you like and for as much as you give them. If your product is anything critical at all, you better get rid of all monkeys lest they screw up something. Finding talented coders is a difficult problem since the only judge for a coder is yet another coder, in technical matters. Everybody will tell you that they're the best and whatnot but only a coder can understand the depth of grasp of a coder. Self-confidence, experience etc. is just too easy to fake and to falsely believe in.

    19. Re:Idiots by Eli+Gottlieb · · Score: 1

      Furthermore, coders, especially the "talented" ones, don't exactly fly the banner of allegiance. They'll leave at the first opportunity to make more money. If you don't let them take control of a project, they'll either do it their own way, or go somewhere else that lets them do it their own way. Have you heard of open source software? Nothing ever gets done because they keep "forking" things when they have their own ideas!

      Hey, some of us would prefer shorter hours and more vacation time! Money's not everything...

    20. Re:Idiots by 0xdeadbeef · · Score: 1

      How many startups failed miserably by betting everything on the up and coming celebrity developers?

      None.

      How many entrenched corporations crack the whip and get reliable results, minimal fuckups, and near-zero consequences for those fuckups?

      None.

      You ask very poor rhetorical questions.

    21. Re:Idiots by TempeTerra · · Score: 1

      "You break it, you bought it"

      --
      .evom ton seod gis eht
    22. Re:Idiots by Lando · · Score: 1

      That may very well be, but good coders have the dedication to stick around when things get rough and to continue working. Now the reason a good coder will leave of course is when the company starts treating them poorly. Loyalty works both ways, when a company starts to take advantage of their position, requiring 80 hour work weeks, people to come in when there is a problem without compensation, lack of raises when to company is making money off their skills that is when a good coder will leave. I think the reason you're confusing loyalty with non-good coders is the fact that these people have to stay at the job. A good coder is probably smart enough not to believe company promises when the company starts to treat them poorly.

      Or do you expect them to get punched and then turn around and say, "Thank you sir, may I have another?" That's not loyalty, that's stupidity.

      --
      /* TODO: Spawn child process, interest child in technology, have child write a new sig */
    23. Re:Idiots by Anonymous Coward · · Score: 0

      Actually, I know the guy that bought an iPaq.

    24. Re:Idiots by russotto · · Score: 1

      Ahh, slashdot, where the obvious trolls are Insightful. Putting in the bit about Open Source was kind of overdoing it, don't you think?

    25. Re:Idiots by Anonymous Coward · · Score: 0

      Unsuccessful troll is unsuccessful.

    26. Re:Idiots by sexconker · · Score: 1

      Ahh, slashdot, where the obvious trolls are Insightful. Putting in the bit about Open Source was kind of overdoing it, don't you think?

      Ahh, slashdot, where people get whooshed.
      Let me get that for you...
      WHOOSH

    27. Re:Idiots by Anonymous Coward · · Score: 0

      hmm female or person with small kids i suppose? most males do not think work/private life balance is so important, are more into competition, reaching goals (like unrealistic schedule), working 80 hours/week (if carrot/stick is big enough), and being recognized as some kind of superstar, and usually start to "cool-down" only after getting kids, if even than

    28. Re:Idiots by Anonymous Coward · · Score: 0

      hmm exactly my experience, usually when we get older we start appreciating more important things in life, like family for example

    29. Re:Idiots by Eli+Gottlieb · · Score: 1

      Does "Eli" sound like a female name? Only to Gentiles...

      Person with small kids? Inshallah one of these days I'll have kids.

      But in my case: person with a girlfriend, person with friends, person with hobbies.

    30. Re:Idiots by Eli+Gottlieb · · Score: 1

      Coders don't fly the banner of allegiance because management doesn't fly the banner of allegiance. They can't make long-term promises when it's possible they'll get bought up after 2 or 3 years. What can you possibly offer me aside from salary + Bonus? Stock? 401K? Incentive plan? Who even takes those seriously these days? Fact: If you aren't reviewing your employee's and asking them every 6-months to a year what makes them happy, don't expect to keep em'. You can only burn the smart ones once.

      Time off work. It's one of the few things that cannot POSSIBLY lose value.

  6. Wisdom by lucm · · Score: 5, Insightful

    This is exactly how Rockefeller was thinking: when you come across talent, you hire, then you adapt your business based on the people available. Even if in the short term it does not fit in an existing MS-Project plan, over the years you build a strong core and the team is driving the business, not the other way around. And if people walk away to get more experience, you keep the door open so you can benefit from what they did elsewhere.

    Unfortunately, a lot of companies are doing the exact opposite because the MBAs are trained to manage by balance sheet, stock price and quarterly projections: short-term metrics.

    --
    lucm, indeed.
    1. Re:Wisdom by Maximum+Prophet · · Score: 3, Insightful

      Most employers are looking for Rumplestiskin employees. "If we just had people that could spin straw into gold, we'd rule the world." Then they either wait for Mr. R. to apply, or they take the first smooth talking huckster that claims to be able to spin gold. This is especially bad at the 'C' level.

      --
      All ideas^H^H^H^H^Hprocesses in this post are Patent Pending. (as well as the process of patenting all postings)
    2. Re:Wisdom by Amouth · · Score: 3, Insightful

      my favorite part about that is they often over look a real Mr. R because he doesn't have the normal look of the slick C level guy.

      --
      '...if only "Jumping to a Conclusion" was an event in the Olympics.'
    3. Re:Wisdom by Anonymous Coward · · Score: 3, Interesting

      Unfortunately, a lot of companies are doing the exact opposite because the MBAs are trained to manage by balance sheet, stock price and quarterly projections: short-term metrics.

      This is sadly true. I'm experiencing it first-hand. I work for a Fortune 50 IT company as a software developer and team lead for 8 other developers. I was recently given a new "stretch" assignment with the vague title of "architect" (which I'm still learning how to define) along with four other people from other organizations within the company. It comes with a pay bump, but I recently learned that the other four people got far better financial packages than I did.

      Throughout the process of creating the assignment, my management has consistently over-promised and under-delivered (financial compensation, timelines, and even job scope). I know that this is a positive move, but it could be *much more* positive, based on what I've seen by comparing notes with the others. My immediate manager understands that I could easily leave and work elsewhere, joining the steady trickle of coders and team leads that have moved to greener pastures over the last 12 months. My senior managers, though, don't seem to understand this.

      This assignment puts me in a possibly unique but precarious position, as mentioned in TFA. I know that I can get more (more money, a better title, more flexibility). I just need to figure out how to approach them, and get what the others got.

      Worst case, I exercise my right (as mentioned in the article) to accept the random interview requests that I get every month or so, and politely walk out the door.

    4. Re:Wisdom by Anonymous Coward · · Score: 0

      Very, very well stated!

    5. Re:Wisdom by Belial6 · · Score: 4, Insightful

      I'm not going to disagree with you, but I would like to put in that there is another factor that gets over looked.

      Middle management is a necessary job that is not taken seriously. I have worked for great middle managers, and I have worked for (lots) of bad ones. The C level management has no idea what the actual employees do. In a company of any size, they couldn't get a grip on it anyway just do to the vast quantity of different jobs being done. Middle management is there to manage the day to day work, and to report to the higher level management. When this breaks down, the C level management can't informed decisions, and the worker doesn't have the tools necessary to do their job effectively.

      Middle management has become such a joke that neither the C level management, nor the workers take them seriously. No doubt the fact that the C level management doesn't take them seriously is a big reason why so many people that are bad at management end up in middle management.

      I know that when I have worked for a middle manager that was skilled in his trade, my productivity has often doubled or tripled over the times I have worked for those that were not skilled in their field.

    6. Re:Wisdom by trancemission · · Score: 0

      Touche......

      Any 'grad' can code....

      Coders are 'ten a penny'

      The value is in people who understand what the *business* needs to develop.

      So many ways to skin a cat in this industry.

      Find someone who understands your business and how they can develop it and 'move it forward'.

      If they can also 'code' - look after them ;)

    7. Re:Wisdom by Kittenman · · Score: 1

      This is exactly how Rockefeller was thinking: when you come across talent, you hire, then you adapt your business based on the people available. Even if in the short term it does not fit in an existing MS-Project plan, over the years you build a strong core and the team is driving the business, not the other way around.

      Excellent comment. I've worked in several areas where a bunch of talented people were assembled, did the work, released the project and then broken up. Staff were blown to the four winds. Rocky would have us looking at what we can do with what we have, rather than what we want to do and who we get to do that.

      But I think reality is harsher - businesses are there to make money and do the whims of the CEO/Shareholders, not employ people.

      --
      "The greatest lesson in life is to know that even fools are right sometimes" - Winston Churchill
    8. Re:Wisdom by lucm · · Score: 2

      Throughout the process of creating the assignment, my management has consistently over-promised and under-delivered (financial compensation, timelines, and even job scope).

      From their perspective, this makes sense because they have short-term incentives. Talk is cheap, and leading people on is a typical management tactic.

      My immediate manager understands that I could easily leave and work elsewhere, joining the steady trickle of coders and team leads that have moved to greener pastures over the last 12 months. My senior managers, though, don't seem to understand this.

      Working for a Fortune 50 IT company has benefits (nobody will ask you to take out the garbage or change the printer toner, and you will never worry about bouncing paychecks), however the bigger the company, the more likely significant gaps will appear between management layers.

      --
      lucm, indeed.
    9. Re:Wisdom by lucm · · Score: 1

      Middle management has become such a joke that neither the C level management, nor the workers take them seriously. No doubt the fact that the C level management doesn't take them seriously is a big reason why so many people that are bad at management end up in middle management.

      In most companies, there is a serious problem with middle management because good managers are promoted - what is left is either on its way up or not worth much. This is a problem that is seen mostly in management because in specialized jobs (such as software development) there is a smaller ladder to climb.

      This is similar to the problem of teachers working in poor schools. The top teachers usually get better opportunities and they run away, so what is left is either waiting for their chance to go, or just coasting until retirement.

      --
      lucm, indeed.
    10. Re:Wisdom by Anonymous Coward · · Score: 0

      Coincidentally, Rao has a big series on the "Gervais Principle" about how people get promoted.

    11. Re:Wisdom by Doubting+Thomas · · Score: 4, Insightful

      I don't say this often. Hell, I never say this: this is one place where the military has the right idea about how to manage people. Or at least, my poor, second-hand understanding of military chain of command suggests that is so.

      Non-Commissioned officers are on a separate career path. They are expected to continue managing 'the workers' in some capacity for their whole career. They both know what has to be done and can sympathize with the poor bastards who'll get stuck doing it. They are not expected to seek a C level position. That's not their job. Getting shit done is their job, and no assignment or promotion will ever completely hamper that goal.

      Meanwhile, the commissioned officers never manage the workers. Occasionally junior COs will try get things done that are a Bad Idea, and an NCO (eg, a warrant officer) will tell them to "Kindly fuck off, sir.". These people ARE expected to seek a C level position. Perhaps most importantly, if you demonstrate an inability to eventually achieve a C-level position, you may find yourself unwelcome, and encouraged to leave. "Up or Out"

      I think where this breaks down when applied to civilians is that we don't distinguish people who DO from people who manage. If you can get things done, we should let you do that until the world ends. If you can't get things done, but you can kinda sorta interact with some people who do, should we really keep you around forever? It seems to me like maybe that's not such a good idea.

      --
      Just because it works, doesn't mean it isn't broken.
    12. Re:Wisdom by EricScott · · Score: 1

      Gosh, golly, gee. I didn't understand anything you wrote.

    13. Re:Wisdom by Anonymous Coward · · Score: 0

      From their perspective, this makes sense because they have short-term incentives. Talk is cheap, and leading people on is a typical management tactic.

      I've often wondered what sort of short-term fire / incentive I need to create in order to get what I want.

      Working for a Fortune 50 IT company has benefits (nobody will ask you to take out the garbage or change the printer toner, and you will never worry about bouncing paychecks), however the bigger the company, the more likely significant gaps will appear between management layers.

      That's true -- working here has benefits. I can log in and work from my company laptop anywhere in the world. In fact, I have internet access anywhere in the world, thanks to our VPN, and an extensive list of numbers, should I need to fall back to an actual modem (which I did in Europe, once). On the other hand, we can't easily get new wide screen monitors (this is a "Capital" expense, which is controlled by my boss's boss's boss's finance guy), projector bulbs (this is a "regular" expense, which must be approved by my boss's boss's boss's boss's finance guy, assigned to my area), or even whiteboard markers (the supply guys are just being cheap, I think).

      It's incredibly short-sighted.

    14. Re:Wisdom by lucm · · Score: 1

      From their perspective, this makes sense because they have short-term incentives. Talk is cheap, and leading people on is a typical management tactic.

      I've often wondered what sort of short-term fire / incentive I need to create in order to get what I want.

      Working for a Fortune 50 IT company has benefits (nobody will ask you to take out the garbage or change the printer toner, and you will never worry about bouncing paychecks), however the bigger the company, the more likely significant gaps will appear between management layers.

      That's true -- working here has benefits. I can log in and work from my company laptop anywhere in the world. In fact, I have internet access anywhere in the world, thanks to our VPN, and an extensive list of numbers, should I need to fall back to an actual modem (which I did in Europe, once). On the other hand, we can't easily get new wide screen monitors (this is a "Capital" expense, which is controlled by my boss's boss's boss's finance guy), projector bulbs (this is a "regular" expense, which must be approved by my boss's boss's boss's boss's finance guy, assigned to my area), or even whiteboard markers (the supply guys are just being cheap, I think).

      It's incredibly short-sighted.

      I think a quote from The Tao of Programming is de rigueur:
      "You perceive this immense structure and are disturbed that it has no rational purpose. Can you not take amusement from its endless gyrations? Do you not enjoy the untroubled ease of programming beneath its sheltering branches? Why are you bothered by its uselessness?"

      http://www.canonical.org/~kragen/tao-of-programming.html#book7

      Enjoy your shelter :-)

      --
      lucm, indeed.
    15. Re:Wisdom by PoolOfThought · · Score: 1

      How many layers do you have there? Geez I worked for a company that got bought by US Bank. Even after the reorg I didn't have a boss's boss's bosse's boss (including the CEO of USBank). And your current employer org chart shows that you have an extra one on top of that plus presumably a CEO over all of those?! Freaking amazing structure there.

      --
      My present is the activity I am currently engaged in with the purpose of turning the future into a better past.
  7. Career length by vlm · · Score: 3, Insightful

    investment is actually investment in people who will live out long careers in the sector

    long careers? He means ageism might kick in at 35 instead of 30? Sign me up!

    --
    "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
  8. We are a waste by tatman · · Score: 2

    Speaking for myself mostly, I spend most my free time playing games rather than developing a product or service. Yes I do invest in learning new skills and technologies. But once I get a grasp of it, I go back to my game.

    --
    I've always said English was my second language. Had Romeo and Juliet been written in C, I might have understood it.
  9. Sexy by Anonymous Coward · · Score: 0

    I am one sexy piece of meat. Oh, yes, I am :-P

  10. 10x Engineer by Maximum+Prophet · · Score: 3, Insightful

    The industry standard when I was in school, was that the average programmer could churn out 10 debugged lines of code a day. I know I could run at 300 lines of C a day if distractions were minimized and the coke machine didn't run out. I had friends that could do 600 without too much trouble. (none of us got good grades, because we were writing too much code.)

    These days the company I work for keeps the phones ringing, cube noise up, and enough meetings that I'm lucky to write a few lines. Some days go by without any objective measure of success.

    --
    All ideas^H^H^H^H^Hprocesses in this post are Patent Pending. (as well as the process of patenting all postings)
    1. Re:10x Engineer by fsckmnky · · Score: 3, Insightful

      the company I work for keeps the phones ringing, cube noise up, and enough meetings that I'm lucky to write a few lines. Some days go by without any objective measure of success.

      Remember all those people in your COBOL class that had perplexed and confused looks on their faces, and were only there because they required the class as part of their MBA coursework ? Those people are your managers, and their cost-benefit analysis said if they stuffed you at a tiny desk in the phone room, they could save $100 on floor space and cubicle walls.

      Go talk to some of them about a productive engineering environment. I'd lay odds the same perplexed look re-appears. ;)

    2. Re:10x Engineer by Anonymous Coward · · Score: 0

      Better yet, go work for a better company. Seriously, there is a *shortage* of good developers. There's no reason for you to stick with a company you don't like.

    3. Re:10x Engineer by Anonymous Coward · · Score: 0

      300 lines of C a day

      The dreaded LoC metric. We usually say it's meaningless; but it's not absolutely meaningless. The average problem in language X will take programmer C Y lines to code. Of course, nobody asks you to code an average problem, and you might be an A programmer or a D- programmer.

      I came into school sharper than average and have fond memories of beating my peers 3:11 in printed page count (we were required to hand in printouts!) simply because I knew how to code using lookup tables.

    4. Re:10x Engineer by Maximum+Prophet · · Score: 2

      Location, location, location.

      Don't want to move, don't want to extend my commute. Also, they pay me too much, and are very flexible with the hours. That causes a lot of inertia. (I could make more, if I took a pay cut in a new job, then worked my way higher, but I value my time too much)

      --
      All ideas^H^H^H^H^Hprocesses in this post are Patent Pending. (as well as the process of patenting all postings)
    5. Re:10x Engineer by dubbreak · · Score: 4, Informative

      These days the company I work for keeps the phones ringing, cube noise up, and enough meetings that I'm lucky to write a few lines. Some days go by without any objective measure of success.

      What's more important than the obvious lack of productivity that gives the company as a whole is the way it demotivates the employees.

      I was in a similar situation. I lost my private office to a shared office, then to an "open concept" plan. I went from 500+ lines/day C# to nearly none (unless I worked from home). It was the meetings, general drone of noise, lack of a door to keep sales and service personnel out.. etc. Interruption after interruption. It wore on me.

      We implemented some functions to try to prevent the interruptions (e.g. single point of contact within the software team, acting as the gatekeeper/barking dog), but it really wasn't enough. Software team productivity dropped from high 80s of % time spent developing to under 60. I was under 40% of my time spent developing due to my long term experience with the products. That combined with a non-competitive wage for our local market and I was extremely unhappy. I desperately wanted to be productive and wage wasn't a huge issue when I was a happy employee but it became quite important when I could make more at any other shitty job in town.

      Long story short I left to do independent contracting at a much higher rate. I much happier getting stuff done and getting paid what I know is a fair wage. The company I left is now looking for a replacement that will expect the wage I expected and will need 3-6 months experience with their products to be a contributing member of the team. It's costing them. Of course IF they find someone who is actually good (finding good devs is extremely difficult, I helped hire the last 2 member sof their team and 90% of the applicants were duds) they will still have problems keeping them productive and keeping them at all.

      A few local companies have it figured out and are getting most of the local talent (which often means poaching as talented people tend to have jobs). If the smaller private companies don't step up to maintain their current staff they are going to find themselves without talent and having to cough up a lot of money to attract talent to a high cost of living location and then train those people.

      --
      "If you are going through hell, keep going." - Winston Churchill
    6. Re:10x Engineer by kogut · · Score: 5, Informative

      >I know I could run at 300 lines of C a day Someone call security. We have a mid-level manager masquerading as a coder. I've never met a competent coder who considers lines-of-code/day to be an even remotely useful metric of productivity. Coders who eat through requirements like a shark through chum with tight, transparent patterns...those are the good ones.

    7. Re:10x Engineer by msobkow · · Score: 1

      Nonsense. A competent C/C++/Java programmer will produce more on the order of 1000 lines of debugged code per day, even with 25% of their time stuck in meetings. Nothing would ever have gotten done over the years if people could only write 10 lines a day!

      --
      I do not fail; I succeed at finding out what does not work.
    8. Re:10x Engineer by Anonymous Coward · · Score: 0

      And here when someone starts talking about tight, transparent patterns we usually look behind them at the failed projects they have worked on with them...

    9. Re:10x Engineer by Have+Brain+Will+Rent · · Score: 4, Interesting

      On the last moderate sized project I worked on where I had full control of development IIRC I ended up with about 70,000 lines of code, i.e., all comments etc stripped out. There would have been more code but (sigh...) about half way through the process the client changed course and about 30% of the code had to be ripped out as they no longer wanted that functionality - that code isn't included in the figure of 70,000 lines of code.

      Total time for the entire development process was about 1,800 hours - which included the above activities and, of course, understanding the pre-existing system, meetings, designing the solution, removing the code for the discarded functionality, more meetings, full documentation - source comments, system documents and substantial (>100 pages) user manuals, email with stakeholders, more meetings.

      It is in use by governments, businesses and universities and it took over two years before anyone found (what they thought was) a bug.

      However most people/businesses don't want to pay what it costs for that kind of result.

      To be fair I think figures like 10 lines/day usually mean that at the end of the entire process 10 lines that survived and are documented and survive testing account for a day of time. But still you really have to wonder about the people at the low end who managed to get the average down to 10 lines a day... were they producing code that was simply discarded wholesale? Were they producing negative lines of code, i.e., somehow intentionally or unintentionally sabotaging the efforts of others?

      --
      The tyrant will always find a pretext for his tyranny - Aesop
    10. Re:10x Engineer by Anonymous Coward · · Score: 0

      Last week I produced about -50000 lines of code (yes, that is a minus). Sad thing is that someone wrote and maintained that code half a year, before I replaced it with about 10 lines of code which I wrote within half a day.

    11. Re:10x Engineer by Anonymous Coward · · Score: 1

      If we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent" -- Edsger Dijkstra

    12. Re:10x Engineer by Anonymous Coward · · Score: 0

      I know it's not completely relevant, but I'd like to ask you: What would you say makes a "good" dev? I'm going to be starting CompSci at uni next year, but I've been programming for years as a hobby anyway and I've worked on a lot of smaller projects and trying to apply for some freelance as well. The point is, I know I'll be a good enough at simply writing code in 3-4 years, but what else are people actually looking for?

    13. Re:10x Engineer by Anonymous Coward · · Score: 0

      Maybe Prophet meant 10 substantial lines of new debugged code? If you eliminate insignificant comments, braces and line breaks, the actual number of lines decreases substantially. Not counting refactored or otherwise reused code also reduces the count.

    14. Re:10x Engineer by Anonymous Coward · · Score: 1

      I can write over 800,000 lines of bug-free code in a typical work day. It's easy: just tape down the Enter key.

    15. Re:10x Engineer by darkwing_bmf · · Score: 1

      If what you do is a) useful/relevant and b) can be understood by someone else a year after you leave the company then it's good code and you are a good developer.

    16. Re:10x Engineer by Have+Brain+Will+Rent · · Score: 1

      These figures generally mean executable statements so yes comments, blank lines, lines with just a brace are not included.

      Also, IIRC and I may not, being "debugged" means that it doesn't obviously fail when you try running it - but it doesn't mean "tested". Yes, there is a continuum.

      --
      The tyrant will always find a pretext for his tyranny - Aesop
    17. Re:10x Engineer by Anonymous Coward · · Score: 0

      -50,000 seems a bit extreme but yes, my example of this was someone trying to move a mysql db from Windows to Linux. The table names had upper and lower case characters - in the code, but not in the actual file names. So it croaked as soon as he tried it on Linux. He then spent several days trying to find all the occurrences where the table names were used and change them to what the file names were.

      I found him saying this to his boss to explain why he was behind. He also stated that it was a laborious process to find all the occurrences in the files because he had to go through each file line by line with a text editor - they were all in only 2 of about 25 files and followed a strict pattern. I guess he never heard of grep.

      I first tried to very gently point out to him that the root of the problem was that Windows was case insensitive and that Linux wasn't, to which he authoritatively replied that all mysql database implementations were case sensitive regardless of OS. I told him by email to just set the mysql switch to make the match against table names case insensitive. And, still gently, I explained how to use grep and use patterns in Linux. He adamantly refused to believe there was a problem with how he had approached the problem.

      Now what I saw was:

      • He clearly didn't think through the fact that this had in fact worked on Windows - which meant his idea of the problem had to be wrong.
      • It didn't occur to him that someone else might have had this exact same problem (whereby he might have suspected the existence of the case switch).
      • Even if the above weren't the case, his approach to finding the problem statements was ludicrous.
      • He was unable to accept help and instead became defensive and hostile...

      Well I didn't have to work with him so I just dropped it but I had seen him do things with a similar "flavor" before... yet he kept being hired - he was, on the surface, cheap.

    18. Re:10x Engineer by wmbetts · · Score: 1

      I was a company that had an open type plan for the developers. We liked being able to bounce ideas off of each other without really getting up and the overall communication improvement with in the team. It was helped others followed simple etiquette rules. The big rule being if someone has head phones on don't bother them unless it really is important.

      What we hated was everyone walking through our space to get some where else. No one could understand this isn't a walk way. It's where we work. It's like a giant office just for us. We eventually put filing cabinets up and blocked our "open area" off so it was still open in the sense we could talk to each other, hold meetings and get the things we liked out of the design, but reduce the things we hated.

      --
      "Ubuntu" -- an African word, meaning "Slackware is too hard for me". - stolen from Dan C alt.os.linux.slackware
    19. Re:10x Engineer by JustNiz · · Score: 3, Insightful

      So true.
      The company I work for recently moved office but they gave us engineers the opportunity to see some sites they were considering.

      The managers were amazed when we said we preferred the crappy old site with separate ofiices rather than the shiny executive newbuild with a big open space.

      Then It dawned on me the reason why they couldn't understand.

      Managers spend all day doing nothing actually productive, just justifying their existence to each other verbally, so they automatically believe that any environment that promotes communication must be the best.

      They are not mentally equipped to understand that anyone's productivity can be anything other than proportional to the level of communication going on around them, whereas in fact, for developers it tends to be inversely proportional.

    20. Re:10x Engineer by 0xdeadbeef · · Score: 1

      A competent C/C++/Java programmer will produce more on the order of 1000 lines of debugged code per day

      Paging Dunning-Kruger, Dunning-Kruger, please pick up the white courtesy phone.

    21. Re:10x Engineer by hibiki_r · · Score: 1

      I have seen the negative value developer in the past: Someone who created more bugs than he fixed, and when given new functionality, it'd be harder to figure out how exactly it was going to fail on you and fix it than to just throw it all away and write it all from scratch.

      Now, what people don't realize is that the real reason only 10 lines remain even for average programmers is that the hard part of most business software is requirements. It is not hard to generate requirements: The difficult part is to make sure the requirements really fit the need, and are understood by the developers. I have spent a lot of time over my career ripping apart code that made assumptions that were not true even before the program was launched, or tied together concepts that should have never been combined. I have seen the core of an inventory system rewritten 6 times before it was ever used.

      The best programmer is not one that can write the most code in a day, but the one that knows the right questions to ask when handed a problem, makes high quality assumptions, and writes code that is readable and ready for change.

    22. Re:10x Engineer by dubbreak · · Score: 1

      Previously we had offices similar to Joel on Software's ideal office. Everyone had a private office with a door, but they were in a circle around an open area with a test bench. If you wanted to hear what was going on simply leave your door open, if you needed privacy just close your door.

      Once we went "open plan" we had the same issue: headphones weren't obvious to people outside of the team. I wore giant DJ headphones and they weren't obvious enough for anyone outside of the team, "You busy?"

      --
      "If you are going through hell, keep going." - Winston Churchill
    23. Re:10x Engineer by dubbreak · · Score: 1
      Well put. To me the most important thing is code that other people can follow. If your code isn't maintainable it is useless in the long term (and I know people that have been fired for that when they wouldn't clean up their act).

      As for immediate things that makes someone "good" during the hiring stage I'd say:
      • Good communication skills (dealing with the team or as a freelancer dealing with your clients
      • excellent problem solver
      • good work ethic
      • no ego

      Realistically, you can pick up nearly any skills you need as you go (if you are smart and dedicated). A compsci degree should give you all the foundation you need so that you can learn everything else as you go. Soft skills such as interpersonal skills are really important and still underrated. I think it's the soft skills that separate the great devs from merely good ones. Attempt to be a social geek not an anti-social one. Shoot shit with the sales guys and service staff (when on coffee or whatever) and see what you can learn from their angle. Yeah, many sales guys are knuckle draggers, but it's amazing what a simplified view of the world can bring out. We spend so much time focused on details it's good to get someone else's simplified outside view.

      I've found being well rounded to be helpful. Some would worry about being a "jack of all trades, master of none" but I've found breadth to be extremely useful. Sure you can specialize in some certain domain and some pay damn well but if that well dries up and you haven't kept up on what's going on it can be a rude awakening. Push yourself outside of your comfort zone as often as possible then you'll become more an more efficient at tasks in general (rather than good at a specific problem).

      --
      "If you are going through hell, keep going." - Winston Churchill
    24. Re:10x Engineer by Lando · · Score: 1

      Industry standard is still 20 lines of "bug free", "documented" code a day as far as I know. It's so hard to find decent coders that will work for what drones get.

      --
      /* TODO: Spawn child process, interest child in technology, have child write a new sig */
    25. Re:10x Engineer by Anonymous Coward · · Score: 0

      I've been programming in C for 15 years... I can do 1500-2000 lines in a day.. but not every f'ing day. 2 days in a row max... and you have to spend ALL day on it.. not 8 hours. The entire day. AND it depends on how big the project is. If I wrote 1500 lines in a day, I can guarantee you I just started writing a program from scratch. If it's millions of lines long, like Windows: you realize a programmer at MS writes around 1000 lines A YEAR.. that's 4 lines a day.

    26. Re:10x Engineer by benjamindees · · Score: 2

      Exactly. And they measure your value that way as well. If you sit in the corner of the office with your office door closed, you're probably goofing off. If you work from home, you're completely worthless.

      --
      "I assumed blithely that there were no elves out there in the darkness"
    27. Re:10x Engineer by Kjella · · Score: 1

      To be fair I think figures like 10 lines/day usually mean that at the end of the entire process 10 lines that survived and are documented and survive testing account for a day of time. But still you really have to wonder about the people at the low end who managed to get the average down to 10 lines a day... were they producing code that was simply discarded wholesale? Were they producing negative lines of code, i.e., somehow intentionally or unintentionally sabotaging the efforts of others?

      One of the reasons LoCs is a mindbogglingly stupid metric is that a good coder will add more lines and remove more lines. You add more function points and remove code that is copy-pasta, doesn't use the library functions available or is just 10x as long as it needs to be. You can have added 100 lines of functionality, removed 90 lines of crud and still end up with the same LoC as the guy who just added 10 lines of crud. The reason they're down to 10 LoCs is because their patches get rejected, rejected and then rejected some more in review...

      --
      Live today, because you never know what tomorrow brings
    28. Re:10x Engineer by Anonymous Coward · · Score: 0

      Any project over 100kloc that I've seen has been a bloated pile of crap. A 1000kloc project could as well be a 100kloc project with great design. Surely the million lines are easier and cheaper to get produced. But why should I want to be involved with crap business? I hate crap.

    29. Re:10x Engineer by Anonymous Coward · · Score: 0

      I write 10 lines of perl per day, but they do more than 1000 lines of Java.

    30. Re:10x Engineer by Anonymous Coward · · Score: 0

      It takes time to solve the problem, to design in some speed into the solution multiple people usually need to brainstorm.
      The main time for a developer is not spent coding, its spent thinking, if the coding is in the "way", then the developer is not good enough.
      Coding is something you do as a side task, the real work is to figure out how a hell everything should work.

  11. Boon for Tech Fly By Night Schools by kodiaktau · · Score: 1

    I can see the Fly By Night Degree Programs swooping down on this and getting more stooges to sign up as software programmers.

    You too can make thousands of dollars more per year .

    It is misinformation like this that drives me crazy about this business.

  12. The biggest differential in productuvity ... by YordanGeorgiev · · Score: 1

    Is in the developer's profession ... I know developers which are worth 1000 and more of the cheap minds calling itself developers ... Sad but true.

    1. Re:The biggest differential in productuvity ... by Anonymous Coward · · Score: 0

      The regular good developer is 10 times more productive than average code-monkey. What is shocking is that they don't earn 4 times as much, let alone 10 times...

  13. Scarce? by wilfy · · Score: 1

    > the vast majority of them haven't found a way to use their own scarcity to their advantage Strewth, if I'd know I was that scarce and valuable I would have warned the guys that just 'insourced' our projects. BTW, 'insourcing' means bringing a project it into the company then sending it out to India. It sounds more cozy than 'I am sacking all indigenous programmers and employing truckloads elsewhere because I bought half the software house'. Good luck with that. I am going fishing.

  14. has anyone actually read this article? by doom · · Score: 4, Insightful

    Has anyone actually read this article? The guy is talking out his ass. As far as I can tell he's got nothing behind anything he's saying. In the places I've worked, developers have certainly been valuable-- this is why, after all, we're paid a lot of money to do stuff a lot of us would do anyway-- but the critical assests of the companies have been things like the reputation of a domain name, or the side-agreements with various content providers, and so on. As for a new bubble, yes, as far as I can tell there's a venture capital bubble of sorts in the SF area: VCs are tossing money at 20-somethings that'll work 80 hour weeks under the delusion that they're going to be the next facebook. This makes a degree of sense from the investor point of view, if you consider that there's nothing else going on in the economy remotely worth investing in. This time around, there's this weird phenomena where there are no rental apartments available at any price in SF, but there's plenty of vacant office space: the kids are working on laptops in their living rooms and out in cafes, not in actual offices-- they're also completely trashing their backs and hands in the process. If you really want to invest in a growth industry, think about "physical therapy".

    1. Re:has anyone actually read this article? by Maximum+Prophet · · Score: 1

      they're also completely trashing their backs and hands in the process. If you really want to invest in a growth industry, think about "physical therapy".

      Or adjustable standing desks. Supposed to be great for your back.

      --
      All ideas^H^H^H^H^Hprocesses in this post are Patent Pending. (as well as the process of patenting all postings)
    2. Re:has anyone actually read this article? by Anonymous Coward · · Score: 0

      Has anyone actually read this article? The guy is talking out his ass. As far as I can tell he's got nothing behind anything he's saying.

      It's Forbes and it's about technology, so that sounds about right.

    3. Re:has anyone actually read this article? by Anonymous Coward · · Score: 1

      Rest assured this a 'seed article' that is designed to give the impression that developers being scarce is a foregone conclusion. This will be followed by "we need more 3 times more visas" articles in 1-2 weeks - visas to be handed out to people where Venkatesh Rao is from of course.

      Every time I have read a "developers are scarce, technology in dire straits" article in the last ten years, I have read about some new visa legislation bill or some such within the following 2 weeks - I've come to suspect the timing is not a coincidence.

    4. Re:has anyone actually read this article? by Arran4 · · Score: 1

      In places that I have worked so far. They have not.

    5. Re:has anyone actually read this article? by DoctorBit · · Score: 1

      This time around, there's this weird phenomena where there are no rental apartments available at any price in SF

      Huh? I just checked Craigslist today and there are literally THOUSANDS of apartments advertised in the SF city (yes really, I counted over ten pages of listings at a hundred listings per page for Tuesday alone) and THOUSANDS more in the south bay. What are you talking about? See for yourself:

      http://sfbay.craigslist.org/apa/

      I lived in downtown SF during the last bubble and there really was a shortage of housing then, only a few apartments advertised each day for all of Santa Clara county and maybe a dozen each day in SF. Calling the phone numbers in the ads back then would just get busy signals or no answer. The shortage made huge front-page headlines in the San Jose Mercury.

    6. Re:has anyone actually read this article? by w3woody · · Score: 1

      They guy may be wrong, but he's probably less wrong than the pointy haired boss in the corner office at some random large non-tech corporation.

      And that's the key: the MBAs are groping in the dark barely able to find their own ass. One happened to grope his way slightly closer to the light. Give him kudos for that.

    7. Re:has anyone actually read this article? by doom · · Score: 1

      If you search on "San Francisco" it includes a lot of stuff that isn't, like Oakland and Daly City. If you punch the "San Francisco" tab, that restricts it further. As of today (Dec16) there have been 200 posts-- much older than that, and they're bound to be stale-- not "thousands". I grant that I was exaggerating when I said "none at any price"... there are some if you're willing to pay through the nose for a tiny place.

      When I was looking (last October) conditions may well have been worse, but then, I personally have to screen out a lot of things like the Sunset and Richmond districts which are too far from the railway stations to be practical for the Silicon Valley commutes I always seem to end up doing.

  15. Oh but management can fix that by SmallFurryCreature · · Score: 1

    Status reports! MORE status reports! Scrum stand up, daily reports, weekly reports, time sheet, burndown chart. It is easy to! Today: 8 hours - Updating status reports. Rince and repeat.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

  16. Ballmer was right? by Anonymous Coward · · Score: 0

    You mean Ballmer was right when he got stuck in a loop, repeating "Developers, Developers, Developers, Developers, Developers..."???

  17. Coder is a way of life, not a job by TiggertheMad · · Score: 3, Insightful

    Seems to me that there is miles of difference between a born Engineer (a smart, logical thinker who loves tinkering and solving problems), and a sold Engineer (someone who has no inclination or desire towards engineering, but simply wants to make as much money as possible).

    So very true. As someone who did a fair amount of freelance developing over the last decade, the number of people who are using compilers because they think it will get them rich is truly scary. Non-comp sci types are *probably* safe to let loose on basic web development tasks, and that is about it. If the number of developers that I have meet that are the really talented types who really 'get' coding are representative of the industry as a whole, I fear for our future.

    --

    HA! I just wasted some of your bandwidth with a frivolous sig!
  18. Can't get there from there by SuperKendall · · Score: 1

    The right answer to your thought experiment problem is to find/make an accountant who knows enough about software to write useful specifications, then put them to work on testing the results too. That's cheaper than trying to turn a good developer into a entry-level accountant, which isn't very likely to go well anyway.

    I'm not quite sure I see where that argument is going, because the account who can spec and test is still not going to be able to actually build the software - but to build the software well you really should have a developer who can learn enough to understand why and how a system will be used.

    So basically you are better off (as in: it's no more expensive) to find a good developer with an interest in or willingness to learn Accounting. Though the spec accountant can still be of use...

    Also, I don't think accounting and programming are as disparate fields as you might think...

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
    1. Re:Can't get there from there by tehcyder · · Score: 1

      Also, I don't think accounting and programming are as disparate fields as you might think...

      On slashdot, programmers are rock stars. Accountants, CEOs, lawyers, doctors, bankers, architects or whatever are just mug punters.

      --
      To have a right to do a thing is not at all the same as to be right in doing it
  19. Writing under the influence by russotto · · Score: 1

    Mr. Rao: Please write articles while drunk more often. They are quite amusing.

  20. I've worked with a lot of coders in my time... by clockwise_music · · Score: 1

    Hardly any of them are in it just for the money. The ones that are just drop out during uni when they realise that you need a brain. I've only met one or two coders who really salivate over the money. Most just want an interesting job to work on and good people to work with.

    Maybe Australia is different, but 99% of the coders that I've worked with would never drop the ball in order to just make more money (I can only think of one guy and he was a genuine psychopath). All of the good ones stick around and get the damn thing delivered, normally even when that means late nights and horrible bosses. We have professional pride and always strive to deliver the best possible system given the constraints. If you don't, then word gets around pretty quickly and you'll find it very difficult to get more work. You can always spot these people, they have lots of 3-6 month projects on their resume, and when you drill them for details it's always a bit too vague.

  21. face it... by hitmark · · Score: 1

    the knowledge economy do not work, as the ease of knowledge distribution works against it. End result is a continual stack of draconian laws to try and counteract that, eroding all respect for law in he process.

    --
    comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
  22. very good by berniemne · · Score: 1

    Srsly very good article. I'm always thinking about moving to USA becuase of these guys. Srsly the rest of the world lives in the stone age. Literaly. (Why the fuck I fuck around in EU, fuck knows....)

  23. The mobile market by tepples · · Score: 1

    We're talking about developers here. People that think you can always throw more RAM or disc space at a problem rather than keep their code neat and clean.

    Those are the managers, not the developers. But the mobile market has helped convince managers that throwing more hardware at a problem isn't always better than throwing more developer time at it. If you want your application to run on a device that the end user already has, it'll have to fit the RAM, storage, and network limits of the device. PDAs, tablets, and smartphones tend to have less of each than laptops, desktops, and servers.

  24. Then why couldn't I go to acting school? by tepples · · Score: 1

    You can practice your fake smiles. It is called acting.

    Then why don't technical colleges have acting as a strongly recommended course?

  25. Jobs for tech-talented people with autism? by tepples · · Score: 1

    People *are* things. A social system can be manipulated to give the most-positive outcome the same way a computer system can.

    That still doesn't help people like me who have a disability that impairs their understanding of social systems. How are people born with mild autism supposed to eat in an economy that strongly rewards a people person?

  26. Get rid of the money as quickly as possible by Anonymous Coward · · Score: 0

    As a coder my strategy has been to get rid of any money that might come my way as quickly as possible. The value of things in my life is much higher than the value of a bank account balance or poorly performing stock in my portfolio. Smart people tell me things will be better next year and we may indeed see a new boom. I mean, like at the hype around Groupon. Pffft, if that doesn't prove that a new tech bubble is likely, nothing does.

  27. Not everyone wants to move to California by Cutting_Crew · · Score: 1

    I have read the article and all the sub articles and one universal truth keeps popping up. That talent is hard to find. While one writer seemed to grasp that not everyone wants to move to Silicon Valley, the problem for rare talent is that realizing that there is a lot of talent around the rest of the country...from people that didn't graduate from MIT, Stanford or UC Berkley...and guess what... just like normal every day americans they have family and friends and while they may be slumped over some desk doing mediocre mundane software development, the family and friends thing is more important than doing something that would love to do but have other considerations to make..personal considerations.

    At some point I have brought up this point before in a previous story but it would be oh so nice if places like google would locate shops in different parts of the country. I am not talking about huge datacenters that only employ 50 people or call centers to try to solve peoples problems. I am talking about software hubs. They dont have to be as glamorous as the mothership office and they dont have to support 3000 jobs...but there is lots of talent, particular in the southeast where i am , where people are hungering for work that they love to do in their own time. The bonus is, is that because most of the country costs about 300% less than san fran to live in places like Tennessee, Mississippi and Florida for example, the salaries don't have to be as big and you still get the same type of work - if you find the good talent , and there is some.

    just thoughts and ramblings.

  28. Wage stickiness and the failure to price talent. by w3woody · · Score: 1

    The real problem, one that the Fortune article almost correctly alluded to, is that in the Software Industry, wage stickiness (http://en.wikipedia.org/wiki/Sticky_(economics)) is extremely high. Corporations are willing to cost themselves tens or even hundreds of thousands of dollars worth of intangible damage in order to save a few thousand dollars on floor space because they either believe the slowdown in the general economy is also reflected in the Developer market, or because they don't understand the vast incremental value a talented developer brings.

    Wage stickiness occurs because of imperfect information and from fairness concerns; it just doesn't seem fair to pay a senior developer doing 20 times more work what he's worth because then a company would have to figure out he's doing 20x more work and pay him a seven-figure salary. With imperfect information managers look to balance sheets, and because they can't effectively control their work force (because they don't understand them), they don't realize that one key person's departure caused the entire project to collapse or be delayed months, costing hundreds of thousands or millions of dollars.

    The one thing I got from the Fortune article is that people are starting in the business community to wrap their heads (imperfectly, of course) around the problem. One thing I think we'll see in the next 10 years as software eats the world is a loosening of wage stickiness. And you will start seeing the top 1% of programmers making salaries that start to compare to the CEO in the corner office when enough information percolates to management that those top 1% programmers are bringing more value to the company than the CEO.