skysight-inc/HackerNews huggingface dataset:
I feel like this is taking Zuckerberg's quotes out of context. I watched that interview, and more got the impression that he was simply pointing out the reality of the situation. Of course Facebook wants to keep great employees, and of course they try their best to do so.

The problem is that they know that great employees in a startup are, by definition, the people who always want to be working on the next big thing, and nobody is ever the next big thing for long. Facebook knows they took a lot of talent from Google when the next big thing moniker shifted their way, and they know the next big thing after Facebook (maybe Twitter, maybe someone not yet in business) is going to do the same to them. There's simply no avoiding it. You can only IPO once.

I didn't take his quote at all to mean they don't want to retain good employees or that you shouldn't bother. He's just pointing out that to a certain extent that's impossible and it's best to just admit that and work around it.

Also if I'm not mistaken Zappos is based in Las Vegas, and keeping programmers around there is a lot easier than SV.
It sounds interesting. Did they tape it?
My experience is that the third graders know how to multiply without a calculator. But they use the calculator in 6th grade through 12th grade. By the time they get to college the connections in their brain used to multiply haven't been used in a long time and thus they have forgotten it. It isn't a travesty though.

It used to be the case that high school students were taught interpolating polynomials but they aren't anymore. It used to be taught to make estimates on what log(1.0356) is based on a table to values. When calculators became common the old timers would say things like,

"Wow, kids these days. They don't know anything. They have to rely on a calculator to find what log(1.0356) is. I can do that using interpolating polynomials and a table of values."

I suspect everyone on this website using a calculator to find log(1.0356).
Apple:Sprint::Google:Verizon
That sequence is called the Konami code, which you can read more about at: http://en.wikipedia.org/wiki/Konami_Code

If you're interested in seeing other sites that use it, check out http://konamicodesites.com/
My guess is that the answer is an unsurprising "It depends".

A high turnover can (emph. can) facilitate an upbeat, fast culture. Someone comes in, gives his fresh perspective on that particular problem-set and moves on. I sincerely doubt that Facebook doesn't full-heartedly encourages retention for key employees to ensure stable operation, testing and so on.
The most important question to ask before taking seed money (from VCs)
There's a tape rolling, but no live stream. I hear that the recordings will be available "eventually" (har har).
We verify in a quick Google search:
http://www.google.com/search?hl=en&safe=off&q=sin(pi...

that sin(pi) = 0.
Try doing the samething on the google reader. You will get the Ninja !!!
sin(pi)=0

I wouldn't feel ignorant or anything. The article left out that information seemingly on purpose, presumably so that people would try to figure out where the i went.
For those of you interested in a longer look at this, check out "E, the Story of a Number" by Eli Maor.

Yes, I read when I should probably be hacking.
The formula is:

e^(ix) = cos(x) - i sin(x)

Since sin(π) == 0, i * 0 == 0 so you have cos(π) left which is -1.

So in sum:

e^(i π) = cos(π) - i sin(π) == -1 - 0 == -1
Berlin NoSQL last week:

http://blog.isabel-drost.de/index.php/archives/99/nosql-berl...

http://www.h-online.com/open/features/Happenings-NoSQL-Confe...
Interactive Maps of the Accents and Dialects of the UK
Non-ASCII domain names are coming
And furthermore, if you're calling malloc enough to make checking your mallocs have a significant overhead, you're doing it horribly wrong.
This seemed a bit harsh, but (after consulting Wikipedia) I'm guessing you're trying to say that even after doubling to 16, it still sucks compared with "common RISC processors (which typically have 32–64 registers) or VLIW-like machines such as the IA-64 (which has 128 registers)."
Valid point. Anyone know exactly what VC program he is talking about?

I'm really curious to see how the Sequoia thing shakes out for YC.
Right you are. I should have used a different word than "riskier" there as it doesn't really fit my intention. More precisely, I would say that single founder startups are less likely to succeed (therefore riskier to fund if you are funding them). I don't think that there is a coincidence that YC looks at single founder companies more carefully, or that pg listed being a single founder as the #1 mistake that kills startups [1].

