Hacker Newsnew | past | comments | ask | show | jobs | submit | begurken's commentslogin

Also, do not be deceived by "data science": it's mostly a bullshit term, and translates roughly to "programmer who knows basic statistics"

This is utter rubbish; I really wish people would keep quiet about things they know nothing about. I suggest that you have never actually discussed a domain with a data scientist if you think it's "basic statistics".

In our dev. shop, we have a lot of great programmers, but none of them can touch our data scientist when it comes to working out what our tens of millions of users are actually doing and what their salient attributes are.

As for the data scientist needing to 'implement their theories', that's what the developers are for. The data scientist does the analysis, then works with the developers to implement systems that incorporate the results. Neither group is capable of the other's work.


"I suggest that you have never actually discussed a domain with a data scientist if you think it's 'basic statistics'."

Utter rubbish, perhaps. But since I've actually done the job, I do happen to know something about the subject. It's a marketing term, not a term of art.

The vast majority of "data science" performed at web companies boils down to knowledge of summary statistics and probability theory, a smattering of basic statistical models, and (most importantly) the ability to write code. There's not much that would challenge an advanced undergraduate, let alone a doctoral-level statistician.


This message is very well known and understood.

The interesting question is 'why do foolish managers continue to treat their employers in poor ways that are known to decrease productivity?' In terms of productivity, it's a total lose-lose situation.

I'm 37, and I'm pretty sure that I have worked out the answer. Most corporations are run by people (the managerial class) who are more interested in power than results. They hire sycophants who kiss upwards and amplify pressure downwards. Competence is irrelevant; after all, any competent manager would resist managing their employees in ways that management science have proven to be unproductive.

I have been in a couple of these companies, and they absolutely rot from the head down.

At least in tech. we have the option of getting out, because such companies are generally not entrenched and are on track to fail. Unfortunately, in other parts of the economy, such companies are unassailably entrenched, so their workers have no choice but to work for stupid, evil, toxic organisations, or to change career.

The result of these organisations is that much of the US now has a toxic culture of 'if you're not stressed, you're not working'.

A friend also suggested to me that it's possible for groups of people to become 'addicted' to stress; it would be interesting to see more on this.


There's a less cynical answer: it's that managers are subject to the same principle, of insufficient R&R resulting in tunnel vision, and so they're exhausted and hence tend to think short-term (beat this unrealistic deadline now!) instead of long-term (we'll cut the least important features or slip the deadline so we can get it done). The only way to break the cycle is to realize that a good portion of what you do doesn't need to be done, and ruthlessly cull out nonessential tasks so that nobody does them.


> Most corporations are run by people (the managerial class) who are more interested in power than results.

This made me a lot angrier before I realized that this is just the primate dominance dynamic expressed in business organizational structure. It's the default human response to the circumstance, just like street gangs are the default response to different circumstances.

That has changed my attitude to "I hope these assholes get hit by a truck" to one of compassion to people whose wiring has gotten them trapped in a local maximum. There are no villains, only people who the system has trained to serve the system.


It's partly a problem of optimizing metrics that are easy to measure, like ass-in-chair time.


I couldn't agree more. There is absolutely NO way to effectively measure programmer productivity.

If there actually were an objetive way, then it would be a different story. But in the absence of it, a team has to "look" productive at least, and that means people in the office looking like they're working. Even if it means less real work getting done (because again, how do you measure that objetively? can't be done).


> There is absolutely NO way to effectively measure programmer productivity.

One of the big reasons programmer productivity is so difficult to measure, is that you need to also see future productivity of everyone else who works on the code. If a programmer takes an extra week to build something more maintainable and that improved design saves months of future work, it's likely a productive use of time, but that's not always obvious until those months are saved (or not saved). That's not easily measured until the full lifecycle of the software is complete.


Measuring programmer productivity, as in long-term impact, is much harder than measuring how many hours Programmer X sits at their desk or how many lines of code they can spit out in a day. Those are metrics that other programmers notice after maintaining code that previous programmers leave behind. It's always going to be a delayed reaction.


i agree that working with breaks and socializing with colleagues for a coffee/a walk/ a fresh breath of air is good for productivity. however i do not agree with some posters who say that there are no metrics to measure productivity. there are ways to measure programmer productivity. not talking about lines added or features added. in general we can get a sense of how involved is a feature addition by looking at the list of data structures needed, algorithms to process the data, algorithms to list/display the output. more formal methods--http://secse08.cs.ua.edu/Papers/Danis.pdf


