skysight-inc/HackerNews huggingface dataset:
Have you tried a standing desk, yet? (Don't know if it helps you. It was good for my back.)
Reminds me on that article on GNU grep doing some speedy magic: http://lists.freebsd.org/pipermail/freebsd-current/2010-Augu...
I've only recently found out that by "Modern C++" most people mean the way to write C++ as exposed by Alexandrescu's book on Generic Programming - is that what you mean too?
This is one of medicine's major problems: such a study is considered to be required, yet no one with enough funds (read: big pharma) will execute a study of the enormous size required to control for all these variables (because there is nothing to be gained for them). For all we know, every mental illness is cured in 80% of the cases by changing to -- and adhering to -- a healthy lifestyle. As the situation is, there will never be a study that proves it.
The problem is not 'pay for performance'. In fact, that's not what they're doing!

The problem is that no matter how good you are, the most you can get is 6% more than what you're currently making. Some people improve far more than that in a year, and provide far more value to the company than that.

In my dad's time, he quit jobs that refused to pay him what he was worth. If that meant a 10% raise, when the cutoff was 5%, he quit. He didn't argue with them. He just told them how it was and that he would leave unless they paid him what he was worth.

Guess what I did this year? Yup, same thing. When I started with the company, they were really, really good about paying me what I was worth. But after a few years, management changed a lot and they started the 'it's a recession and we're capping raises at 5%' stuff. I knew I was worth a lot more, and complained. They refused to do anything, and gave a vague promise about looking at the situation in a year. I quit and went elsewhere to get what I'm worth. Instant 40% raise.

I started there as a junior dev, and actually suffered with that situation for 2 years before I demanded compensation, and that's how I got 40% out of whack.

So no, it's not about 1% being beer-money each week. It's about getting paid what you're worth.

Oh, and btw, that's not $6.40 per week for a year. That's $6.40 per week for the rest of your life. Future jobs will be based on your current pay, and if you let them take it from you now, someone will be taking it from you later, too. Unless you demand it.
I mean, is this a joke or a viral site or something? The About page explains that it was done by someone called "Sir Pastor Alhaji Babalawo omotodun, Ph.D, MSc, etc...", which sort of brings to mind the Nigerian emails. Couple this with the outregous "also get paid tons of money($1 for winning a special challenge per week)" and P(legit site) goes really low.

On a different note, in the longest palindrome problem, the C++ function header doesn't pass (or return) references, which seems to be amateurish.
Other than the stock apps and Google Voice:

Camera360, Jorte (calendar), Tweetdeck, Google Reader, Dogcatcher (podcasts), Dolphin Browser
May be they will produce a white paper on why Oracle's NoSQL is better than other NoSQLs :)
fixed, tks
Computer Bowl I (1988)
Yes, I would love this in Canada too!
SEEKING WORK

Experienced Ruby on Rails engineer (3 years experience), and Cocoa developer (I've been writing in Cocoa for the last 8 years).

If the project is big enough I can bring a team to bear on the project: I have a number of really good freelancing people I can bring on for larger projects, and/or depending on what kind of skillset your project requires.

Email, Github, etc etc avail in my proile
Maybe the people who make corporate purchasing decisions need to be reminded?
I like your simplified model, and I know random strategies are sometimes helpful. My point was that random strategies are not always helpful.

I worry people don't believe this, so let me use a silly outlandish example to prove my point.

Here's a game:
Suppose we have a countably infinite number of boxes, all numbered. You pick one to hide under, and I have to find you by looking under boxes which I choose, one at a time. I get to look at as many boxes as I like until I find you or get tired and go home.

Under box 1 is famed astronomer Neil deGrasse Tyson, who was spying on you with his (perhaps magical) telescope all morning. He will gladly tell me where you hid.

I now announce my strategy for this game, namely, to pick Box 1 and ask Tyson how to win.

Will you now respond with the original, "From the point of view of game theory, this is not an optimal strategy since it merely invites the opponent to avoid box 1. ..."?

The point of this silly example game is that randomized strategies aren't necessarily helpful for certain classes of games where one strategy gives you disproportionate information about the state of the game.

Guess my number games and battleship games risk being very similar to my extreme illustrative example, but I'll admit I don't know how much.

Bottom line: I just resent the insistence that good game theorists dogmatically REQUIRE randomness in all competitive situations. This is not necessarily the case.
Wouldn't it be sensible for the law to be that the loser has to pay the lesser of the two legal team's costs?
Interesting, but do we have enough information? To quote Spolsky...

A 50%-good solution that people actually have solves more problems and survives longer than a 99% solution that nobody has because it’s in your lab where you’re endlessly polishing the damn thing. Shipping is a feature. A really important feature. Your product must have it.

(http://www.joelonsoftware.com/items/2009/09/23.html)

This article doesn't go into details about the history of why Etsy's architecture is the way it is. It's entirely possible that this architecture enabled them to launch and iterate faster at a critical point in their history, without which they'd be nowhere.

Do what you need to now that will work. If your project is successful enough to experience a few orders of magnitude growth it'll need rearchitecting in some way anyway; build the heavy engineering when you know what you need, not think you know what might be the pain point.
For the other videos check out this index:
http://research.microsoft.com/en-us/um/people/gbell/tcmwebpa...
Some things are better left unsaid.
> except Yakuza kill, we just make you homeless.

Predatory tactics on both ends, my friend. See the subprime mortgage problem in the US.

Like I implied: Yakuza = violent means to an end, US Loans = non violent means to a same end within the respective field.

I am not implying banks do the same as the Yakuza regarding "protection" and bribery/extortion, though that does happen in the US, just on a different level (can't threaten politicians so easily with baseball bats). See http://en.wikipedia.org/wiki/Ralph_Nader#Automobile_safety_a... about how an attempt was made to blackmail Nader.
Pinterest: The Hot New Self-Expression Engine
This document is nothing more than an embarrassment for Oracle. "One size DOES fit all - and that size is ORACLE!" Really? Even the most entrenched, old school DBA stuck in the bowels of some drab insurance company in Indiana wouldn't buy that. I'm not a NoSQL guy by any means (check my profile) but the desperation in this doc is way more palpable than a guy like Ellison would approve of.
This is pretty far off topic now, but I'd suggest dropping the resentment for the bullies, you'll have a more fulfilling life and make better decisions and observations. (Like, for example, very little government money goes to welfare).
For germany I feel confident to claim that any projections you could make about ROI should more than warrant it.

I have a suspicion that Americans tend to underestimate Germany, thinking of Europe as something that might be comparable to the US, and Germany as only a small part of that.

In reality, Germany has 80 million people - similar to California, Texas, and New York state put together, and is as you say the world's fourth largest economy.

They also much prefer German over English, so it might well be a good investment for many startups to have a German English student translating their site.
as long as it has some backup in verifiable data

A discussion on TCO is very dependent on the context in which the analysis was made, such as application type, volume of data stored, volume of data indexed, type of data (e.g. is it a tree? is it a graph?), queries per second/hour, number of concurrent connections, analysis on further scaling possible (vertical / horizontal), analysis on the requirements for real-time ad-hoc queries, entry-level costs, and so on and so forth ...

Basically, the variables are so many and so complex that any TCO analysis (regardless of validity) won't apply to your case.

That said - I rarely feel the need for NoSQL, simply because I can fine-tune PostgreSQL to whatever needs I want. But I'm not running neither Facebook, nor Twitter.
>"Also please note as just a key employee we were going to give him 3-5% equity in the company."

A key employee who is putting $50,000+/year into your company is getting 3-5%?

Are you really worth $1million to $1.5 million after a year and will you be worth twice that next year...just so he breaks even (assuming he is only working 2000 hours a year)?

Sorry, but if you are losing clients then you and your cofounder aren't selling coal in Newcastle, and the fact that the programmer isn't welcome in the office and is being blamed for all the problems raises a question about who is actually a dick.
Pay for performance only works if the marginal value of pay is greater than the marginal cost of performance. A performance bonus of $6.40 per week is less than a third of that pay at 40 hours, so why would someone work more than an additional 20-40 minutes (depending on time usually spent at work) to obtain it? Evidence is that the value of their time is around $20 an hour, after all.
Linking External Databases Into Sage CRM (SageCRM)
Five steps to finding a CTO co-founder
Why Nokia is working on a new Linux distro for low-end smartphones
Er, Ev Williams was probably not the best example to use for "it's better to focus on one thing." Would the author have told Ev to focus on Odeo rather than work on that crazy, silly side project called Twitter? Perhaps Billy Chasen shouldn't have been "distracted" by Turntable.fm?

The article is essentially one big tautology: don't be distracted by distractions! Well, the problem is no one knows what's a distraction and what's the next Twitter. That's the skill that matters - not ignoring "distractions" altogether.

It's perhaps important to remember that Clay Christensen remarked that nearly all disruptive innovations look like toys at first.
Yea, otherwise I threaten you "bribe me or die" on camera. I bribe you, you blackmail me with that footage.
Some possible reasons a developer might think of it as a project and not as a founder:

1. Not enough equity, or there is a promise of equity but no sense of commitment

2. No voice. Feedback and suggestions ignored

3. Possibly unreasonable expectations from management. How do you know it should only take 150 hours? See item 2.

4. Developer might not have confidence in management

Or, it's possible that the developer really is the wrong person for your startup. I would suggest some introspection before the "Come to Jesus" meeting. Maybe you can turn this around. Give the dev a chance to speak his/her mind and be open to what they have to say. Make your expectations clear, set a short term goal (x, y and z need to be done by Friday) that you both can agree on. If that milestone is met, great. If not, you have your answer and can move on knowing you did your part in good faith.
It could be that, or it could be that the very best stuff was discovered years ago.
And the bible in turn paraphrased Spiderman: "with great power comes great responsibility."
I made this to help people crowdfund their birthday gifts, x-mas presents etc...

1. find products

2. add to cart

3. checkout

Using stripe for CC processing, heroku, rails 3 etc... Creating a payment api for social payments next.
Panda 2.5: YouTube (and Google)Wins Again
Right? They're alienating a very large developer community.

I tried to send them an email about ruby support and the typo on their compilers page but their email form doesn't even work. I take this to be way too amateurish and scam-like.
Google announces Google Trusted Stores
OK sounds like hell, but your programmer is probably not a dick, he's probably got other stuff on his mind and I don't just mean the family.

As founders you're no doubt driven people, it's what it takes, but you can't expect everyone to share your vision, or be able to give up their time or commit their future for something they didn't invent - even if it starts to take off - simply because it isn't their idea no matter what the incentives.

That said, perhaps what you are looking for is someone who fires on all pistons, and surely you can spot that in the recruitment process. The twinkle in their eye, the energy, whatever it is there'll be a clue.

Also have you tried breaking down the tasks into smaller tasks, maybe the sheer size of the project has overwhelmed him. That way you get to keep a good handle on progress and can easily switch to someone else if things go wrong.

Talking of which, you'll be surprised how many good programmers can pick up the ball and run with it, so don't feel tied to this one guy just because he has all the knowledge.
Guide on Making Pizza
I think it is because more "control" and "testing" over changes sounds better, and safer, at first glance than speed-to-deploy does. It's easier to choose the option that sounds stable.

But then over time, companies realize that their tendency to add bureaucratic gate on top of gate to the process has begun to harm them because they can't release simple updates in anything less than a few months.

Frequent and small deployments sound riskier, and tougher, at first.
I don't think so, no. Why should a person or company be financially punished for doing nothing wrong? Your suggestion means that if you are sued and pay for a decent lawyer to defend you, but your opponent pays someone dirt cheap (or no-win, no-fee), and then you win, you will be out of pocket for your own defence.
At least in some cases, it would be better of politicians had to 'eat their own dog food.'
I kind of think of it the other way.

It is overkill to implement a full fledged SQL database and write a bunch of SQL queries, if all I need is a persistent key/value store.

I've been playing with Redis lately, and it is really incredibly easy to use, and it maps quite well to the data-structures that I already have in my code.

There is certainly use for both types of database, but a lot of the NoSQL products are genuinely good tools (completely ignoring scalability), and make using SQL look like hammering screws for certain applications.
Waiting… to Sell Your Business
MySQL and Postgres are awesome for a lot of what websites do. They have advantages and disadvantages. Things like sharding tend to be premature optimizations except for write-heavy sites running at high scale. I prefer a mixture of SQL and NoSQL for the projects I work on. Redis, especially, is great at things like atomic updates and counters that become cumbersome in sql. With a well architected model-layer the complexity of multiple datastores can be minimized significantly. By using the right tools for the job, we are often able to simplify even versus using one database and a hacky solution.
What was your experience integrating with stripe?
> If your business model implies a scale-or-die condition, then I'd say it's fair to design your solution to accommodate NoSQL, but not waste time implementing it in production. It's a horrible waste of time to design something around a Cassandra cluster that will be hit once every second.

It sounded to me like he was saying that sometimes it's actually more work to figure out how to stuff your data into a relational db than a non-relational one?
The difficulty does not, but pay is only one form of compensation. Those with the most opportunity have many good options, some with more pay, and some with better work conditions. in other words, if you need a smart person you need to compel them to work for you.
Let's say my business is real time analtics---tracking mouse movements on the page.

This is tackled by quite a few startups, so it's not out of the realm of things we HNers do ourselves.

Mouse tracking can generate potentially millions of data points per day for even a small number of users. However, we only store a set amount of data per client.

If for example, you think that every point should be tracked individually you can easily run into the case where Postgres will be non-optimal under the read/write load.

Something like Redis on the other-hand might be optimal.

This is a case where its not a premature optimization, its just the right tool for the right job.
Are you short-sighted or long sighted?
Europe's largest LP posts study on VC performance in EU and US
I'm so used to reading "Not all who wander are lost" that my brain originally parsed this headline as "All who wander are lost". Then I clicked through and the URL was "all-who-wonder-are-not-lost", so I went back to check and see if I read it wrong. And I had read it wrong, but because I'd missed the "not". So I thought, "That's funny; the submitter must have made the same mistake and submitted it as 'wander' even though the article's title says 'wonder'." Then I clicked through again and the article's title said "wander".

I don't really have a point. I just wanted to share my mostly-irrelevant tale of mental tomfoolery.
I think that's where the "well-executed trolling" comment comes in. He essentially whipped everyone into a tizzy by complaining that a framework for helping to get better performance out of I/O-bound web services by handling I/O calls asynchronously doesn't work so well if you take a CPU-bound monkey wrench and jam it directly into the gearbox.

I suspect that it worked so well because the idea of using Fib to talk about performance is kind of built into the collective programmer unconscious. The whys, hows, and whats of using Fib to talk about performance are somewhat less well-entrenched, though. So there's room to trip people up by getting them to go, "Yeah, this sounds interesting, and I recognize all the words so it probably isn't technobabble!"
Kinect may act as a parental control body scanner in future
I wonder how long it will take them (advertisers) to figure it out.
* Lack of sunlight
The insane part is that a startup has bureaucracy, not that code is in a RDBMS.
How to hack Silicon Valley, meet CEOs, make your own adventure
Not that you can't do this in python:

python -c "print '\n'.join(open('LICENSE.txt','r').read().split('\n')[:-10])"

But this is besides the point.
but hard to believe in 2005 someone thought it was a good idea to build your business rules in your database layer.

I remember having that exact argument in 2005. Someone not only thought it was a good idea, but thought it was a good enough idea to aggressively argue with me for.
Agreed, there are things I can do with CouchDB that make me absolutely giddy. And I'm not talking about performance, and I don't even want to think about what the relational model would look like.
If this is the company I think it is, then they took my last name as well. They're legitimately using it, even if you may not like the use. I got around it by using the .me extension instead. You can always pick one of those others instead of .com.
GOP Presidential Candidate Herman Cain has a MS in Computer Science
Come to India. Please.
I second this. Can he also be ostracized from the internet completely on all devices/all his locations? In fact hit his office staff too since we are not sure who actually committed the infringement.
(1) the manner in which the domain name(s) is/are identical or confusingly similar to a trademark or service mark in which the Complainant has rights; and

(2) why the Respondent (domain-name holder) should be considered as having no rights or legitimate interests in respect of the domain name(s) that is/are the subject of the complaint; and

(3) why the domain name(s) should be considered as having been registered and being used in bad faith

------------------------------------------------

The issue is registered AND being used. It would be pretty hard to argue that it was registered in bad faith when it is his name. Of course, ask the Nissan guy about this, there are exceptions.
Bureaucracy is just process that you don't like, isn't it?
I fail to see how Perl-golf style conciseness is inherently more "productive" (particularly when it makes it harder to understand and maintain operationally important software).

I'm not sure the author made a great case, but it does matter. Unix admins often think in terms of lines, because lines are the default unit of action. No matter how much planning and cfengining you do, there are still times when an admin must take direct action on a system. When that happens, they use the interactive command lines. These lines often aren't repeated frequently and have no need to be stored in any file other than .bash_history, and therefore do not need to be read or maintained. In those situations, the conceptual and physical overhead incurred by something like 'import re' is most assuredly significant.
Interactive Web Platform for Guitar Lessons
Yes, reasoning about laziness and difficulties using types are library issues.

I disagree, if the language were strict by default, this was not an issue. It is a language problem that is forced on libraries.

However, for most Ruby web applications that I have worked on I have had to spend time re-writing slow parts of the application because Ruby was truly the bottleneck,

My point was that Haskell is often a lot slower than C of C++, so people will rewrite CPU-intensive code anyway. Look at many of the popular Haskell modules where heavy-lifting is done (from compression to encryption), most of them are C bindings. That code will be nearly equally fast in Haskell as in, say Python.

BTW. I am not arguing that Haskell not faster than Python, Ruby, Clojure, etc. But for computationally intensive work C/C++ are still the benchmark, and that is what people will use in optimized code. Whether it is Haskell or Python.

Particularly if a library is forcing you to learn about existential types.

But why is it? Because the language does not support the kind of polymorphism that is commonly used, in an intuitive fashion. People need containers with mixed types that adhere to an interface in some applications. And a commonly-used method to realize this in Haskell is by using existential types.

we can at least agree that async IO is a big win

Yes.

And likewise deployment to multi-core is no extra effort in Haskell/Erlang, whereas in Node, Ruby, or Python you will need to load balance across multiple processes that are using more RAM.

Since most modern Unix implementations do COW for memory pages in the child of process of a fork, this is not so much of an issue as people make it out to be. The fact that you mention Erlang is curious, since spawn in Erlang forks a process, right? Forking is more expensive than threading, but again, in most applications negligible compared to handling of the request.
You know, if Amazon aquired webOS that might even give them the opportunity to enter the cell phone market, which could be a logical next step after the Fire...

Oh, for a cell phone with an E-ink display...
I hope your code is compatible with mixed schemas. Otherwise your NoSQL is just moving the problem somewhere harder to test.
4 Best Foods To Eat
A new social media magazine called Media Tapper
Hmmm...that last sentence doesn't jive totally with me. As a business-guy, I'd rather diversify my risk over many deployments than over one deployment every six months.

The word "control" probably has more to do with it. The option that makes management more important (big requirements documents, for example) is probably the one management will choose.
Adapteva launches 64-core Epiphany-IV | thinq_