Again though, there are plenty of success stories for single founders. I would posture that the ratio of companies which are ramen-profitible to those which aren't is higher for multiple founder startups however.

1. http://www.paulgraham.com/startupmistakes.html
This is really interesting--I've always been annoyed by this problem, and amazingly Google hasn't fixed it yet. My startup is actually selling a product that is very similar to this, and looks to solve the same problems, but I really really like the "if a business isn't open, it'll tell you about similar ones in the area that are."

I'd like to hear more about your app, how much traction you have, etc. The biggest problem with making this work, of course, is to have city-wide (or country-wide) buy-in by all the businesses. Because is a good percentage are not updating this product with info for you, than it's useless to the end user. This last problem is the one we have solved.

Feel free to contact me if you'd like.
Rocking out with JamLegend
I developed a brazilian barbecue calculator called Churrascolator: www.calculoparachurrasco.com.br. It's a 2 month project. It is the greater and better site in this segment. Try it!
This came out around the time of the Star Trek movie. It's a reference/parody of the absurd lens flares in that movie.
Content Isn’t King. Relevant Content is King
Facebook is so backwards. Everything I hear about Facebook as a corporate entity bodes very poorly.

Employee retention is one of the number one most important things in any company, especially software companies, and double-especially in software startups.

A lot of executives and executive-types have absolutely no comprehension of the real cost of training a new programmer. If you have any kind of complex codebase, it's going to take _several months_ before a new hire can acquire ideal productivity -- and no, pair programming doesn't make this possible in a day and a half.

Startups have more than enough problems as it is getting something off the ground even in cases where all the founders stay with it all the way from concept to launch to profitability. Many startups whose original teams are intact die out before they become profitable.

Changing the lineup is just going to make things that much less likely, especially if your tech guy drops, because the tech guy knows all of the ins and outs of your actual product, which is probably undocumented and messy, and it will take a good programmer a long time to acquire the same level of familiarity with the product.

There are times when you don't have any other options to cut someone loose, but I would avoid it wherever feasible. Your company's essence is its employees; they run the company, their philosophies, management, and implementations are delivered to your customers, and they understand your domain, your products, and your accounts -- this isn't just intuitive knowledge that any qualified person (in whatever profession; accounting, sales, etc.) can waltz in and pick up, and retaining that wealth of information is critical to any successful business.

At least at most of the places I've worked, poor retention occurs when there is poor communication, disregard for an employee's cares and well-being, or a combination of the both. I don't understand why so many managers and executives have such a complex and insist on abusing subordinates, but it should be seen that doing so gets you nothing but angry ex-employees and ever-diminishing market share, relevance, and cashflow.

Fast turnover is such especial death for programming departments, and fast turnover almost always indicates serious systemic issues in the company.

Zuckerberg is crazy to think that this is legitimate strategy; it must be that he has seen the retention rates at Facebook and is now saving face by claiming it's part of some overarching corporate strategy so that the unprofitable Facebook can keep getting funding to maintain and purchase its servers.
What you've described is called "consulting". It can be useful occasionally, but not very often. You don't hire on full-time employees as consultants without specifying that, it's a recipe for bad things. Employees expect a steady and fulfilling career; consultants consult, employees are employed.
More precisely, I would say that single founder startups are less likely to succeed (therefore riskier to fund if you are funding them).

I'd agree with that.
Make the Mobile Web Faster
"without literally killing the single founder." is the proof that you note in the opening line.

It's true based on your hit-by-the-bus risk alone. The catastrophic risk (something goes wrong with a founder, their family, etc.) is diffused by having a portfolio of founders.

The business is a function of the people; lose a person lose the whole entity.
I was taught programming at a (quite big) university at Toulouse, France. First years were taught Ocaml (Caml-light, actually). The first 2 hours took place in a lecture hall and were about the lexicon of the language: authorized characters, possible identifiers, keywords… A typical "by rote" course.