That approach can set a sort of lower bound on how much work a feature requires, but judging productivity also involves measuring how often the program fails to meet its specification and how much work to modify it could have been avoided up front.


Addiction to stress is kind of a real thing. It takes a complete stripping away of the mentality that most people have to see it for what it is. The managerial class is also put through the paces in Corporate America. I've seen this first hand. Unless you are a C-level executive, there is always someone using the veiled threat of job loss to keep you in line.

The tech world has some problems, but compared to the work environments that the rest of the country is experiencing, it's Shangri-La.

I wish that all of the country (world, really) would be able to exercise control over their destinies as easily as we can. The mindset and the skills together are a great gift. Never cease to be grateful.


> A friend also suggested to me that it's possible for groups of people to become 'addicted' to stress; it would be interesting to see more on this.

This NY Times article was posted here a few months back and touches on the same idea: http://opinionator.blogs.nytimes.com/2012/06/30/the-busy-tra...


Let Oracle bundle their bloated adware. Don't provide them a free service by telling them how stupid and self-destructive this practice is; if they're too dumb to work out that it isn't in their long-term interests, they deserve the consequences.

Publicly traded corporations are all the same; they're all equally obnoxious, a-moral, and hostile to customers when it suits their perceived interests. Oracle's Java adware is just a tiny little symptom of this; the actual problem is systemic to public corporations.

This kind of obnoxious user-hostility is what made me abandon closed source software for personal use. Additionally, my company (a private company) doesn't use any closed-source software in our systems, and never will. For us, open source software is better, more flexible, more supportable, and the nail in the coffin is that there simply aren't any vendors that can be trusted by a small organisation such as us.

Oracle don't care about little people signing a petition anyway. If one of their large corporate customers told them directly that this was unacceptable, they would stop it in a minute.


The point is Java is open source...


No, OpenJDK is open source.


But OH NOES, they are teh socialist!!11oneeleventy And we all know that socialism always fails because socialist governments go bankrupt; at least, that's what rags like the Economist have been telling me for the last 30 years.

<sarc>This is why free-market, no-social-services USA has such a low public debt/GDP ratio, whereas quasi-socialist (public health: boo!) Australia has high debt/GDP, and socialist hell-holes like Denmark have off-the-scale debt/GDP ratios.</sarc>

Just look at the numbers in my (highly debatable and somewhat cherry picked) loosely ranked list of least to most socialist countries.

Debt to GDP ratios (2010) USA: 73% UK: 86.8% Australia: 30% Canada: 83% Germany: 82% Japan: 208% Finland: 49% Sweden: 38% Denmark: 46% Norway: 49% Singapore: 118.2% France: 86%

DERP. Oh dear, the numbers appear to have little correlation with with how socialist the country is, but may be more related to how 'innovative' a country's banking sector is, how many 'state owned enterprises' there are, national demographics, corporate political capture, and how distorting the tax system is.

Even the neo-liberals at the Economist are starting to understand that government provided social services, transport, health, and education aren't the primary factor that sends countries broke. Perhaps one day they'll notice the elephant in the room: the banking sector.


