skysight-inc/HackerNews huggingface dataset:
Practical continuous deployment
For me (UK, not US) it increases it.

Nobody outside the financial sector uses it here, at all. And 10M is always understood to mean 10 million, never 10 thousand (that's 10k).
Mind Palace
This is very helpful, because even though I can produce css I sure didn't know the names of anything.
There is nothing we can do, really. Money is very close to power, and obviously the relatively poor (those who rely on a salary) have far less say and control than the extravagantly paid (those who do not require a salary). It is a fundamental trait of our free and capitalist society. We're merely mourning obvious inefficiencies, "bugs" in the convoluted system of laws and philosophies and culture that govern our society.

This is a suboptimum outcome, in our opinion. Watching inequality rise dramatically over a few short decades only bolsters the belief that these are suboptimal outcomes.

And watching these unmeritorious fools perform poorly while being paid thousands of times the average pay of their own staff is disheartening. It's obviously not a meritocracy. It's obvious that the extravagant, suboptimal pay scheme isn't buying quality leadership, nor is it rewarding any kind of out-sized risk on the part of management. Tiny risk compared to venture or entrepreneur, small or negative benefit, massive reward.
Google declares war on vertical videos [video]
As logfromblammo notes, this is a very old thing. Perhaps as old as agriculture itself.

That said, I see nothing wrong with the branding, as an education and promotion drive. If it gets more gardens in, all the better.

(I try to beat the "input costs" with my home container drip system, and not abuse the planet by growing $400 vanity tomatoes. Recycle, reuse, buy on closeout.)
It depends which point of view. If I made a movie of the simulation and then played it backwards, the gas would go into the box.

There is nothing in your experiment that says this is wrong. In your experiment, you must wait, and therein lies the problem. You've implicitly put a forward arrow in there.
Some registrars even provide such a service for free (well, included in the annual registration fee), though look for reviews to see how reliable your registrar's is before trying it in anger.
Why don't you just leave it up and running? Open-source it, let people run it on their own servers?
Surprised how nice the visualization looks, given how ugly the Bloomberg terminal is
U.S. Venture Capital Investment Highest Since 2001
Unfortunately not. Since all JS is going to be transferred to the client, if the key is in the JS the client has access to it.
My to-do list is on a paper. I wrote it with a pen.

I'm not cramming my entire life in there, just the crappy errands and chores that I need to do. Otherwise I'd forget to do something, or be distracted by something I need to do later. Also when I finish my tasks I know that I'm really finished, and I'm not constantly thinking "did I forget something?" or "What else did I have to do while I was out?"

I feel there would be no use for a to-do app. To-do lists are just too low tech. Making it an app just makes it too complicated. Note: that doesn't mean don't digitize it if you want to.
I bet its a lot bigger than you think. For example, you can handle a ton of views on something like WordPress or Ghost with DO's smallest offering. Especially if you use it in combination with caching and and a reverse proxy like Cloudflare.
MongoDB will be shipped as part of every RHEL installation. So pretty sure it is actually going to be getting even more popular.
I thought the recommendation would be use Discourse or something like that. Seriously, this is like the first post in years by this guy that doesn't mention Discourse (thank god).
5 tools for collaborative coding
I resized a 1024 instance to 2048 last night and it looks like it is already running on the new processors (from /proc/cpuinfo): model name	: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz

Should I upgrade? Do I want 2 x RAM for 1/2 vCPUs? =)
I've had success with leaky todo lists. Basically, write yourself a todo list for, say, today, then at the end of the day, trash it, pretty much regardless of how far you made it. If a task is to survive the next day, it should get there "organically" rather than by being blindly copied. If you find yourself copying a task more than three or four times, that's a clue to drop the priority. (Only a clue. Sometimes things happen that don't really release you from any todo obligations, like sick kids, but it's still at least a clue.)

Though I tend to find this is more useful for weekends when I have to figure out what maintenances tasks to do than anything to do with programming.

For development, another approach is to just learn to live with the Katamari ball. Yes, my project has about 1500 open "bugs"/issues. That's life. The only todo-ed-ness that I accept is that I need to at least look at the incoming list and deal with them somehow, but "clearing the list" isn't on the table, so why stress about it at all? Some people can't seem to do this, so they'll have to seek other solutions, but this works for me.
Bandwidth - How big the pipe is.

Transfer - How much they let through the pipe.

Just a guess.
Maybe the first one or two challenges could be available online, and requests should be accompanied by the answers to those. Maybe that would reduce the volume somewhat.
Can You Solve This?
This is my newest game that is available today. Get it for iPhone and iPad.
I've worked over the last two years on a library called Falcon.js (http://stoodder.github.io/falconjs/). It's your typically MVC/MVVM structure with similar concepts as Backbone (Models, Collections, Views). But utilizes the awesome data-binding architecture of Knockout. Falcon's core belief is that front-end developers shouldn't explicitly have javascript mixed with html (or vice versa). This is made possible only because of how Knockout handles data binding and templating. Falcon adds common sense architecture around that belief. Take a look! I'm always excited for feedback. I've use Falcon in many production level apps both for desktop web and mobile hybrid apps.
I too, have tried countless amount of to-do apps, and none of them stuck with me for more than a week or so. It's frustrating. I look around me and see so many people use to-do lists, and it seems to work for them. So why then, does it not work for me?

I have no idea, but I have more or less abandoned trying to use a to-do list at all, simply because I work perfectly fine without one, so why change that?

Jeff mentioned 3 things, but I give myself a little more flexibility with that. Sometimes I can have 4 or even 5 if it's really necessary. But these are events or tasks that are really important to me. In fact, my mental to-do list usually takes at least a week or two to get fully "checked".

I wake up in morning reminding myself of the 3~5 most important things within my next week or week and a half. Things like securing a major contract, giving the best man's speech at my friend's wedding, maybe even writing a blog post (or simply coming up with ideas for one). Although I've been incredibly busy lately and have had no time to blog, I keep putting that on my mental to-do list every week, and it becomes part of the way I live. I start to notice things I want to talk about, give it some time to circulate in my head, then either discard it or write down the general idea for when I have time to write it. This works SO much better for me than the alternative.

How do I keep track of everything else? Simple. I make them routines. If I want to dedicate a year to learning chess, I dedicate time to it every week and treat it like any other important event in my life; it cannot be cut out unless it's absolutely critical. Having routines like these help me a lot with managing stress and frees my brain to consciously work on other things. Everything else that does not fall into the routine category or my top 3~5 to-dos is simply not important enough, and I cut them.
This might be a good thing for some customers.

In the past on certain host servers you get a great experience - low latency and the ability to burst CPU usage. However occasionally you get provisioned on an awful server where the latency of your server varies significantly, and your apps struggle to get a decent share of the CPU.

I'd rather see my servers have a small but more fair amount of burst instead of all packages getting 8 CPUs with some of them getting a bad experience from noisy neighbours.
Having a schema most certainly does help, since you can know with certainty what shape a specific record has before retrieving it.

If you have an ORM for your schema-less database, you get roughly the same thing, but with weaker guarantees.

Correct data migration requires knowledge of the schema of the data.
Only thing really hurting my "to do" list of org-mode is that I have about 3 different computers that would need to be synced with what I'm currently "doing." I'm sure there is a good way to sync my settings, but I don't know it right off.
article says he faces 20yrs? thats a bit less than what Aaron Swartz faced?
Yes, that point is true - it's easier to go from the stricter environment to the more open one - I guess that's basically just how entropy works. Note that I don't necessarily disagree with the article, I just wanted to offer some perspective on why I think the schemaless approach can often make sense, especially in how CouchDB handles it. If at some future point, the worlds of RDBMS and NoSQL fold into one DBMS handling all the use cases perfectly, I'm all for it - it's just that right now I'm still skeptical about going all schemaless on an RDBMS, since it's still a rather new feature, and the underlying system is very complex and has grown for decades.
MySQL/Postgres aren't difficult but they are more complex that MongoDB.

And in Agile you are taught to only focus on the short term and then move only when you need to. In which case picking the simpler database has merits.
Surge Pricing is illegal in Berlin, and probably other European countries. And I imagine the illegality of price gouging ("surge pricing") while also skirting taxi regulation will be expanded dramatically in the coming years, all across much of Europe and blue states.

Yes, you can profit when you find loopholes in regulations that your competitors can't take advantage of. Color me shocked.
Technology in Africa Weekly Catch-Up
> All other rents will rise as well, because all owners will see what everything else costs and continue to charge ridiculous amounts for their spaces.

Don't be absurd. Owners are already well aware of the fact that there are rich Google engineers beating a path to their door, and are glad to charge said engineers as much as they think they can get away with. Additional housing is competition, and if they affect prices they will cause them to fall, as various Google engineers will have an alternative to Mission-district Victorians and other existing housing stock.
> The advantages of a fixed schema are similar to the advantages of a static type system in programming

Yes, but I already have one of those in the form of a static type system. I dislike database schema for the same reason I dislike XML schema: it tends to enforce only the most trivial constraints, and means you duplicate part of your validation (because you still want validation in code for the things you can't check in the schema). It's just another moving part that can be a potential source of failures.
Run Your Research: On the Effectiveness of Lightweight Mechanization (2012)
I'm not sure why you think it's lower res. It looks about equivalent to me. The trees look a bit odd in Google maps, but the quality of the building windows and cars looks about the same.
There are always great offers on http://lowendbox.com/ - I'm very happy with the small KVM offers edis.at is offering.
Yeah, I had to hit f12 and disable the background with Firebug.
I love this[1] 'arrow of time documentary' if you are looking for something fun to watch.
https://www.youtube.com/watch?v=4BjGWLJNPcA
Congratulation on Linode

I stopped being a customer since migrating to DO but my needs were really small

But I think their strategy of keeping the price and increasing capabilities are good. Between $5 and $20 is a "big" difference for one person (still, it's a day's lunch), for a company it's nothing.

However, I would definitely go to Linode for CPU/IO intensive tasks. Amazon sucks at these (more benchmarks between the providers are of course welcome)
Plus, what happens when the power goes out and now I can't receive email?
Well by experimental feature the Node.js team means that the API to access clustering features isn't set in stone - not the stability of the code.
Ask HN: How popular is TypeScript outside of the Microsoft ecosystem?
How many people use it with Node.js, Ruby, Python, Java, etc? I'm sure CoffeeScript is more popular, but is that changing? How does the popularity compare with Dart (which it's exactly comparable)?
Obesity in Nauru
I think it depends on what you need to sync, but I've also had this problem and have found something that works for me.

I use Sublime Text for both development and quickly "jotting" things down. I keep 2 copies in my Dropbox, which is installed on all my computers, and have 1 for work, another for personal. Anytime I need to jot something down, it gets synced to all my computers regardless of whether I need it to or not. I don't have to spend time thinking about it. It may seem weird at first but it's become second nature for me.
How the word "entrepreneur" got too popular for its own good
The problem is that by turning "entrepreneur" into an aspirational catchall for everyone from Bill Gates to your next Uber driver, we've lost our ability to measure and understand the macro shifts taking place--and their policy implications.
IMO, this is the worst argument. There are multiple schema evolution tools for SQL, there's nothing stopping your team from changing the schema every week - plus, it's not hard, certainly less hard than having to maintain code that deals with multiple document schemas at once.
I've been asking a lot of people when MongoDB is actually the right tool for the job.

http://daemon.co.za/2014/04/when-is-mongodb-the-right-tool

I'm starting to form this idea of what constitutes an ideal use case for mongo in my head, and i'm trying to prove the model.

If I were to imagine some kind of "realtime" multiplayer game, like quake or something.

1. You have to have the state be shared between all the parties in a reasonable time.

2. The clients only need the data that is directly relating to the round they are in, so you have the concept of cold and hot data.

3. The data is all kind of ephemeral too, so that you don't specifically care about who was on what bouncy pad when, but you do want to know what the kill score/ratio is afterwards.

4. You have a couple of entities that have some kind of lightweight relationship to each other, which makes it just more complex than a key-value store like redis is really suitable for.

5. These entities are sort of a shared state, and thus get updated more often than new unrelated documents get added, and couchdb's ref-counting and append-only nature makes it really unsuited for constant updates of an existing record.

any feedback would be appreciated.
How can suicide become "more socially acceptable?" What does the delta consist of, between suicide being "not socially acceptable" and suicide being "socially acceptable?"

I've had no experience with anyone I know of committing suicide, but I am not seeing how to evaluate whether it is or isn't socially acceptable.
I think the underlying problem here is managerialism [1], which is mainly a cultural problem [2].

The way that one solves cultural problems is mainly by talking about them. If enough people are saying, "Hey, this prohibition thing doesn't work," and do it for long enough, then eventually the unquestioned cultural assumptions dissolve.

So my question for you is: why are you standing in the way of people doing something about it by being a jerk?

[1] http://en.wikipedia.org/wiki/Managerialism

[2] http://www.amazon.com/Confronting-Managerialism-Business-Eco...
Once in Hawaii, at a meeting of philosophers sitting around a table discussing reality, several days passed and Suzuki said nothing. And finally the chairman said, "You've been silent all this time. Would you say something about reality." And Suzuki didn't say anything. I think he may have looked up. Finally the man said, "Well, is this table real?" And Suzuki said, "Yes." And then the man said, "In what sense is it real?" And Suzuki said, "In every sense."
>I personally have found that in most cases, if a request is truly urgent, you will know it.

Why not just take care of a task ahead of time before it becomes an urgent matter? An ounce of prevention is worth a pound of cure and all.

If you think a task or request isn't required or should be modified then discuss it with the requester or at least let them know you can't completely the task.

Otherwise you mess with other people's workflows and are just one of those people who doesn't play nice with others.
... you should submit your 4th grade essay to Dau.mil. Apparently this is the level of research they are looking for.
That would be great, thanks. I suspected they were using d3, but based on how consistent some of their visualizations are with each other I suspect they have an in house library that they are using as well. Would be cool to hear from the source :)
Dropbox's Condoleezza Rice advocating for warrantless NSA surveillance
If you're the COO, and most of your compensation is in stock or bonuses related to the stock price, and the stock nearly triples during your reign (15.92 to 41.07)... you're going to get a big payout.

I also don't really buy that firing him cost this much, since much of it seems to have been a sunk cost. That stock was going to vest eventually whether he was fired or not, it just vested faster because he was fired.
I don't agree with the author. A to-do list is a way to reduce the cognitive burden of to-do ideas popping at the wrong time when you can do nothing about them and then forgetting about them when it's the right time to do them..

I agree that most of us (and I include myself in us) are incompetent at managing our to-dos though.

I think we need a better methodology than GTD to tackle to-do list.
This is not true.

Linode allow you to attach additional IPs to your Linode at $1/month, for example, I have one Linode which has 6 IPs attached for only $25/month. I still can't find a company has this kind of flexibility.
Seeing as San Francisco is already more dense than Brooklyn, I question that. However you could over 3 million people in San Francisco if you built up to Manhattan levels of density. That would be impressive.
Heh.

Actually, thank you to the previous poster. I didn't mind the criticism. His point -- "your existing site doesn't look good enough to convince my boss" -- is very valid. The new site looks a lot better and it's not done yet.

It does in fact scale pretty darn well, mostly due to the fact that it's connectionless, stateless, and opportunistic. If you're on a network with ten million people but are only talking to ten, you'll only be sending packets to/from ten.

The supernodes have to know about all ten million, but last I checked that wasn't very much memory... maybe a few gigs tops? So that's what, $20-$30/month per node? Or I could add the ability to put a real database under it and use SSD cloud nodes and handle billions of users with sub-10-ms lookup latency.

Of course if I get that many users that'll all be in the good problem to have category and I'll have plenty of money to scale out and if necessary improve the protocol/architecture. There are many directions I could explore: M:N supernodes with load balancing, various other sharding techniques, moving to beefier cloud providers, further decentralization in the protocol, all of the above, etc. I could set up big labs, run simulations, do all sorts of cool stuff. I've done enough so far to convince me that the problem of monstrously scaling this thing is very solvable. Just have to do the work.

I'm not making the crypto fungible. The protocol does have flags that could be used to indicate new algorithms if upgrading the crypto becomes necessary, but I have been an absolute simplicity nazi with this thing so far and will continue to be.
Not really. Actuarial escape velocity is a concept that emerges from the SENS proposals [0]. Next to nothing you do with your life has truly significant expected impact on your future longevity other than providing support and funding for SENS and SENS-like research aimed at repairing the root causes of all the big killer age-related conditions.

(Less significant here means a ten year swing in life expectancy. Exercise, not smoking, calorie restriction - these are things that can make 5-10 year expected differences. Everything else is pretty marginal if you exclude the obvious exogenous line items like risk of accident. But an improving implementation of SENS provides indefinite extension of healthy life out to the expected limits due to accident rates, which is somewhere in the 1000-5000 year range for present data).

The mainstream medical research community is largely focused on patching late stage manifestations of aging. Most work and funding goes towards either manipulating proximate causes rather than root causes, or trying to find ways to alter the operation of metabolism to make the disease process less terrible - but again without addressing causes. Until such time as the research community is overtaken by the "address root causes" disruption currently taking place, of which SENS is an exemplar, but by no means the only movement, then progress towards extended life and defeat of age-related disease will continue to be painfully expensive, slow, and marginal.

The trends in life extension achieved through medicine to date are all largely incidental, unintentional. Where aging itself as a collection of processes [1] has been slowed it wasn't because that was the deliberate intent. Again, because until very recently no-one has been trying to address aging itself rather than focusing on the nature of its outcomes. It is the same difference as that between working to reverse or prevent rust in metal structures versus working on repairing structural failures that occur due to that rust.

[0]: http://www.ncbi.nlm.nih.gov/pmc/articles/PMC423155/

[1]: http://sens.org/research/introduction-to-sens-research
Nice comment, however I doubt any informed gardener would want to emulate Iowa corn field topsoil, it probably has just slightly more biota in it than the Atacama desert at this point.
Heart disease is killing fewer people allowing more to reach an age where cancer becomes a major killer. Since cancer treatments have advanced the number of deaths due to cancer looks flat.
The Norwegian site Finn.no got 3D maps that looked exactly like this back in 2008. [0]

As the link explains, the technology originates from the Swedish air force, and was meant to guide missiles through urban landscapes. It was since commercialized for civilian uses by the company C3 Technologies.

This looks like it's exactly the same technology.

[0]: http://labs.finn.no/sesam-3d-map-3d-revolution-the-people/
Some Misconceptions About Startup Exits
OpenSSL Bug Hunt Needs Donations
Aesthetic and lifestyle minimalism are not the same thing.