On my second year, I took a more specialized route. Among other thing, we were again taught Ocaml, as if we learned programming for the first time —which was the case for many of us. This time we were no more than 30. The first 2 hours directly jumped into expressions and functions. Much less to learn, much more to understand. Overall, this second course was faster, by a factor of at least 3. And the class understood it all.

Anyway, one aspect of rote learning we always had was the downgrading of our program in the case of minor syntax errors.
I also didn't get the "Register to started" link.

I found the FAQ linking to "There are no FAQ" kind of odd.. Then why have a link to FAQ?

Also, when clicking the "ask a question" link does anyone want an alert telling them to register then use the contact form?

Unless this is just beta stage stuff, I think there are better ways to do this. You could take them to contact form and offer to chance to register there as well.
He's probably right in that the American culture / schooling seems to favor memorization, but the distinction between "problem solving" and doing things by recall is fuzzier than he implies. A lot of problem solving can be cast as examining details to find a match and looking up how to proceed. (That's not a terrible description of Prolog, come to think of it.) The reverse is true, as well.

Is a sysadmin troubleshooting an erratic network and starting with checking DNS doing what he calls problem solving ("my experience says checking this will narrow down several potential causes") or working off memorization ("many cross-cutting issues are caused by DNS, check there first")?
Sorry. I didn't want to sound harsh. The x86 ISA has a register starvation problem. I am sure the phone I am writing this on has a far more elegant and modern processor than the PC I'll return to after I finish lunch.

The sooner we can ditch x86 (and that includes amd64), the better.
I'm not sure why I'm doing this, but I'll try once more...

'My argument' was not that there are roughly almost equivalent words in English. There are multiple things:

- the case of linguistic relativity is largely resolved contrary to your view, but you don't appear interested in talking on the level of the informed intellectual debate

- I cited a vertical example of culture shaping language, rather than some other direction. However, the death of English would not mean the death of misogyny.

- Native Americans speak English, but retain a much different and largely unchanged culture, but you didn't see fit to address it. This point alone contradicts your claim of the "completely intertwined" nature of culture and language. Note also that America dwelling English speaking Asians retain a respect for elders and dutiful study habits, all while speaking not a jot of their culture's original language (in the crude sense you'd want us to believe it- no one's stuck on proto-Indo-European anymore). Various Amish communities preserve entire eras while speaking more and more English.

Could you elaborate on how 'usted', '-san', or 'Mr.' are necessary to a specific culture, no substitutions?
Write this as e^(iπ) + 1 = 0 and you have my favourite equation.

It relates all the fundamental mathematical numbers: e, i, π, 1 and 0.
I think the postulation that most programmers like to hop jobs is incorrect. It's always been quite a hassle for me. Programmers, like others, prefer steady income. They prefer steady insurance and easy taxes, and all of the other benefits of staying at a job.

Facebook, afaict, is losing talent because its management is out-of-touch, overbearing, and ineffective. Google is losing talent because it's well on its way to becoming just another corporate entity.

People want to work somewhere fun and small. This usually describes startups. Google is now huge and is suffering some symptoms of that hugeness, and it's driving developers who were attracted to Google's startup culture out.

I think that it has much more to do with an acceptable atmosphere than "the next big thing".
> you can read the online docs, but you don't really get it until you read a certain book.

Isn't that expected and normal for anything that involves thinking about things a different way? D has language features that most programmers aren't familiar with, so to use the effectively involves a shift of thinking. Same with Grails.
If you draw a Sine graph, you will see that sin(x) is zero at 0, pi, 2*pi, ...

If you draw a cosine graph you will see that it is -1 at pi. Therefore in the above sum the sine part just falls away.

