467 karma · joined June 23, 2008
This is a common snowclone (X is <far superior in some dimension - often intelligence> than you or I) that really bothers me. It's a kind of hero worship that attributes too much to the hero in question and makes unfounded assertions about "you or I".
I can understand that people become enthuisiastic about their heroes and that exaggeration is even a form of showing respect. But too much is no good for anyone.
I can't imagine that I'd be able to get there until around 22:00. I don't suppose that anyone will still be around then?
Thing is, people in aerospace in the 50's to 70's had a mission and they worked on cool things. If you're working for a typical software company you have neither (unless you consider refactoring that enterprise app as a mission),
High ranking people love this kind of moralism, because it feels like they're really doing something. But the proof is in the pudding and guilt-tripping people about having reasonable working spaces is not going to make people do good work.
This CEO is lazy. Building a good working culture is mundane and takes a long time with constant little tweaks. But nothing beats the rush of thinking you've ruffled some feathers.
It's the equivalent of parents doling out corporal punishment to kids: it really seems to work, but at best does nothing over a long period and at worst creates distrust and fear. Real parenting takes effort, as does real management.
I can understand that some on HN have an Apple preference but Apple almost gets free advertising by the way some talk over here.
Why vote up a comment because someone says they're going Apple?
Python is now my go-to language, especially because of Scipy, NetworkX and bridges like RPy.
I would definitely put in the time if someone with mathematical modelling experience can support the idea that I'll be more productive in Clojure. Anyone?
I really would love to see a list of testimonials and anti-testimonials of people from various fields that switched to Clojure and either got much more done or got burned.
Sorry, I realise that this is a wee bit off the main topic.
Speculating is one thing...
> Also, it's stereotypical that third world folks abuse store return policies and customer support in general.
...but it's inexcusable when it leads to unsubstantiated claims that tar so many people with the same brush.
Also it's a massive stretch to call any but a very small handful of Eastern European countries "3rd world". (I need not defend Eastern Europe, since I'm South African myself, but it's plain as day that a lot of Eastern Europe is not doing too badly).
While I cannot be sure that Jeffrey Zaslow is a Boomer or Gen Xer (the fuzzy dates around those eras makes it difficult to decide), this accusation of entitlement seems to be a Boomer message.
We're talking about a generation that, although its members had much less material amenities than us, they had an easier time getting ahead. Try buying a house as a young person now. When my dad was my age, he could support a family on his salary.
And given that the Boomers (and early Gen Xers) have just wrecked the world economy, I think there's more than a little hypocrisy here.
If the later Gen Xers and Gen Yers have a sense of entitlement, it's because they do as their elders do.
Someone has to try this and if their idea doesn't work, I will bet good money that they'll stumble upon other interesting results (if they keep going).
But until we have more of that, cultural items like Barbie might help to bootstrap the process.
I agree that it's a distant second, but it's better than nothing at all.
I read maxklein's other story (about how programming is procrastination).
I'm going to give him the benefit of doubt now. To be blunt, he needs to work on how he communicates.
But, I think the gist of what he's trying to say is: there are certain things you need to do if you want to succeed well in business. You have to want to do business (the making money part), but that includes things far beyond programming (for example).
I think I see what he means about working with people who want to make money: they have to be in it for the long haul. But even people who would lose interest when they're rich have a long way to go while they're still (relatively speaking) poor.
You don't want to discount the Woz's of the world just because their hearts are in the tech. If you do, you lose.
To me there is a distinction between people who want to make more money and people who want to build things. The former is in it for power, whilst the latter is in it for recognition.
I realize how simplistic that sounds. But many of our current problems came about because people don't care about what's behind the money. We need less indirection in the financial world. If I invest in something, I should give some kind of damn about it.
I also wouldn't be surprised if the members of Group 2+ generally hate the control that the typical manager exerts.
If you want to use language X, then use it - there's no need to justify your choice by slating language Y.
When I countered that you mostly don't even know what you're modelling and that the design state space is much larger in software, he retorted that all sorts of things can go wrong with just a single pipe in a chemical plant but that it doesn't stop reliable plants from being built.
But he didn't get it: that pipe is a component in a well understood framework. It's nothing like the unexpected things you get in software. The software equivalent is that of a buggy component whose specification is well understood - if you rewrite the component, you'll get what you expect. In software, proper specification is the rub.
I have worked with many electrical and electronic engineers (I studied CS) and not one of those engineers was on average better at writing reliable software. They did try hard to specify their systems in advance, but the actual systems soon started diverging from their specifications.
I grant that the absence of evidence is not evidence of absence, but it is equally wrong to keep maintaining in full faith (and without convincing evidence) that software development is an engineering discipline.
I have never seen anyone argue convincingly for nor against the engineering approach in software. If anyone has done a study on this, I would love to read it.
This uses your notation from the Dr Dobbs article, so that Ci (a category) is a user and D is a document (a comment?).
Did you use something like trigram signatures?
Also, is P(Ci) equal to #comments made by Ci/total number of users?
Interesting stuff jgrahamc!
What is also never mentioned is that what employees desire is as much the business of a business as other things.
But suppose we buy 100% into the maximizing shareholder mantra.
If you have programmers that are interested in these technologies, your shop is probably doing some interesting work (since otherwise these programmers would not have bothered working at your shop). In this case, careful leveraging of new technology (that is, choosing something that's not too far right on the curve for your purposes) can give you a leg up on the competition, since the programmers are happier and you can offer things that the competition cannot.
A manager that avoids new technologies in this context is not doing what is good for business.
It is a false dichotomy that what is good for programmers is necessarily unrealistic or bad for business.
Am I the only person on earth that rails against this? I trade my time for money, but I am no-one's "subordinate". To me, a manager is someone who makes sure I can get my work done and checks on the overall progress.
I guess I'm asking for a mighty downvoting but I really want to know if others think its okay and why its okay to be a subordinate (especially when the superordinates are so often less than impressive human beings).
Many in the functional world realize that some things are akward (see Peyton-Jones's talk "Wearing the hair shirt" about Haskell).
To answer the question about loops with recursion: you seldom write recursive functions when programming functionally but instead cast things into maps, filters and reduces. Thus it's not such a big problem (and the cool thing about using map & family is that you can replace them with parallel versions quite easily). With that said, some practical functional languages provide sugar to write seemingly imperative loops.
In terms of libraries, at least Scala, Clojure, F#, CAL, Nemerle (amongst others) ingrate well with either the JVM and/or the .Net platform. You can implement Erlang nodes in any JVM language (which I grant is not as good as calling directly into the JVM from an Erlang function).
There are definitely advantages to writing as much of your code as possible to avoid side effects (obviously ignoring the odd print statement to help with debugging), since your code becomes easy to test and easy to reason about. But in real world apps you will need state management - Clojure and Scala both allow this (in different ways) and I'm sure that F# does too (though I've never worked with F#).
I think that these three languages address many (all?) of your concerns. They all have cool user communities, so give one of them a shot.
Probably the best thing to do, is to put together the simplest thing that will do the task and to try to sign up some alpha testers.
I don't know if people will ever stumble upon a set of interaction constraints that will make people civil if they're not already committed to civility. In that regard HN has always been good (but not perfect, as evidenced by some of the episodes mentioned in this comment section).
If someone lashes out and gets a calm response instead of being downvoted to oblivion or without being baited, the whole atmosphere becomes much less toxic (even if the original commenter insists on trolling).
The levels of stress that I have can be debilitating and actually keep me from doing my work. It's useful to see lists like this to remind myself of what I should be avoiding.
That might be true for dense graphs, if you think that O(|V|^2 log|V|) is unfavourable.
A normal maze graph is planar and therefore |V| <= 3|E| - 6. Thus, maze problems can always be solved in O(|V| log|V|) time for a constant number of exits and starting points.
So, while the author made a little mathematical blunder ( single layer maze problems are efficient to solve), he's not the one that implied NP-completeness.
EDIT: Clarified my comment so that no-one can think I'm implying that an O(|V|^2 log|V|) algorithm is an NP problem.
For someone who's not a graph theorist, it's an easy mistake to make, since the longest path problem is, in general, NP-complete. He was probably just thinking of this problem.