2010 figures are a bit out of date given the deficits the US has been running (the US has risen over 100%). I think the Economist actually has noticed the banking sector (consider this invited column from 2010:http://www.economist.com/economics/by-invitation/guest-contr...). By and large, the shift in US politics to the right has the Economist looking like a left-of-Democrat newspaper these days. The idea that Obama is a "socialist" is, to anyone versed in a tiny bit of history or political science, laughable.


Indeed; thanks for the update on the US.

I believe The Economist paid lip service to the role of the financial sector in the collapse; but that's mostly my opinion; as you say, they definitely covered it to some degree. At least they're apparently starting to realise that chanting "cut public services" over and over isn't the answer.

One problem with the USA left-right false dichotomy is that when you pick a middle point between the Republicans and the Democrats, you end up with something that resembles no political party anywhere else (including in the USA's history); everyone else's right wing parties (and the Republicans in the past) resemble the Democrats or are even further 'left'.

As far as I can tell, there's almost no difference between Obama and (for example) Reagan based on the left/right scale; yet US conservatives generally idolise Reagan and demonise Obama. It's bizarre.


You didn't read the article, did you.


I read the entire article; your comment is pointless and unconstructive.

My comment wasn't especially well-worded or clear, but loaded with a fair amount of sarcasm which some people have trouble with, so let me try again.

The Economist is a Neo-Liberal rag. 6 years ago, they would NEVER have published an article like this. Now they're starting to consider actual evidence and are seeing that government social services don't necessarily send countries broke.

However, they still have a long way to go before their analysis actually mean anything. Because they're still strongly attached to their broken neo-liberal world-view.


Ah, it was a meta-comment on The Economist's position.

If you had been straight-forward up front, that would have been much more interesting. Your initial comment was a mess. Not because I "have trouble with sarcasm", but because it had little direction and (to phrase it in terms you should understand) was so drenched in sarcasm as to have practically washed away the original message.


Guilty as charged on that one! I'm incoherent this morning, and feeling a bit off colour. Thanks for being classy and constructive (no sarc).

Here's a fun experiment. Go to the article, and search for the terms 'bank' and 'monetary'. 'bank' appears once within 'bankrupt', and 'monetary' doesn't exist at all.

Any article on this subject is meaningless without including those. The Economist is like an alcoholic who has recently started to admit that their behaviour is sometimes harmful, but hasn't yet come out and said "I'm an alcoholic".


Any article on this subject is meaningless without including those.

Eh, it's fine in my book. Banks may be the biggest issue, but so long as we're getting somewhere I'm happy with The Economist focusing on different aspects. Getting tunnel vision and saying "we must focus only on banks!" would ultimately be a loss, IMO.


Sweden was at 70% and went to 30% (now, 38% was in 2010 as you pointed out) because they cut governement spendings from 67% of the GDP to 49%.

Then you conveniently left Greece out of your list. You know that it did partially default and that it's going to default again right?

And Spain, why did you left Spain out? You know what's going in Spain right now? 50% unemployment amongst young people. Crazy high state budget deficit.

France is in deep shit right now and that 86% from 2010 was heaven compared to today. New car sales dropped year-to-year by 33% or so, companies of all sizes are closing left and right and they're heading for a default is they keep on that nanny state "here are more gifts for you so your sense of entitlement gets higher and you keep voting for us socialists". Because you know what? When a liberal president (Sarkozy) was cutting 180 000 public servant jobs at the very same time collectivities (run by the socialists) did create 500 000 jobs. 500 000 public servants jobs created by the socialists which now, of course, are explaining that Sarkozy did a bad job (he was president right in the middle of the financial crisis and it's all Sarkozy's fault).

The banking sector ain't the issue: we're first and foremost living, after the sub-prime crisis, a state debt crisis.

Why do we need to bail out banks? Because they have bad credits. Do you know the kind of bad credits they have now? State credits which states are never going to pay back.

And why do we have states that are going to be unable, just like Greece, to pay back their debt? Because they've been running budget deficits for years and years and years.

Honestly we're witnessing the failure of governments spending more than they rake in and socialo-communists are able to turn this around and to try to make us believe that it's the evil capitalists from finance who are responsible for all the world's problems.

I'm not buying it.

I confidently say that a nanny state with public spendings at 67% of the GDP like Sweden was before is too much. At 56% like France is right now (but it's going to skyrocket seen that they're not reducing public spending while their GDP is going to take a hit this year and lots of people from the private sector are now unemployed) it's too much too.

There has to be a certain % which is "right" and there may be some room but it's certain that socialists in France asking for more socialism are out of their minds.

The problem when you're "on the edge" with a % of public spendings so high that it's basically ruining the private sector and hence killing any innovation and with state debt around 100% is that you have not much room for maneuver anymore. All it takes is a little match and your beloved nanny state takes fire. Just like Greece. Just like Spain right now. Just like France tomorrow if they do nothing.

It's ugly and it's the fault of government running budgets on deficits.


While you may not agree with static_typed (his name suggests he's probably not a huge Ruby fan), the Rails community (& to some degree the Ruby community) should listen to folks like him. This is because more and more people would agree with static_type's statements.

The high chance that more catastrophic rails exploits will be found in the next month (if all of the paths to YAML.load have been found, I'll eat my hat) will increase the number of people making or agreeing with statements like static_typed's. After an exploit or two have been found in February or March, people will be pointing at Rails and saying 'I told you so'.


There's an implicit assumption here that consistent behaviour within a corporation matters. I think this is wrong. Corporations' interests are served perfectly well by them behaving inconsistently whenever it suits their interests. There may well be executives in Fox who know about the inconsistencies here who simply don't care, because it doesn't affect the bottom line.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: