skysight-inc/HackerNews huggingface dataset:
I don't understand why you thought you could quit the whole company and still retain 100% of your assets, then come back 7 whole years later and complain that you were no longer an owner.
PayPal is now an identity provider
Thanks, Mike! We are definitely better guessing some categories than others. We're improving that all the time. The suggestions are a feature we just added last week.

It's actually free for services providers to make offers. We charge for ads, and may charge for some other premium features in the future.

Thanks again for take the time to check it out!
FAETEC RJ
Educação profissional: técnico de nível médio concomitante, técnico de nível médio subseqüente e formação inicial e continuada de trabalhadores.

Educação superior: Graduação tecnológica e normal superior.
Bedlam DL3: When "Me Too" Gets Out Of Control
>“Anytime Pearson and Google are used in the same sentence, it’s going to get people’s attention,”

Yeah, even when apparently this isn't a collaboration between the two, but just launching through Google Apps. It certainly doesn't sound that exciting either, sounds like a press release for a costly new service. Moodle is open-source already and is running many good services on campuses.
There won't be general-purpose walkthroughs, because the general answer is "don't change the database structure of a database that's serving live traffic: You'll never enumerate all the things that could possibly go wrong."

In most specific cases, there are alternatives to stopping the show during an upgrade. First, you check your backups! Then, there are various strategies. You can make many simple schema changes while the system is running. Or put the DB in read-only mode and still mostly manage to serve pages -- perhaps with an occasional HTTP 503, so hopefully that's okay -- during your upgrade. Or phase in changes over several releases, carefully architecting for backward compatibility. Or bring up a parallel system and gradually migrate active users to it. Depending on what you're doing, you may find yourself having to write a special upgrade script that migrates old formats to new formats, or even using database triggers to keep "old" and "new"-format tables in sync during the transition. A well-constrained database may help keep things sensible during the transition -- or, you may have to drop half of your supposedly-sensible constraints just to make the transition work.

Moral: Even if you know exactly what you're doing, live updates are more work: More planning, more code, more infrastructure, and/or more stress. In many real-world cases, you should just take the system down for a minute. Focus your engineering effort on making sure that "minute" is as short as possible, and in making sure that you can detect problems and roll back as quickly as possible.
And eye-witness testimony should be made inadmissible (and I think may eventually). DNA evidence has a 1 in 200 (ish) chance of being wrong[1]. Hard time to be a lawyer.

1. Source: The Drunkard's Walk. This is the estimated likelihood of a lab error, which by far drowns out the 1 in a billion chances the DNA match is wrong, but the numbers are not reported and not admissible as evidence.
"Why are you still deploying overnight?"

Because you don't hire a system admin to do that job for you. :}
That 36% number may be a little high since TNW is considering the Nexus One and Google TV as failures.

The Nexus One has greatly raised the level of high ends Android phones. It was a first attempt for Google to define Hardware in collaboration with manufacturers, and since they now keep doing that on regular basis I would say it was a success.

Google TV initial launch was possibly a failure, but the Honeycomb or Ice Cream Sandwich update will certainly be a re-born and, possibly, a worldwide "second" launch. I think it's too early to judge it.
"Isn't biology an application of physics and chemistry? What else is there?"

Emergent Behavior.

Even if you don't buy the emergent behavior perspective modeling biology as a flat plane of chemical and physical interactions is orders of magnitudes greater than most chemistry and physics models.
$100k is not entry level for a sysadmin in NYC. I get my numbers from the fact that just about half my company, including its headquarters, is in NYC.

I am absolutely confident that there's some role/vertical definition you can come up with where sysadmins are making $100k in the door. But I think you're discounting most of the market for sysadmins, just like the people on the other current HN sysadmin thread who all seem to believe that sysadmins also optimize SQL queries, fix C code, and teach systems programming to stupid developers.
Exactly. I once worked with a very smart Obj-C guy. I asked him if he could document all the method calls so I knew what they did.

He said: there is no need. In Obj-C the selectors should document themselves.
The fools who sold the stock to you initially instead of holding it.

To be honest, I am growing tired of arguing against people who believe that the economy is a zero sum game, along with all the other fallacies. I can just grow wealthy on the back of betting against them, which is what I suspect others are doing.
The best parts of Java were very notably not designed by committee. They were designed by Josh Bloch, or the edu.oswego team, or maybe Gosling. The best apache projects usually started off as written by one person or a small group.

The shitty parts, like J2EE, are designed by committee and more than that each committee has an implementation that they're going to sell right out of the gate. It's supposed to be a standard that solves problems, but each player has an incentive to try and lock you in, and is more concerned with selling software than solving problems.
Other filter words appear to be 'wow' and 'balls'
The only good point is #2: you want your people to be awake during the deployment so they can deal with any problems. The others basically amount to "You should have other processes in-place to avoid the same problems you're trying to minimize."

Three words: Defense in depth. You don't always need every advantage you can get, and this is a pretty costly one. Still, it's simply wrong to assume that a particular precaution is always needless.

Interestingly, you hit a bit of a sweet-spot if your primary customer base is located halfway around the world. You can roll out updates when your people are most wide awake, but when you'll only break things for a few users if something goes wrong.
It wasn't intended to come out as if I was complaining. Someone mentioned the podcast, it's not as though I brought it up myself. I liked the podcast in the beginning. It just simply took a different path than it should've in my opinion.

The title of it is "Build & Analyze" right? So, it should be about "building" things (whether that be coding, building said code, or as a metaphor for other things in life) and "analyzing" things related to the same... code or life.

But instead there is very little discussion of building... and the analyzing is ranty and uninspired.

One of the recommendations I made was Hypercritical with John Siracusa. Let's compare and contrast a bit..

Siracusa is one of those guys that just knows how to take something, whittle it down to nothing and find the faults. There's nothing wrong with finding fault in things. There will _always_ be faults, however big or small. The difference is in how Siracusa talks about them. He's critical of things to the point of beating a dead horse. Hypercritical is perfect for his podcast. Probably the most apt name I've ever seen for a podcast. But when he discusses these faults he provides some of the best examples he can come up with for _why_ he feels that way, and/or _how_ the faults they could be corrected.

Marco on the other hand just. Complains. I think he tried in the beginning to provide just cause for his complaining. But in the end he failed to be able to do it consistently. Instead, the podcast turned into another version of The Talk Show. At least with the Talk Show Gruber can be entertaining. Though I rarely listen unless the show notes show me something interesting. But Marco is trying to emulate Gruber and failing hard. Even his blog is taking on the same type of thing with a tiny bit more iOS discussion.

Either way. People can make their own opinion. I just hoped to make it a quick way for people to know to avoid it. If they're like me and they find annoying dick-ish podcast hosts to be on the do-not-listen list then they know right away that Build & Analyze isn't for them.
Will robots steal your job
Having built a custom cluster using vanilla MySQL + async replication, I can tell you that it's no walk in the park. Our requirement was to have the data shared across two data centers in different geographical areas with automated failover, and time from failure to failover completion of under 30 seconds. We managed to do this, but there were some very ugly parts. For one, we have no automated fail-back since promoting a slave, you lose the ability to deterministically figure out where other masters need to start replicating from (global TX IDs will solve this). We also get some false positives (much more than real failures) due to the fact that the cluster monitor has to be in yet a third geoarea. Lastly, this requires application support. We remedy this by having a common DB session layer and a messaging system for notifying all the applications of failures.

The good things about this are that we do get high availability with all the normal features of an RDMBS (JOINs, random queries, high-level query language, etc). We also have sharding baked-in so we get to distribute write queries across multiple masters. Having said that, the next time I need high availability I will be setting up either a two-node MySQL master-master cluster with mutual monitoring or some type of a different data store that provides eventual consistency.
I was thinking it was along these lines:

Coldplay are a British alternative rock band formed in 1996...

(first line in Wiki article)
To answer my own question in case anyone else comes across this: yes. I'm on iOS 5 and f.lux works great.
Check this post by one of the developers from a while ago: http://blogs.gnome.org/desrt/2010/11/15/gsettings-is-fast/

EDIT: Also, http://blogs.gnome.org/desrt/2010/12/19/more-on-dconf-perfor...
Incredible thing and inconceivable person(14 pictures)
"We have dropped PHP 4 support and we have refactored all the code to be strictly compliant with PHP 5.2+."

Exciting!

I have some projects written in 1.3. Anyone port from 1.3 yet and care to comment on their experience with it?
So you're saying that people interested in cryonics will not actually give more money to charities? Doesn't that go counter to the assertion that you've repeatedly made that cryonists are more likely to invest in improving the future?

People who care about the state of the world after their deaths are more likely to donate. How much have charities benefited from posthumous donations? A cryonist who does not expect to "die" has no incentive to donate in their will. At least religions say "you can't take it with you". Cryonics says "sure you can; put it in the bank".

You're also making a false connection between the desire for self-preservation and rational behavior. People do all kinds of stupid crap because they think it will keep them alive. They go to faith healers, they take dangerous or useless substances, they engage in pointless rituals, etc. I would say "pursuing cryonics" belongs to that list.
Read the linked paper, it's actually very good. It looks like they used good science in testing this:

"From our study, we conclude that both our method and the light probe method are highly realistic, but that users can tell a real image apart from a synthetic image with probability higher than chance. However, even though users had no time restrictions, they still could not differentiate real images from both our method and the light probe method reliably."
The bad news: a change in how iOS manages files in version 5 means Instapaper's ability to store articles for you to read offline has reached something of a limit. If you get low on space iOS will now delete Instapaper's copies of articles:

http://www.marco.org/2011/10/13/ios5-caches-cleaning

This is less of a problem if you are online all the time as Instapaper will redownload them, but it still kinda sucks.
hurr i'm swearing on the job. I'm crazy, me
I'm curious why you ascribe that preference to historical reasons. My exposure was in reverse order to yours but we have the same preference.
Ask HN: Any good introductory literature on design
Something similar to "Design for Hackers: Reverse-Engineering Beauty" but perhaps more in depth and with more theoretical background. Just browsing Amazon comes back with a lot of books, some with good reviews, some with bad. Seems that there's a lot written on the topic. So what would be a good start? I don't want web/computer design only - need some basic background too.
University of Washington (Computer Science and Engineering): http://www.cs.washington.edu/education/course-webs.html

Some of the video lecture series:

CSE 421: Introduction to Algorithms:

http://www.cs.washington.edu/education/courses/cse421/06au/v...

CSE P 501 Compiler Construction:

http://www.cs.washington.edu/education/courses/csep501/09au/...
Why spend all that time defining who you aren't? Put that same energy into creating something of worth!
How to make money using karmurl.com
How To Discover Amazing Talent For Your Startup
This is correct. Headlines are often written in the passive voice, e.g. 'Iraq Bombed' rather than 'So and so bombed Iraq'.
They have detailed personal information on 700m+ people. How is that not "worthy of attention"?
I said "tens of thousands of millisecond granular timers", you can safely assume multiple timers on any given socket. You are describing something as complicated that has been a feature of every major event library since ACE_Wrappers.

I'm at a disadvantage arguing about working with evented timers in multithreaded environments, because generally I event to avoid threads. In environments where I've done both (for instance, Cocoa), I dedicate a thread to the event loop and give it a message queue interface to the other threads.

"Waking the polling thread" is pretty straightforward. Just set up a pipe and ping it when you have a message you need delivered immediately. That's no more expensive than "timerfd".

I'm not arguing that select/poll are superior to epoll and kqueue (although select is just fine for many applications; why would I care, though; I don't write directly to select or kqueue). I'm saying that the Unix interface to timers isn't unscalable, and the scalability problems are in userland. Unlike select/poll, which did in fact have an O(n) problem in the u/k interface, the Unix interface to timers isn't a bottleneck.
New Battlefield 3 ‘Operation Firestorm’ Level Shown at GeForce Keynote
this is awesome. "bootstraping bootstrap"
Eyup. Self-published books are a real roll of the dice on Amazon.

While the existing publishing industry may collapse, publishers/editors will still exist - they will have to exist for a good book to be createdd.
this editor is 4.5 yrs old, no updates since then, total abandonware and was never meant to be anything else than a part of one much larger environment. it stays on that domain solely for my lack of attitude towards getting rid of it:), and partly for a sentiment. still amazes me, people are taking it seriously;).
I wonder if there could be a model where an author releases a "beta" version of their book at a cheaper price and then "fixes" suggested by readers are then released for free to those who bought the original. A kind of group editing. A later version 1 could be released at a higher price for those who don't want to deal with errors.
Why in the middle of the night? The economics of things, mostly.

At my previous job, we were still in process to get session migration to work so servers within a cluster could update while others were running.

At my current job, we don't have a cluster (we have a single over-provisioned server), and that method simply isn't in the budget for the foreseeable future. However, 3:00 AM PDT is 3:30 PM IST (India), which is where most of my team is, as well as the support staff they need (most staff there are on swing shift, as well). Thus, an early morning release is actually a very convenient, as well as lower cost, time to do the release. As the site is mostly US customers in both a B2C and B2B use case, this timing (around 6:00 AM EDT) works very well, and I don't see it changing.

I realize this doesn't scale for a global app, but it explains the lack of pressure to spend much consideration on higher tech, more expensive, deployment methodologies.
I work on medical software. Surprisingly, most hospital systems require a fair bit of downtime. Hospitals have downtime procedures that they use during these periods (basically switching to manual, paper-based systems).
Also look in to Suhosin[1] from the Hardened-PHP Project

[1] http://www.hardened-php.net/suhosin/
Great little composition & perfect experience to go with it. People here are bitching about the details - but the fact is that the design is simple enough to put focus solely on the mobile designs. If you're a designer and need a bit of categorized inspiration, this is perfect. Thanks for sharing.
The number of machines a sysadmin can support depends on what's running on those machines. This is a case where raw averages can be extremely misleading.
Sleeping Beauty online
Sleeping Beauty online
when the fairies had said caused the Princess to be carried out in the best apartment in his palace and to be put in a bed all embroidered with gold and silver.
I prefer Readability as well. I can't justify the $5 per month subscription though. I'd happily pay $20 for a lifetime subscription, but I'm not sure what they're providing that is any different from Read it Later, Instapaper, etc. that justifies the monthly cost. I know they are attempting to pay back authors, but I don't understand why that must be a recurring cost. $5 per month is just a tad cheaper than what I pay for Netflix or prgmr.com, and I don't think it provides near the value of those two. Now when I get a Kindle Touch I might change my mind.
I was hoping the author would have some deeply insightful answer to the argument, "because the deployment requires the site to go down for a few minutes and we want to avoid inconveniencing customers" but he avoids that topic entirely.

That's the number 1 reason for an overnight deployment, by far! If you can deploy code without bringing the site down, then of course, do it during the day!
This is incredibly reckless and naive advice.

You roll out when it least impacts customers because:

1. Impacted customers affects your bottom line. Minimize that and you minimize losses if something screws up.

2. Murphy's law. I don't care how much testing and QA you do; stuff will ALWAYS creep through, and sometimes it'll be nasty. QA works to minimize this, but it can't eliminate it entirely due to diminishing returns. Show me your guaranteed bug free deployed code and then I'll consider changing my view.

3. If you've designed and tested your rollback procedure prior to actually doing it, the chances of not being able to roll back in the real deployment is orders of magnitude lower than the chances of a failed deployment requiring a rollback, which in turn, if you've done your testing and QA, is orders of magnitude less likely than a successful rollout (but not 0, thus the midnight rollout).

If you're worth your salt, you have a tested rollback procedure, laid out in simple to follow instructions (or better yet, an automated rollback mechanism with a simple-to-follow manual process when the automated method inevitably fucks up).

You rollout, and if it fails, you roll back. And if that fails, you use the manual procedure. You should have the entire process time boxed to the worst case scenario (assuming successful manual rollback) so that you know beforehand what the impact is, and won't need to go around waking people up asking what to do.
Which classic brute force Ruby solution was the right call, seeing as how Bundler (a) improves ad-hoc packaging dramatically and (b) has gained widespread adoption.

They did the simplest thing that could possibly work, and ended up delivering 65% solution; now they're iterating. The hard work was getting people to adopt Bundler in the first place.
newb commit msg: <nocomment>

uber commit msg: fuck
The extortion accusation is just legal hardball, I assume. Remember that the OP hit first with the cease and desist along with a demand for $12M. So they hit back (though perhaps overstepped what is legal themselves, I don't know the law). Certainly they don't get brownie points for niceness, but they're playing on the same field as the OP.
A near-instantaneous switchover is possible if you're migrating a database to a new schema, but it's pretty hard work.

For this to work, every action that will result in a database write needs to go in log, and that action log needs to be replayable be the updated version.

In the context of a web application, you have:

1. Take your database backup, start recording action log.

2. Perform your database migration against your database backup.

3. Install your updated web application (not available to users yet).

4. Test your updated web application.

5. Disable your existing web application.

6. Replay the contents of your action log using the updated web application.

7. Making your updated web application available to your users.

It's definitely not a trivial matter to sort out: it means lots of time working on your deployment process, for example you have to be set up to have both versions deployed simultaneously, which likely means a lot of mucking about with URL rewriting. The application also has to be built to support it.

Maybe there is a better way?
This is quite straightforward. You either own stock in the company or you don't.

You own stock in the company if you received shares when you founded it and/or if you received options, vested them, then exercised the shares upon leaving the company.

If you own shares, you produce the certificates, and the acquirer will buy them from you.

If you don't, you don't.

No attorney can help you if you claim to own shares in a company without actually owning any shares.

The discussion about what you "deserve" and "don't deserve" is irrelevant. You either own the shares or you do not own the shares.
I'd be willing to stake some money on a bet that they're going to regret the decision to build key Ruby infrastructure on Marshal, say, within 12 months.

Having said that, I cannot at this moment tell you how to take over a Ruby runtime with a malicious Marshal byte string.
Apple still plans to make synthesize the default behavior in the future, but they encountered problems of C ambiguity that prevented it from shipping for Lion.

I don't think how old the language is matters, especially since it has seen several major updates in recent years.
I love the extensive use of teapots. On a previous life, I had one (a physical one) on my desk.
That's a good point. I think the success is what changed him. When the podcast started he was just starting to become a member of the "outspoken" members of the community. Thus, he was sort of the new guy.

You know what I'm talking about. The new guy that's quiet because no one knows him outside of "hey, he's the new guy." But as you get to know him, and he becomes more comfortable he starts to show who he really is as he becomes more outspoken.

Now, I don't want to say to not be yourself, and you can't please everyone. But I preferred the first 5-6 episodes of B&A over all the others. He was humble and interesting. Somewhere between 7-15 the humble was disappearing and the interesting vanished.