skysight-inc/HackerNews huggingface dataset:
Perhaps lately. Prior to this past November, the stable release advertised on their site had been stuck on the same version for years, without even any point releases. And they use SourceForge for hosting.

The code quality may be excellent, but it just seemed to me that they were not too well organized, logistically, compared to other projects.
Why not make a big solar still thus: go to Saudi Arabia, dig pit near the ocean, pile up the fill next to the pit, let solar evaporation carry freshwater up to the top of the pile, store it on top so you have pressure?

There must be a reason why not make lots of these on the coast. If someone knew how to run the numbers I would be very curious.
How to steal money using a smartphone with NFC
Also, solar cells are not as efficient as direct sunlight evaporating the water to be condensed later.
In my experience, no design document, no matter how carefully drafted survives contact with the enemy^W^W an IDE. At best you can define interface boundaries between independently developed modules.

Edit: broken leftover line
Hehe, i was writing my post when you submitted this.
Well, yeah. The whole idea that you can somehow "save" on ops by doing X is just accruing technical debt, moving the point at which you will need ops into the future and also thus making it far more expensive when that time comes. It will be a fire that maybe only expensive outside (ops) consultants can put out. Imagine that: A fire that no one at the startup can put out. That's a lottery I don't want to play. If that doesn't scare people out of this kind of "we don't need ops anymore!" hooey, I feel like they deserve whatever comes their way down the line.
Flaw-finding Ruby on Rails bot steams past humans
The gameplay and tech behind the two game franchises is closely intertwined. The gameplay of Last of Us requires the high quality animation and cover systems built for Uncharted 1 and the melee combat system added with Uncharted 2. Now we see Uncharted 4 take some of the improvements to friend AI and dialog from Last of Us and push that forward.
I once got a $25 Starbucks giftcard for pulling an almost 48-hour epic coding session to fix some major issues right before a large trade show(we were blowing the 64 open file handle limit, so I completely rewrote our audio system to stream from the texture cache instead of individual files).

That's all the bonus/royalty/atta-boy I ever saw in my times in games. The 90/10 rule is in full effect in that industry where the top 10% make 90% of the profits.
The minimum wage for exempt employees in NYC is $675 per week, so for two people that's $70,200.

https://labor.ny.gov/legal/counsel/pdf/administrative-employ...

(If you take outside funding for your startup, that's going to be the minimum you're allowed to pay yourself, and statistically it's unlikely that your spouse is going to be making less than that.)
> However, to make a fair comparison you should also consider the toxic byproducts of uranium extraction and purification. Coal is not refined in anywhere near the same degree as reactor-grade uranium.

If I understand correctly, these waste products are liquid or solid that can be stored, rather than dispersed into the atmosphere like coal byproducts. (Of course, storage poses its own technical challenges, like warning people in fifty thousand years not to mess with them, and the Hanford site's current leakage problems.)
Yes I think it would still be a good idea to require expiry date for "immutable" content, just as a safety net if something is misconfigured somewhere etc - then when you fix a bug, you will know the precise time at which it will be gone for everyone (hopefully the expiry date was not set to 10 years).

However I wonder what is the typical cache lifetime of resources on current web. IIRC someone on HN posted like a week ago that from their study, it's rather short - stuff is evicted from cache quite rapidly if not used. So fast that getting a cache hit for jquery from CDN is quite unlikely very often.
A greater paradox is how does a decentralized currency, which relies on computational power for preservation, continue to protect itself from algorithmic advancement?

- With patents/copyright, the creators make the work publicly available with the expectation of protection.

- Without patents/copyright, the creators keep it private and can use the advantage to take over the network.
The Power of Design Thinking
Why do you find them expensive?

I've done thousands in my career. They don't take much time compared to actually writing the code, and adding an extra 5% of engineering time pays major dividends later without drastically reducing throughput.
It isn't a paradox it is just bad logic (as usual) by the developers of the 'core' version. These guys are actively working on taking away transaction fees from the miners yet they will always be fighting the fact that the miners ultimately dictate the network.

I don't think they are afraid of Chinese miners adopting this, I think they are afraid of everyone else competing with the Chinese miners and the network becoming more decentralized, which would mean they will have a more difficult time disrupting communication and understanding of the issues at hand. Not to mention it would mean more people they would have to pay to keep from increasing the block size and ultimately using the version from their github repository.
Moral theorizing is irrelevant. Trademark law is the only relevant factor here.

The legal question under US trademark law is whether a reasonable consumer is likely to be confused by the name and erroneously infer that some sort of relationship or endorsement exists between the two companies.

As Tesla is a rather obscure figure among the general public, my personal view is that average consumers will not be confused and the Nikola Motors name does not infringe Tesla Motors' trademark. However, that is far from clear-cut would be subject to endless dispute in court, probably with both sides producing survey and focus group results promoting their interpretation.
It's not made clear why they don't just add solar to the general grid and power the plants from whatever the grid is providing. Presumably that would be solar during the day, maybe some CSP after sunset, maybe some wind at night, but if they really need to burn some oil during the night then it's not the end of the world. Better than giving up because they can't figure out how to run the machinary from one particular power source.
The Hyperloop’s Underwhelming First Public Test
Exactly what I was wondering.
>This post concedes that code reviews are better for the more fluffy ends -- teamwork, openness, social recognition, but given their high costs, I'd rather achieve even these soft goals in other ways than to impede my team's delivery potential.

What techniques have you found effective for improving the soft goals in the context of software (genuinely curious)? Are we talking more conventional management/business concepts or something a bit more loosely defined?
Quebec introduces legislation forcing Uber drivers to buy or rent taxi permits
That's true, but I believe less relevant than most would think. Most of the "dynamic dispatching" people talk about could be similarly monomoprhized. The only real dynamic dispatch occurring in most programs is due to dynamic code loading (separate compilation from your post).
Please take a look at Transloadit[0], we offer a ton of features and have a good pricing model, that I believe will be excellent for your case, we'd be very happy to talk over it and offer you a good discount, please email me at abdel[@]transloadit.com

[0] http://transloadit.com/
Amen.

Another huge cost of code reviews is distraction. We've all seen the Paul Graham essay on maker's schedules vs. manager's schedules. We've all read the statistics on how much time is lost to interruptions. Code reviews are a massive interruption, done on a manager's schedule. Each code review is a distraction, and can take a significant time commitment, if it is to be a meaningful review.

A few years ago, I worked at a company with a strong emphasis on code reviews, and it turned into a waste of time when people couldn't afford to waste time. You'd have to do the review, but you really needed to get back to your development or bug-fixing because of the impending hard deadline, so there would be non-commital non-review reviews such as "looks good to me", or "I see no problems". While a good code review can be valuable, these perfunctory ones are a huge waste of time.

Finally, code reviews sometimes substitute for design review, which catches the most serious problems much earlier. At this same company, it drove me crazy that we always had time for code reviews, but never for design reviews.
I would check out Philosophy Bites, which is a podcast interviewing active research philosophers in 15-20 minutes about their topics.

http://www.philosophybites.com/

Check out Stanford Encyclopedia of Philosophy, which is free and edited by active research philosophers on pretty much every major topic and figure.

http://plato.stanford.edu/

Naming and Necessity by Kripke is about reference and the causal theory of reference, but it assume a decent amount (in case that is what you were asking for specifically).

The Very Short Introductions series have some really good booklets if you want quick ways to jump into a topic.

A few other books:

B Russell The Problems of Philosophy. OUP (dated, but a classic general introduction)

Simon Blackburn Think. Oxford (nice general introduction)

Tim Crane The Mechanical Mind. Penguin (Nice introduction to phil of mind)

A J Ayer Language, Truth, and Logic. Penguin (dated, but a classic)

D Hume Enquiries

T Kuhn The Structure of Scientific Revolutions. Univ of Chicago Press
Code reviews can easily become a tool for people with huge egos to prove their smartness. I get code review comments for grammar of my comments or very small code style preferences that Google's anal style guide can't enforce (yet).

I like code reviews, don't get me wrong. But there should be a way to respond with "you just shut up, you're only trying to make yourself look smart".

It's all because higher up people mostly look at code review conversations this is happening. The other day I asked my peer how do I write this code? A or B? He said I don't care, A seems fine. Then in code review he commented it should be done in B way.

It's all politics.
Free Guide: How to Get Massive Traffic from Pinterest to Your Blog
Where Will Halliburton and Baker Hughes Go from Here?
The single biggest problem with Austin is the VC situation. AV became a "growth" fund, and nothing has really replaced it.

When Seattle has a better VC community than your city does, it is a problem. Without VC, Austin remains a great place for the engineering offices of tech companies from elsewhere, but until there are more angels and VCs in Austin, probably not the best place to start a company.
I have a long-term experiment to implement KVM in Rust. Adding union support to Rust was the first step: https://github.com/rust-lang/rfcs/pull/1444
> The government did issue you license plates specifically to be able to track you.

They issued the plate so that when something happens involving a car, they can look at that car and figure out who the owner is.

That's quite different from tracking. If you have enough license plate readers all over the city, you can get a pretty good picture of all the movements I make. And store them for long periods of time.

License plates were issued to identify the owner of a car. Not to comprehensibly track the movement of all car owners and be able to look up every place I went to in the last year or longer.
Plenty of projects, even greenfield ones, aren't checked into source control.

I really and truly did not know this still happens. Hell, even on throwaway/PoC stuff for which I am the sole developer, and code that stands a good chance of never seeing the light of day, I start with git init. 'cuz the probability that I'm going to wish later that it was in source control outweighs the very minor cost of putting it in there. For an organization that produces software that others will later use, I'm at a loss to explain it other than inertia.
Our corporate taxes are the highest in the industrialized world, so yes, lowering them would lower the incentive to move.
"now you have to buy" I fail to see why. Do they also have to "secure" a handle in every social media/service/website/platform that allows registration? An email account in every provider? Register their company in every country in the world?
> the hard problem of consciousness cannot be solved via the scientific method

Then why are you arguing about the choices of a nominally scientific institution? If you want to practice mysticism, you're free to do so, but it's strange to argue that academic institutions (which are, ideally, based in fact) should do the same.

> consciousness, the experience of qualia, is not externally observable.

Unless you believe in otherworldly mystical forces producing consciousness, we have neuroscience. There's no reason, in principle, that the behavior of the brain should not be entirely observable.
Darn 16.0 upgrade insisted on rebooting my Windows.

Should not be necessary in 2016
Hardly any one gives a shit about code quality, except the developers that have to maintain it afterwards.

Saying that, poor code quality has been a real incentive for me to improve my own code. When I eventually work out what something is doing and see how much simpler it could be i try to redo it in a way that will be a lot more understandable to the next person. If I visit my own code a month or two later and don't immediately understand it, its time to refactor it. At the end of the day I prefer writing code to debugging it, so the less time I have to spend trying to understand code, the less time I spend debugging.
http://www.naughtydog.com/docs/Naughty-Dog-GDC08-Adventures-...
I work on a team with the same size as yours. Although we do not all sit in the same room, we still do code reviews. Since we are small we are not the most critical on style.

I am a big believer in code reviews especially starting early with a small team. This would set the culture from the beginning because it is harder to bring that in later.
Is there more context around what exactly he's getting at? In games we use matrix inverses all the time(and since they're usually a specialized affine transform there's cheap shortcuts to calculate them) for stiff like hit detection or animation.
“Public software” versus “open source”
Maybe I'm an arrogant XP-ist, but to me this sounds like a good step on the way to pair programming.
I believe it's the percentage of the total city population that are both 25-34 and have a degree. Not the percentage of 25-34 year-olds with a degree.
I don't get your objection here. Not only does high-performance mode eliminate OS-level confounders that would otherwise render consumption deltas highly questionable, it does so in a way that produces worst-case results.

What exactly are you complaining about?
We write those on my team. They usually end up only faintly resembling what actually gets shipped. No matter how much agreement there is beforehand, as soon as people see working software they change their minds. The best thing is to plan for and expect change, not try to mitigate its manifesting.
Bold going away from YouTube.. best of success
That's the same link
As several other commenters have pointed out, code reviews are not a silver bullet. It is widely known that there is no silver bullet.

That said, if your goal is to make a quality product, you shouldn't have to choose between code reviews and continuous integration. You shouldn't have to choose between code reviews and code coverage, or manual QA processes. These are all widely regarded as best practices and if implemented "correctly" and appropriately to the team their combination forms a virtuous cycle for code health and team culture.
Sometime ago, there was an article talking about symbiotic process of desalination. Water would be drawn from the ocean, go into a data center for data center cooling and go to a power plant for steam powered turbines and then go to a water desalination plant because it is easy for steam to be converted to water. Isn't that a better setup?
Literally the only part that does anything is:

mv $vflag $iflag $1 ${1%\.*}.$ext
You can often have 100% test coverage and critical change code reviews, for about same cost
as doing code reviews for each commit.
Movila (plura: movile) means mound in romanian
I'd also be interested in this too if possible, email is {hn username}1@gmail
I suppose you should've used some yourself.
> though everyone I've talked to seems to think it's nuts.

gee, I guess everyone else is just wrong.
Yes, products that infringe a US patent can be seized by US customs. (Cisco is trying to do this to Arista right now.)
That sounds like a culture problem. You don't really want people who are out to prove how smart they are, versus people that are trying to help the other engineers they work with get better.
This was an interesting read for me, but I'm struggling to understand, from a design/organizational perspective, why solving the expression problem is a good thing.

If I don't try to solve the expression problem, I'm left with two common [OOP] implementation approaches:

1. A file for each type, within which all operations are also defined for that type.

2. A file for each type (POD), and a file for each operation which contains implementations for all types.

With either implementation, I achieve a good deal of consistency. The questions of "where should I put this new code", "what is the responsibility of this file", or "where could I find the implementation of operator <x> on type <y> within the code repository" are easily answered.

Solutions to the expression problem appear to mix these two approaches. The result seems to be much more loosely structured code. If I want to find the definition of ToString for type Constant, where do I look? It could either be in `src/types/Constant.code` or `src/operations/ToString.code` within my code repository. And as a result, it's no longer obvious what the full responsibilities of any file are within a structured repository without skimming the source.

I've heard some brief discussion of extending libraries with both types and operators - for example, adding a new image format to an image processing library and also adding a new operation. But at that point, doesn't your new code belong in the library (where you can implement it using approach 1 or 2), rather than in application code?
Not sure how to formalize but the team's I've worked on have generally negotiated mutual respect, openness, and teamwork by collaborating on the things of greater import -- the architecture, domain conceptualization, etc. And peer code reviews in some cases tend to work against these goals--because you tend to be down in the weeds of LOC, bike-shedding, arguing over the equivalents of tabbing and spacing or whether a line could be more functionally expressed, e.g....
This article hits an important point. I share an office with a mortgage company (weird, I know). It's amazing how draconian all the various mortgage systems and processes are. Instead of focusing on shiny new ways to make the customer side of borrowing easier, I'm betting there is significantly more money in selling picks and axes to the companies originating, buying, and servicing those loans.
On top of that you as a developer would have to understand what's happening and that it's happening at all. Might be not easy as we have a habit on clearing our cache all too often :)
Windows handles zip files horribly.

The time to extract a 100MB zip in windows explorer is 4-6minutes (if not more). Compare this to ~30seconds in 7zip.
London in Slomo with innovative selfie concept
In Oracle V. Google, a Nerd Subculture Is on Trial
Agree with much of first paragraph; will also point out that Finland (for instance) adds in

-- time to run around every hour for littler kids

-- hearty lunch cooked from scratch at school every day

-- social services that ensure your family has health care no matter the parental job situation

-- a school social worker and psychologist who will help you and your family.

Examples: http://www.theguardian.com/education/2011/nov/21/finland-edu...
http://www.theatlantic.com/education/archive/2015/10/the-joy...
The point of specifications is to standardize certain parts of a system where it interfaces with other systems using the same spec. This looks like it is supposed to pass information from a user interface to a payment system. Specifying the entire system would defeat the point of the specification.
Yeah I noticed that :) Is this a Simpsons reference? Can't quite place it.
The picture above looks like it's reactive armor, which is slightly different. There are multiple versions around, but the core idea is to sandwich explosives between metal plates in such a way that a round striking the assembly triggers the explosive, which drives the plates tangent to the round in a way that can disable it.
Simply put, absolutely the first thing one does after getting rich is preventing others from getting rich.

Rich people are not comfortable with the fact that it should easy for others to get rich, how useful would their current position be, if it were?
I've had a lot of success scraping websites with Capybara [1]. It's intended for writing acceptance tests of web apps, but it works remarkably well for scraping websites. It's written in Ruby, but the DSL it provides for interacting with web pages should be pretty understandable to anybody who's programmed before. It also supports multiple browsers, which means you can tradeoff along these axes:

- Headless vs. Not
- JS support vs. Not

I put a repo together with a sample script [2] for scraping leads off of a website which I will not name, but whose name rhymes with 'help'. It uses the PhantomJS browser for headless JS support. It also includes a Vagrantfile so you can avoid installing all the dependencies on your local machine.

[1]: https://github.com/jnicklas/capybara

[2]: https://github.com/toasterlovin/scraping-yalp
I don't know what you mean by "fully exploit", and maybe there are other, nicer, solutions, but object algebras were specifically designed for Java/C# type systems. The entire idea is predicated on that:

This paper presents a new solution to the expression problem that works in OO languages with simple generics (including Java or C#). A key novelty of this solution is that advanced typing features, including F-bounded quantification, wildcards and variance annotations, are not needed.
Looks good for the future of Methane Hydrate, of which undersea deposits could provide 6 centuries of power for our planet. Methane Hydrate is natural gas in a frozen water matrix.
We're happy to change the title to a more accurate one, or back to the original if it's best. But we need user help to figure these things out—it's impossible to study all the articles well enough to get the nuances right.
Screw the Rich (Here’s How)
Note the "default risk" part of that. I had a credit card that was at a very reasonable interest rate, then due to a series of unfortunate events, I missed a payment.

The interest rate immediately shot up to >25%, and I was told it wouldn't come down for more than a year.
Google for Boaty McBoatFace
Xey McXface is a canary for detecting naming contests within an organization.