The Rise of Developeronomics 253
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.'"
Great a new boom. (Score:5, Insightful)
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
Re: (Score:2)
So cash out before the crash. Barring that, be part of the upper half.
Re: (Score:2)
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.
Re:Great a new boom. (Score:5, Insightful)
Overheated market?
What overheated market?
When I see stupidity like this:
Or this ...
He's never read the posters on the minimsft blog [blogspot.com], all swearing that after being "managed out", they will never, ever recommend Microsoft products.
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:
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!
Re:Great a new boom. (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.
Re: (Score:3)
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.
Re: (Score:3)
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 :)
Re:Great a new boom. (Score:4, Insightful)
Re: (Score:2)
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.
Re:Great a new boom. (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.
Re:Great a new boom. (Score:5, 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.
Re: (Score:2)
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.
Re: (Score:3)
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 d
Re:Great a new boom. (Score:4, 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.
Re: (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.
Re: (Score:2)
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.
Coder is a way of life, not a job (Score:4, Insightful)
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.
Re: (Score:3)
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.
Re:Great a new boom. (Score:5, 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.
Re: (Score:2)
Better yet, an investment account, and look at it (to rebalance the portfolio) occasionally.
Re:Great a new boom. (Score:4, Informative)
Honestly, over the last 10 years my checking account has out performed my investment accounts.
Re: (Score:2)
Re: (Score:3)
Re: (Score:2)
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.
Re: (Score:3)
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.
Re: (Score:2)
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.
Re: (Score:3)
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.
Re: (Score:2)
Re:Great a new boom. (Score:5, Informative)
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.
Re:Great a new boom. (Score:5, 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.
Re: (Score:2)
Re: (Score:2)
Re: (Score:3, 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.
Re: (Score:2)
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.
Re: (Score:3)
Re:Great a new boom. (Score:5, 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.
Re: (Score:3)
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?"
Re: (Score:2)
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
Re: (Score:2)
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.
Unionize (Score:2, Insightful)
"...the vast majority of them haven't found a way to use their own scarcity to their advantage."
The way: Unions.
Re:Unionize (Score:4, Interesting)
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.
Re: (Score:2)
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).
Re: (Score:2)
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).
Re: (Score:2)
Nope, the two sentences I specifically mentioned do not do that at all, in or out of context with the rest of the post.
Re: (Score:3)
Re: (Score:2)
That sounds wonderful, but is it actually legal in the modern world?
Re:Unionize (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.
Re:Unionize (Score:4, Insightful)
Re:Unionize (Score:4, 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.
Re: (Score:3)
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 t
Re: (Score:2)
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 i
Re:Unionize (Score:4, 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.
Re: (Score:3)
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 glo
Re: (Score:2)
Re: (Score:2)
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 employ
Re:Unionize (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.
Re: (Score:2)
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.
Re: (Score:2)
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 work
Re: (Score:2)
"...the vast majority of them haven't found a way to use their own scarcity to their advantage."
The way: Unions.
Face palm
Re: (Score:2)
Add to that the fact that organizing developers into a cohesive group is akin to herding cats and you start to see how hard u
Idiots (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.
Re:Idiots (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.
Re: (Score:3)
Don't be silly; nobody bought an iPaq.
George Bush bought an iRaq, though.
<rimshot>
Re: (Score:2)
Re: (Score:3)
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.
Re: (Score:2)
...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.
Re:Idiots (Score:4, Insightful)
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.
Re: (Score:2)
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.
Re: (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. 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
Re: (Score:2)
None.
None.
You ask very poor rhetorical questions.
Re: (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. 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...
Wisdom (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.
Re:Wisdom (Score:4, Insightful)
Re:Wisdom (Score:4, 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.
Re: (Score:3, Interesting)
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
Re: (Score:3)
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.
Re:Wisdom (Score:5, Insightful)
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.
Re: (Score:2)
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 c
Re:Wisdom (Score:5, 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.
Re: (Score:2)
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.
Career length (Score:4, 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!
We are a waste (Score:2)
10x Engineer (Score:4, Insightful)
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.
Comment removed (Score:4, Insightful)
Re:10x Engineer (Score:4, 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.
Re: (Score:3)
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.
Re: (Score:3)
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)
Re:10x Engineer (Score:5, 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.
Re: (Score:2)
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 gi
Re:10x Engineer (Score:5, Informative)
Re: (Score:2)
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!
Re: (Score:2)
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.
Re:10x Engineer (Score:5, 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?
Oh but management can fix that (Score:2)
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.
Boon for Tech Fly By Night Schools (Score:2)
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.
has anyone actually read this article? (Score:5, Insightful)
Re: (Score:2)
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.
Re: (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.
Re: (Score:2)
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.
Re: (Score:2)
Apparently not. [blogspot.com]