skysight-inc/HackerNews huggingface dataset:
It sounds high to me too and I'm was on the team that rebuilt the login system. From what I know about it - we knew how much it cost us[0] and didn't have the support and maintenance contract figured out yet so we reported out 4 to build and no more than 4 to maintain and the number has kind of stuck.

I would say that I (very naively) thought that it would be easy peasy to rebuild all of healthcare.gov. I was wrong. There are all sorts things that make it much harder than you'd expect in a private sector environment.

I do think that there are probably ways to get this cost even cheaper - however, from a software profiling perspective, moving it down an order of magnitude or two is a huge win and that it's a pretty clear choice between further optimization compared to an order of magnitude change on a VA, immigration, or other system.

[0] I'm not actually sure how exact this number is either - lots of help required from people from all different contracts - so this is an upper bound estimate
Now that opiates can be cloned, will cocaine and ephedrine (for methamphetamine) be far behind?
Programs and Probability
We already do that. (See LoanPath in the compiler.) It's not a problem of reasoning about the structure of data--it's a problem of defining a notion of "overlapping control flow regions" that is simultaneously intuitive to the programmer, easy to compute, sound, and satisfies the ordering constraints we need (well-defined GLB, LUB, and partial order).
http://hentenaar.com/dont-learn-c-the-wrong-way
Isn't everyone who works for the government somehow serving the public? I'll make sure I thank my local DMV clerk for doing their "tour of duty" next time I'm there.
If you want to say that you're paying for access, that Apple can charge what they like, and that 30% is good value for the money for that access, fine. I disagree, but I respect that argument.

But the person above was comparing Apple's 30% to retail's 50%, which is a bad comparison because retail's cut is largely based on the actual costs of selling.
So basically it's more "mercenary" than performing a "tour of duty" to serve your country.
Peak App Care
This is true. What is a project but a collection of small steps? One small, perhaps one hour, of contribution a day for a year adds up to hundreds of hours.
That doesn't make any sense, considering Android also has the same 30%, but makes less.
There's literally millions of pending green card applications. You don't think good IT would help?

On a much smaller scale, I still remember the thrill of renewing my vehicle registration online, as compared to the slow, slow, slow DMV.
I agree: I have just started using Redux and the new 1.0 API and documentation are great.

However, I am very curious about the long-term* future of Redux now that FB's Relay has landed...

(*) long-term in JavaScript-parlance, meaning more than 2 months ;-)
18F also has a big office in SF (near Civic Center) and accommodates remote work, which is awesome.
I accept that there is a difference between "living off-the-grid" and "living in an off-the-grid house". But don't try to claim that this article is only about the first. Because I see several references to living off the grid in the article too, including in the very title it's self.

"Living Off the Grid Under the Sun"

"I am not so sure about the environmental benefits of living completely off the grid."

"I hope you enjoyed reading some of my thoughts and rantings about living off the grid in the high desert of California"

I regret starting this thread now. I actually think what you've done is really cool and would like to do it myself. I just got hung up on the terminology.
Comcast may challenge YouTube and Facebook with new on demand service
I think it's overreaching to say very little.

It's certainly true that the Rust compiler does quite a lot of analysis (more than Go), e.g. non-trivial type inference and borrow checking. In fact, a no-op build of libcore takes 12s for me, with 5s in type checking, 0.8s in borrow checking and less than 3s interacting with LLVM (~1s of which are LLVM actually running). Turning on optimisations pushes the LLVM time out to 4s. Similarly, libstd takes 8s to build without optimisations and LLVM only runs for 1.5s (type checking itself is about the same).

(The plan to make the compiler more parallel and more incremental improve these parts without affecting the quality of the generated code at all.)
The Ultimate List of Monthly Blogger Income Reports
Coding in AdTech – ES6 AND BEYOND – PART 1
> Now, HTTPS everywhere is a dubious project, sorry Konklone

Well, I like it. =)
Yes, #[inline] works across crates
Honestly, everytime I hear about the latest new-and-shiny that car manufacturers try to put in new cars (such as stop-start, keyless ignition) I can't help but roll my eyes at the inevitable fail that this is going to bring. Sure these knick-knacks might look cool now, but what happens eight years down the line, when your electric system goes belly up in middle of the highway or at a traffic signal?
VW is one of the worst offenders in this regard. They are quick to implement useless features without giving any regard to reliability or the idea of graceful failure. The greatest achievement of VW marketing has been in perpetuating the myth about the infallibility of German Engineering. German cars seem to have some of the worst electrical problems which is at least in part due to all the electric and electronic equipment they cram into their cars. I would put greater confidence in the reliability of Japanese or even Korean engineering over them (although even the usually conservative Japs have been tempted to follow these fads of late). One less button on the dash of your bland Toyota, means one less thing that is going to break five years down the line.
Birth interventions in general tend to skew toward unnecessary and dangerous.

Unnecessary interventions due to overly zealous electronic monitoring of "normal numbers", perverse financial incentives to turn rooms over quickly, and callous prioritization of personal time (by some not all) doctors make American hospital birth pretty terrifying to me.
No, my anecdote is more about a data point (well, three actually) indicating we don't really know how many ways there are to break into these cars, and that manufacturers are playing dumb, hence me not being surprised at the news that another one was found.

If really the problem was relatively trivial, VW should have warned me on how to avoid it, and they didn't. It can't be a simple amplifier: it's not just proximity, you actually have to press a button on the dongle to open a door, so whatever they were doing, it wasn't just repeating an existing signal; and as I said, I can tell you that making sure the car is locked has become a nightly ritual.
Sadly, Facebook's interface is badly done. Here's how.

(1) Go to the "People" tab [1]

(2) Click the "+" Icon on the top right [2]

(3) Add the phone number you want to message. [3]

[Reference Images]

[1] https://scontent.fsnc1-1.fna.fbcdn.net/hphotos-xfa1/t39.2229...

[2] https://scontent.fsnc1-1.fna.fbcdn.net/hphotos-xap1/v/t1.0-9...

[3] https://scontent.fsnc1-1.fna.fbcdn.net/hphotos-xft1/v/t1.0-9...
I have a Stennis Space Center (where this is done) coffee cup on my desk. Neat place if you're ever in New Orleans and have some time to kill.
Must Watch– (MASH UP) Bad Blood X Elastic Heart
RustCamp (2015) talks
It is an explicit goal to create lasting Digital Service teams in every federal agency specifically to ensure longer projects (those that actually involve (re)building something) have long-term support. Generally the short-term engagements USDS has are either to help agencies put a fire out, or to provide recommendations that the agency can then choose to implement with their own people.
Does anybody remember I Want Sandy? That was the first product of this type that really worked well for me.
I don't think a high traffic spot could ever cause an issue with this, unless each person tried to start your car. I believe this is referring to the immobilizer chip in the key that allows turning the key to start the engine. Incidentally, this is probably the chip that means that if you lose your key, you can't just get a new one cut, you need to get a new chip too.
I've met a lot of the U.S. Digital Service people and it is an amazing organization. I had a list of concerns (how they work with contractors already in place, how things would evolve with a new administration, whether they would get sucked into long term staffing at agencies, etc) and they had addressed all of them.