It is easy to see that the above is true when you recall that cosine(theta) = adjacent side/(hypotenuse). Since pi=180 degrees, adjacent will be -1 hypotenuse 1 and opposite side 0.
How To Upgrade Ubuntu 9.04 To 9.10 (Desktop & Server)
... using the fundamental equivalence relation =, and the operations +, * & ^
I think a lot of those attributes are less valuable in today's world, mostly for technological reasons. :)

Patience: everything from fast food to ATMs to self-checkout at the grocery has made patience nearly unnecessary compared to a hundred years ago.

Wisdom / experience / skepticism / perspective: most of what passes for 'wisdom' is merely knowledge; many such things are right (but mostly can be Googled), and many such things are wrong (because the sample was too limited -- the saw about anecdote vs data applies). In any case, I think it's far more rare to be wise than old. All these seem like they're aspects of the same thing.

Faith: Unless you meant 'trust', I'd say this isn't a net good, anyway. If you did mean 'trust', then I'd say it goes more with youth and innocence than the
elderly.

Financial maturity: I grew up poor, and having lots of poor, old people around will disabuse you of the notion that older people are necessarily financially
mature; this is more a function of class than age.

Honesty: With pervasive surveillance, we're about to be forced into being more honest than people have ever been. This is actually more likely to affect the young first, rather than the old, as various MySpace and Facebook scandals have already shown. At some point, people will begin acting as though everything they do is on camera. Some of us already are.

Thrift / self-sacrifice: There's less and less need for this, as we're immensely more wealthy than we used to be, and in spite of the gloom and doom about the economy, that's likely to continue without some really massive government intervention.

Perserverance / wit: These seem like personal qualities independent of age, in my experience.

I accidentally downvoted you (while selecting text); sorry. :(
Be more productive using Eclipse
Some tips to help make you more productive using eclipse
Speaking about hackers, retention is probably underrated.

I have personally observed that a tremendous amount of software knowledge and understanding simply walks out the door when a really great designer/hacker leaves a team. The ability to simply ask the hacker who built some part of the function a quick question about the "big picture" rather than reading through lines (sometimes many, many lines) of code is a costly loss.

My extremely limited experience with acquisitions has been that employees at the acquired company are given large time-based retention bonuses. This is a market recognition of employee value. In some cases, this is kind of a waste - not everybody at a company is equally valuable. But there are always a couple of hackers on board who built the original codebase and you need to hang onto them if possible.

Of course, I've also seen companies acquired in what appears to be a strategic move to simply acquire the customer base too.

I believe the idea of employee value is at the heart of what Y-combinator is trying to do - recognize that some people can produce software that is capable of creating greater value than having that same hacker sit in a cubicle writing the next drop-down menu item in MS Word/Quicken/Oracle.
Pi is Wrong: http://www.math.utah.edu/~palais/pi.pdf

It should be e^(pi i) = 1, but pi was unfortunately defined at half the appropriate value in the 17th century.
Imagine you're a complex number, which is just a type of 2-vector.

Exponentiation is to do with growth at a speed which is a multiple of how big you are already.

i is the multiplication which turns you through ninety degrees.

If you grow in a direction which is at right angles to yourself, you turn rather than increasing in magnitude.

Pi is how long it takes you to turn through a half circle.

So if you grow at right angles to yourself for time pi, you are pointing the opposite way.
I used to love sailing on Lake Erie but once I started doing it seriously in the Pacific my sea sickness kept getting worse and worse to the point it was impossible. I really hope to find a cure one day or have it reverse itself (which I guess does happen).

Anyways congrats on following your dreams!
Beautiful Cars Wallpapers, Free Cars Photos, Desktop Cars Pics
Over the last 100 years, car manufacturers have designed some many cars like amazing cars, fastest cars, beautiful cars, electric cars & eco-friendly cars. It's hard to agree on a list of the most beautiful cars ever produced because inevitably personal taste comes into it. Here is what people consider to be the most beautiful car in the world. Some of them we agree, some we don’t. But the point is that they are master pieces in the automotive industry. So, Which is the most beautifil car in the world? Here is the 15 most beautiful fastest cars wallpapers, free cars photos & desktop car pics. You can also see Funny Cars Pictures, Women's Cars, Celebrities Cars photos, fastest cars wallpapers, hot cars wallpapers, sexy car photos, nice cars images & many more.
Yahoo's humongous new HQ -- images and video
Start Your New Business In Just 30 Minutes
Believe it or not, you really can come up with a good business idea in just thirty minutes. The key to a good majority of business sense is the simple old addage, “buy low, sell high. All that really means is take what comes easy for you, but not others, and use it to get something you want.
Another rhetoric on the obvious. When will Atwood write something ground breaking?
For those of you who enjoyed this submission, David Pache (Dache) has a section of his portfolio dedicated to such articles. For example, here's the design process for the Directed Edge (YC '09) logo: http://www.dache.ch/thedacheboard/article/directededge_logo/.
I find it fascinating that people see IKEA as good design. I am a customer and fan of the company, but their sheer size make them levelers of culture and charm eradicators. It is for furniture what McDonald is for local cuisines.

