News for hackers. Stuff that matters.
Re:Hire talent, not five years with Java by InclinedPlane on Tuesday March 26, 2013 @04:53AM (#5441954)
Part of it is the difference in programming culture. With startup culture, which has many good aspects, also came the idea that the death march should be the norm. Meaning, 20-somethings should be working 80 hour weeks on a regular basis and projects should be shipped at the soonest possible moment it's even remotely feasible to do so.

This sort of working environment has no slack, no capability to operate effectively in apprenticeship mode, and little leeway to allow long ramp up times. And as a result it has become more difficult to positively advance the state of the industry or the average skill toolset of coders.

It's the classic problem, when you spend all your time in emergency mode fighting fires you don't have the cycles to be able to make improvements to systems or to other coders as well.

Re:Hire talent, not five years with Java by alberich on Tuesday March 26, 2013 @10:10AM (#5443357)
Funny that I see companies complaining about the lack of skilled workers here in Brazil, but they are not startups... they just don't want to pay the price.

They want engineers, programers, etc. with huge experience and paying a little. Just yesterday I saw a news article talking about the lack of car mechanics... and they say (like it is a great thing) that salaries go high as $450 bucks a month (40h per week)... they don't understand why nobody wants to be a mechanic :P

Re:Hire talent, not five years with Java by caw on Tuesday March 26, 2013 @12:06PM (#5444192)
Total compensation or salary? I'm pretty sure mechanics are paid a base + commission of the sale. The less time they spend fixing the car the more commission they can make (as they move on to the next car). It's an incentive to work. If the labor takes more than the estimate, then the shop and the employee are losing money.
Re:Hire talent, not five years with Java by alberich on Tuesday March 26, 2013 @06:01PM (#5446355)
It seems this sum is all they get, as they said most mechanics prefer to work on their own (informally) as they get more money. Besides, comissions don't contribute for their final retirement salary and stuff like that.
Re:Hire talent, not five years with Java by dexen on Tuesday March 26, 2013 @05:35AM (#5442099)
While I agree with your overall message, the

> (...) death march should be the norm. Meaning, 20-somethings should be working 80 hour weeks on a regular basis and projects should be shipped at the soonest possible moment it's even remotely feasible to do so.

has got me puzzled: in my (limited) experience and from what I've read, a death march is exactly the opposite of shipping early. The usual story goes: a deadline looms, or a milestone slips, a middle manager decides to whip up his team instead of reporting it. Overworked team members can't meet another deadline, the client and/or upper management is kept in the dark about the problem, no extension of deadlines for sake of good metrics, rinse and repeat.

``It is done when it is done'' and shipping early is a panacea, not a cause of the problem.

Re:Hire talent, not five years with Java by InclinedPlane on Tuesday March 26, 2013 @02:42PM (#5445226)
Death march is often the norm, and when more effort is needed the only option is a super death march or just giving up.

And yes, it's not a good way to work. Nor is it even a fast way to work. It's a an equilibrium point that is reached when certain initial conditions in regard to the value that is placed on the appearance of work and dedication are higher than craftsmanship et al is valued.

For people who are immersed in that world view it seems perfectly logical that adding more hours worked will make everything better. But the paradox is that it doesn't, it often makes things worse, for a whole laundry list of reasons. People become physically and emotionally exhausted by the pace, there's no room for higher level improvements which are often the only way to achieve orders of magnitude gains in efficiency, productivity, and quality.

There are a handful of companies that do things right and at those companies employees tend to stick around for not just a few years but decades and the products they make tend to have an outsized impact on the industry (valve, blizzard, 37signals, pixar, etc.) But it's still so hard to fight against the conventional wisdom.

Re:Hire talent, not five years with Java by Retric on Tuesday March 26, 2013 @10:39AM (#5443559)
All it takes is unrealistic deadlines and you end up with a death march. Unfortunately, some people game the system and assume burning people out is worth it.
Re:Hire talent, not five years with Java by mapt on Tuesday March 26, 2013 @05:56AM (#5442155)
If there's no slack for training time, there's no slack for an empty position, which is what we have now.
Re:Hire talent, not five years with Java by winestock on Tuesday March 26, 2013 @12:03PM (#5444172)
Very succinct. If a company can afford to let a position go empty for six months because they "need someone who can hit the ground running," then they don't really need someone who can hit the ground running.
Re:Hire talent, not five years with Java by kevincrane on Tuesday March 26, 2013 @12:51PM (#5444505)
Maybe the difference is not needing to pay someone for those six months when he might just be training still?
Re:Hire talent, not five years with Java by michaelochurch on Tuesday March 26, 2013 @08:44AM (#5442829)
Yes, this. In the analysis that I'm building up (start here: http://michaelochurch.wordpress.com/2013/02/19/gervais-princ...) it's the tough culture. It gets people to work hard but not smart. Long-term strategic considerations are ignored, it's all about now, now, now. That mentality can be good for short bursts of superhuman productivity, but after a few months, it taps out.

The apprenticeship makes sense in the lawful-good guild culture; tough culture is chaotic evil. (Typical corporate rank cultures, where subordination is key but you can get away with pretty much anything-- even doing nothing for years-- so long as your boss likes you, are lawful evil; Valve's bossless, self-executive mode is chaotic good.) So the tough culture of startups is the exact opposite of the progressive (but usually incapable of immediate scaling) guild culture.

Re:Hire talent, not five years with Java by 127001brewer on Tuesday March 26, 2013 @10:26AM (#5443468)
...it's all about now, now, now.

I think this mentality affects all aspects of our lives and society. How do you disrupt this shortsightedness?

Re:Hire talent, not five years with Java by nollidge on Tuesday March 26, 2013 @11:16AM (#5443827)
Eh, let's figure it out later.
Re:Hire talent, not five years with Java by 127001brewer on Tuesday March 26, 2013 @11:35AM (#5443973)
I totally forgot what we're talking about anyway.
Re:Hire talent, not five years with Java by michaelochurch on Tuesday March 26, 2013 @01:10PM (#5444654)
Typical corporate rank cultures are short-sighted because they've lost vision and short-term P&L is the only thing that matters. Risk-reductive management means that no one gets to do anything long-term because no one is trusted to bet that much time on anything.

VC-istan is based on a get-big-or-die mentality. These companies end up with tight deadlines because they're forced to hire so fast. That makes them panicky and stupid when it comes to operational concerns... and it's bad for culture, but no one cares about "culture" in something that exists to be bought by Yahoo in 3 years.

The future isn't going to be built by VC-istan, but by a fleet of ~50,000 small-to-medium businesses formerly called "lifestyle" companies, and the whole ecosystem that grows up to support these "yeoman capitalists". It's going to be built by people that, right now, no one will fund.

The problem is that no one will fund these companies now. Bank loans are good for dry cleaners and restaurants that are unlikely to go to total failure. (Half will be closed in 5 years, but most because their owner-managers could do better elsewhere-- opportunity cost.) VC works for a 5% shot at being a billion-dollar concern. Who funds the 30% chance at becoming a 20-person lifestyle company that, while it never makes a billion, pushes technology forward in a major way? No one, yet. There are "moral hazard"/principal-agent problems to be solved, but they aren't that hard.

I'm actually addressing that in my 17th part of the Gervais / MacLeod series. I'm between jobs (I have offers, but I'm not working right now) and I've had time to really attack this problem. It'll probably be out around 3:00 today.

Re:Hire talent, not five years with Java by bokonist on Tuesday March 26, 2013 @08:56PM (#5447081)
The future isn't going to be built by VC-istan, but by a fleet of ~50,000 small-to-medium businesses formerly called "lifestyle" companies,

The problem is that many technology companies have natural economies of scale. It is not realistic to have a world where you have 1,000 mom and pop search engines instead of 1 Google. One search engine becomes a little better, so more people start to use it, it can make more money, invest in more technology, become even better, get even more users, and eventually the top dog becomes a run away success. Since the entire idea of technology is that you research the novel technique once, and then can use the technology over an entire user base at a low marginal cost, there is a natural economy of scale.

There is of course already a very large economy of "lifestyle" businesses. But these businesses are either b) not in the technology business (restaurants, retail, services, etc.) or b) in an extreme niche of technology where there are so few customers the company never grows that big.

I really do not see how you can break a Microsoft or Apple, much less a Google or Facebook, into 50,000 smaller businesses.

Re:Hire talent, not five years with Java by michaelochurch on Tuesday March 26, 2013 @10:38PM (#5447455)
Google was still an excellent search engine when it had 1/100 of its current codebase. Fifty programmers could deliver something of nearly comparable quality (excluding in-house knowledge that gives it that extra 0.01%). Google's obviously doing a lot more than Web Search, now.

Web Search is a Big Problem and, as you said, it's a winner-take-all, red-ocean business. Google managed to come in when the state of the art was horrendous (few considered search to be an interesting problem; it was "solved" but shitty). Now Bing is almost as good as Google, and certainly far better than Google was when it established dominance of Search.

You say: I really do not see how you can break a Microsoft or Apple, much less a Google or Facebook, into 50,000 smaller businesses.

You don't. Big companies are not going to die out overnight. They'll still be there, they'll still be strong and important, they'll still provide utility and commodity services, but the Big Companies of the mid-21st century might have 3000 employees instead of 25,000. So where will those other 22,000 go? Smaller companies. They'll be more independent.

There are a lot of problems that can be solved by technology but require some "niche" competence. Take the emerging field of data science. Machine learning is very powerful, but domain knowledge is still key. There are thousands of domains that are going to be needing what's currently a very high level of data competence (not big data, but smart data for sure) in people who also understand their problems. That makes room for thousands of lifestyle businesses.

Re:Hire talent, not five years with Java by bokonist on Tuesday March 26, 2013 @11:48PM (#5447692)
There are a lot of problems that can be solved by technology but require some "niche" competence. Take the emerging field of data science.

It's possible that market dynamics will change in a way that favors small businesses over large corporations. Is it likely? You have not convinced me.

Google needs thousands employees in order to run the infrastructure that maintains its current scale, and in order to develop the features needed to keep its competitive edge. Fifty employees is not going to cut it.

It is conceivable that it could be run with, say, 5000 employees instead of 50000. It is possible that the additional 45,000 employees are basically unprofitable, executing vanity projects to give shareholders the impression that Google is innovating in new directions. If that is the case, as programmers we should probably be thankful, because that money is going to bid up our salaries, rather than being paid back as dividends to wealthy shareholders.

In other words - even if businesses could be run much more efficiently - the beneficiaries would be the shareholders, not engineers. Only if the shareholders used their extra dividends to buy more software would it balance out to engineers. If Google suddenly became far more efficient, fired 90% of its workforce, and paid dividends to shareholders, that would not magically create a market opportunity for 1,000 new small businesses to pop up. The new jobs would be in whatever the shareholders getting the dividends choose to spend their money on.

Re:Hire talent, not five years with Java by 127001brewer on Tuesday March 26, 2013 @01:56PM (#5444955)
...because no one is trusted to bet that much time on anything.

Right and, maybe, this partly why a growing number of people do not stay at a company for too long. (I think you mentioned this idea (that, basically, human labor is an easily trade-able commodity) in one of your Gervais / MacLeod posts.)

Re:Hire talent, not five years with Java by lani on Tuesday March 26, 2013 @12:17PM (#5444270)
>> . The positive-sum “win-win” outcomes that Technocrats seek exist, and they’re all over the place, but they never come without risk. Once the company decides that creative risks are intolerable, what’s left is zero-sum social-status-driven squabbling.

This line really hepls me crack the code for me