There are a few negative things as overhang from the rest of government (requirement for citizenship: so many of the great people I know are non citizens, even if many have green cards; drug testing, which doesn't really serve a meaningful purpose), but those are the reality, and don't diminish the value of the program in any way.

I would strongly recommend looking into USDS to anyone who who wants to make a difference in tech. It is a great place to go in the middle of a longer career at a post IPO company like Google/FB, or are between projects.
There is an official book: https://doc.rust-lang.org/stable/book/
That's why there are multiple stories. So someone reading can see the whole range of women's experience in technology. I'm sure there will be some good, some bad.
What do you guys think the online video ecosystem will look like in the next 5-10 years?
PG context of a startup is a company that has the potential to make it into a leading stock market index. Anything else is considered a "life style" business and not within YC or most other VC's scope of interest for funding.
It's a measure of the compiler's quality, and also of the language specification complexity.
Good point. They could do the first building for the community, only displacing a few families. Then once they move in, go full blast on the rest.

That would delay the project.
> I find the counter intuitive part of integration testing is that step 4 ends up being where most of the work is required and far too many people just don't do it because they feel it's not a worthwhile investment.

That's all I'm saying: tenable, but difficult (read: expensive). Frankly, I'm not convinced it is a worthwhile investment. Hence, my interest in how others have approached a similar problem.

Hitch looks pretty nifty, but I'm not sold on the yml/jinja2 approach. I grew to loathe Cucumber, and this approach seems similar. If you can't convince your non-technical staff to write tests in this language (which, in my experience, you can't), then you're better off writing the honest-to-god code that programmers are comfortable with (and can more easily modularize and refactor). YMMV I suppose!
There's an O'Reilly book in the works: http://www.amazon.com/Programming-Rust-Jim-Blandy/dp/1491927...

And The Rust Programming Language (https://doc.rust-lang.org/book) is on its way to paper publication.

The newly minted Rustonomicon (https://doc.rust-lang.org/nightly/nomicon/) that covers deeper aspects of Rust is hopefully destined for the same.
I really wanted to work for the digital service and my experience applying was horrendous. The recruiter scheduled an appointment to call me and didn't at the scheduled time. She followed up weeks later and I finally got my phone screen. Phone interview went well, she said we would schedule another interview. The followup from her didn't happen until another month later. Then I had a technical interview where the interviewer talked over me and asked whether I would use a list or an array for a particular data structure, to which I replied I use Ruby & Python so I don't know what you're asking because it would be a question of semantics, to which he finally clarified he meant a linked list and chided me for not "knowing the difference between the properties of a linked list and an array." How can you expect me to know the difference between two data structures if you're using unclear shorthand to refer to one of them? And the interviewer was an ex-Google engineer so I imagine he had some familiarity with Python (where a "List" is what many languages refer to as an array) since it's an official Google language.

And then of course I didn't get the job (and no feedback on why). The whole thing was maddening, took 3 months total just to get railroaded by an aggressive and imprecise technical interviewer. It sounds like great work though, wish them the best of luck. Wish I could work on their projects.
Kaspersky Lab Statement on Reuters Article
Previously: https://news.ycombinator.com/item?id=10045496
I'm not a C programmer by any means - and the languages I've dealt with don't have signed/unsigned. So I don't fully understand the merits and drawbacks of them.

However I know enough to question this:

>The default int and float types have been removed, as have type modifier like short, long, signed, unsigned.

If the goal is this:

>C2 aims to be used for problems where currently C would be used. So low-level programs, like bootloaders, kernels, drivers and system-level tooling.

It is my understanding that signed/unsigned is exactly the type of concern you have when dealing with low-level, embedded, or binary code. eg. Bit masking, bit shifting, raw memory

So I'm a bit confused. The removal of them seems a bit contrary to the domain goal of the language.
I dream of a world where everything is UTC, UTF-8, and metric.
You also have to move for a little while, right?

Overall, it doesn't sound like you get strung out to dry in any particular way. Seems like it's mostly a "sacrifice" in the sense of putting your ordinary professional opportunities on pause for a little bit- although if the program becomes highly reputable, it could actually be good for you professionally.
>> Last fall, prodded by Gov. Jerry Brown’s administration, the California Legislature passed a sweeping groundwater law, taking California from having the least regulated groundwater in the country to being a model.

Unfortunately by the time the law envisions the new rules being fully implemented — 2040 — aquifers across the state are likely to be permanently damaged or destroyed by over-pumping.
> It's really not fair to lump all of government in with the NSA.

Does the US Digital Service hire people who strictly refuse to assist in any way with any of the operations of the NSA, CIA, FBI, DHS, DEA, or any other oppressive agency?

If so, I'd reconsider, but I don't think they would hire me under those terms. And if they did, they wouldn't appreciate me saying "Fuck off!" if they tried to assign me to one of the projects to prop up one of these agencies?
Well, I have full faith humans can adapt. We just haven't needed to, yet, except with e.g. slower memory latency reduction vs cpu speedup.
Aurous – A BitTorrent Powered Music Player
Your forgetting the costs of the FS pension
I'm not familiar with the current state of physical security exploitation, but I get the sense that it would take more than 30 minutes and pushing the button on a black box someone built for me to compromise. Unlike this.

The issue with electronic exploitation is that the know-how component is relatively trivially automated. Script kiddies, etc.

If I bought an $80k Porche, I'd be bit miffed that it could be stolen from a parking lot in the time it took me to have a sit-down lunch.
Thanks for the proposals.

How would you make your first variant, work with pattern matching?

I like the second variant better, because it seems to work with pattern matching. It would as well have to work without type declarations, letting Haskell infer the types.

But all in all I prefer the way function definition is implemented now. The record issue is more of a trouble - for it Frege actually has some improvements.
I'm afraid Sam Altman could be the sign of rot setting into YCombinator.

Remember Sam described Ellen Pao as doing a good job when in fact she did a terrible job and had to resign from Reddit.

Now he wants developers to go on a "tour of duty"? Makes a mockery of combat veterans who come back with horrific injuries and mental scars.
They could hire this company:

http://www.theguardian.com/world/2015/apr/30/chinese-constru...

It was here in HN a while ago.
Same market as Red/ARRI at first. But I haven't thought about it since I think it's a rather daunting task (CMOS).

Each has weaknesses. For example, Red's build quality isn't all that great and their lack of awareness for what cameramen need on set is lacking. ARRI has a price issue, as well as resolution and raw left to be desired. Especially their AMIRA camera, which could be a first target for a startup - a good documentary camera. Blackmagic is usually all talk - their software is abysmal and hardware has a cheap taste to it. Sony lives in their own world (their professional market division is a bit out of touch with reality).

In my opinion, there's a great space to be filled (at first, but there are others) in documentary and/or ENG camera space. Making a good ENG camera paired with a lightweight version of codex at a reasonable price would be a killer combo. Two main (of many) issues are CMOS design and production and either custom lens manufacturing or sourcing those.

I am not even sure where one would begin to implement their own CMOS. Everything silicon production seems like alien, otherworldly, tech to me once you start thinking of production. Design is on another area51 level as well.
Absolutely - I tried it! I think the ability to interact with a service in a manner reserved for other humans makes it a more intimate (and arguably natural) experience.

The main motivation behind Myra is that it maintains conversational context - so you can ask questions and follow up with it without leaving that context.

Eg: "Find me a restaurant" and "Show me what people say about it".

Just like you would when speaking to a person - and one of the things that most (all?) other AI assistants out there lack.
Worse, the paper says the cipher has only 56 bits of internal state (made me think of DES, but that isn't at play here)

Even worse, they get it down to 48 bits.
Market for the people USDS is hiring generally is higher than that in cash, plus better benefits, plus 50-100k/yr in equity. There is some sacrifice, but not an insurmountable one.
Ah, but did they control for whether the music had vocals or spoken words in it?

My personal theory is that humans are wired to be interrupted by words spoken by other people. Even when you realize they aren't talking to you, a portion of your brain is stuck on monitoring duty.
Why isn't your speed and talent being used for something more useful.
Do you get 2 years worth of pension? ie 2 40ths (or whatever the accrual rate is )
Be careful with your ears, please. With in-ear headphones, it's extremely easy to have 80+dB over a large amount of contiguous hours, which is Not Good For Your Ears™. I have tinnitus, you really don't want tinnitus. And i thought i was one of the careful ones (i.e., i almost always use earplugs at concerts and try to avoid loud bars)! In fact, much as i like bars, these days i find myself wondering if i should (1) not go to bars on account of the loud music, (2) go but wear earplugs (i heartily recommend the Etymotic range), but therefore be regarded as a weird old fogey, (3) suck it up and have regrets the same evening lying in bed listening to the worsened tinnitus...

http://www.nidcd.nih.gov/health/hearing/pages/noise.aspx
http://www.soundadvice.info/thewholestory/san1.htm
I know what a honeypot is. And I know what a cast is. Can you provide more on what I am actually viewing though? Not clear.
By having you perform a small fix, someone else didn't have to work on that fix, and that person got to fix something else.
If Avast is affected by this and the file is a critical system file, real damage can be done to user's systems. Mcafee had this problem five years ago.
Edward says this himself. Practically "Please be careful with my input". That said, his input is not nonsense. No one should take any writing at face value. Always ponder the message, the consequences and if there's an even better way.

Edward Snowden: [...] Just because I say it, doesn't mean it's gospel. I can be wrong about an incredible amount of things. Nobody should trust me. Nobody should grant any sort of outsized weight to what I say.
I'm leaning this way now myself, after previously believing that co-founders were essential and prior to that being dubious about their value.

Two things I've seen kill startups are bad cofounder relationships, and Venture Capitalists. Almost 50-50, with VCs in the lead because they cause a lot of the bad co-founder relationships.

The person you are likely to make your cofounder should probably be your first employee. Make them significant, give them a VP title or whatever, get feedback from them, pay them in equity. But don't let them be in a position where leaving or failing to pull their weight would doom the company.

Finding a good cofounder is nearly impossible for many people for many reasons. If you are a group of people who know each other already and want to start a company-- great.

But cofounder dating is a bad, bad idea. Couples live together for years before getting married, yet co founders want to "get married" within days or months? Even if you choose well on a number of areas, you simply can't know your cofounder well enough.
Exactly. So how many vulnerable cars are on the roads of the world right now because the UK High Court wanted to "protect consumers". It seems insane. A temporary injunction, sure. But two years (actually three since the original vulnerability report) isn't remotely acceptable.

And getting back to the original point: I'd want to see some coverage of how this disaster happened in the UK courts.
At the same time I would say, don't dismiss the benefits of having a cofounder. It's easier to explore new territory as a team then it is alone. Just the psychological boost that comes with camaraderie is well worth it.
Thanks for the kind words. Yes, we have made progress. Yes, there are still quirks. Yes, there is more to do. Come help!

As a YC alum, while I find some strong similarities between Digital Service and a small growing startup, there are indeed some additional hoops that we go through as a part of the US government and that's part of the tradeoff you get for being able to help government agencies that have huge impact!
I'm basing it off the observation that newer cars are essentially never stolen, while popular older cars are stolen in vast numbers.

Whatever the reason, stealing newer cars is harder. That increased difficulty translates into decreased theft rates.
Why do you put it that way? Everyone serving in military takes home a paycheck, but that doesn't make them mercinaries.

The top tech talent that we aim to attract to USDS often can make far more than these salaries staying in the private sector, so appealing to a sense of civic duty and offering short-term engagements is what we have to do to recruit.