IKEA is probably the worst we Scandinavians have done the world since the Vikings; easily beating ABBA. It might even rival the Goth tribes' (claimed origin isn't far from where IKEA started, btw) destruction of West Rome.

This was depressing, I'll go support some of the good local music culture (Death/Black Metal) this weekend, to make amends for my ancestors.

(Sorry for wasting people's time, but it is Friday and I'm a bit fed up with some specs.)
Simple idea. Simple answer:

If your employee kicks ass, retain them.
If your employee is average, let them go.
The article says:

"Why abort with an error message, when a segmentation fault would do? With a segfault, we can at least inspect the code dump and find out where the fault was?"

abort also produces a core dump, so this is a bad idea for that reason too.
D1 + Tango == yes! Excellent combo, but serious lack in the toolchain department. DMD and OPTLINK especially is a failboat currently. LDC is based on LLVM and is "the future", but lacks windows support (exceptions! and this is inherently LLVM's problem now). DDBG is a good debugger, but is unmaintained. GDC is D on GCC, but is unmaintained.

D2 on the other hand doesn't feel like D anymore at all. Sure, there are a couple of nice things in it like ranges, but on the general perspective I could make this comparison: D1 is like C with C++ made right. D2 is D++, what C++ is to C - bloat and inconsistency.

There is also a huuuge problem with D2 and leadership/drama, which split the community. There is also problem with Phobos vs Tango - where Tango is clearly and measurably better, but that thread of issues leads to leadership drama.

Let me be clear on this (I use D every day for my projects - I am into graphics/gamedev with it). Do yourself a favor and learn D1/Tango - toolchain is bearable and there is a book about it from Apress. Community is responsive (#d, #d.tango on freenode if you demand prompt resolutions). Use Tango from SVN, use LDC or DMD if you are on Windows.

Also, check out http://www.team0xf.com:1024 - especially dog (OpenGL platform agnostic binding) and hybrid (gui on top of it). Check out http://www.dsource.org .

There are some movements within the community that will resolve by themselves soon enough - it's too good to fall apart. In the mean time you should really do yourself a favor and give it a go.
A Remarkable Comparison: Affordable Student Loans vs. Affordable Housing
Firstly, I've never had a malloc fail because I code very defensively.

If memory is likely to be an issue, you should control the usage of your memory to start with.

Also, the virtual address space is usually bigger than physical memory (on non-crap OS's and libs) so the performance of the memory access (when swap is involved) is an issue before you get to the stage of running out of memory. Last thing you want is MMU faults and time in the kernel to worry about.
D might not be better from the glance over it, but it's little things in it that REALLY add up. I strongly recommend anyone who ever wrote C++ code to give it a go for at least a couple of months and see for themselves. That is the best way to measure - I can only give you my sincere recommendation to try it out.
I didn't read it that way, I read it that because he set things up in the way he did, "Effectively, no one could now pay a bribe."