skysight-inc/HackerNews huggingface dataset:
Ask HN: Why was the car driveable?
How is it possible a Tesla left for service or sales could be sitting overnight in a driveable state? The car is very powerful, the idea of someone hoping in with adrenaline pumping, they were in way over their head. Not an excuse.

The instant the car activates in the middle of the night, there should be alarms going off. It's a glorified motion detector and trip wire at this point, simple software monitoring. We know all the variables can be monitored over the onboard Ethernet so the prgram could reside any number of places.

I mean, if the Batmobile can do it in the latest movie, Tesla should be doing it in their car, right?
In the context of web applications, what do Haskell or Clojure bring to the table that makes them worth the learning curve?
> Rule 3. Fancy algorithms are slow when n is small, and n is usually small. Fancy algorithms have big constants. Until you know that n is frequently going to be big, don't get fancy. (Even if n does get big, use Rule 2 first.)

Thing is, I don't know; n is definitely small in our unit tests, but if it isn't guaranteed¹ to be small, I'd rather start the code off as something with O(decent) as opposed to O(whatever an array gets me). It's not clear to me if this is what Rob Pike means though: does simply using a hashtable when appropriate to avoid iterating through a list count as "fancy"?

When the ultimate bounds of n aren't certain, I'd rather start with a good O(...) algorithm, and then apply the "measure, and optimize."

¹and even then, if my "guarantee" is coming from something other than physics, I'm wary.
I know it's a little heavy weight, but there is already an open standard around this: http://www.hropenstandards.org/

They have a HR-JSON and HR-XML schema for HR docs..

Reinventing?
Sounds like you're senior to me. If you can quantify how you're the "go-to" guy, then you're in a position to ask for a raise.

To explain my stance vaguely, if you can make critical decisions about abstract concepts, then I'd consider you senior. For instance, I recently saw that some of my coworkers were using an HTML tag in a way that was technically correct, but in a situation where a different tag is more suitable based on the context of the page. This is something I've learned through my studies and experiences as a front-end dev, and as such, contributes in a small way to my "senior-ness".
For contracting work, I've had good success with Harvest:

http://www.getharvest.com/

Lets you track time by task, project, employee, and calculate rates and whatnot.

Incidentally, if you're tracking time for purposes other than billing clients, what the hell is wrong with you?
I think the trends the author is seeing may only be regional. Out here in Oklahoma and on some of my trips around the midwest, every little kid who sees my car knows the difference between a new base model Mustang and a Mustang GT and gets excited to hear a real 420HP V8. Lots of young guys I've met -- in college, through friends, in the military, etc. -- have also had their share of fast cars or tuners. A good number have even done a restoration or two.

As for the women, plenty of college girls and other young women notice what I'm driving and give me complements. A nice car definitely still gets attention from the ladies. Quite a few I've know even enjoy driving stick and like to go pretty fast.

I'll admit, young people may be more practical and economical with their vehicle purchase decisions, but car culture is still very alive and strong here.
Yea, I second what froaway said. 'Scripting' in Scala is quite easy and works like you would hope it would. Integration w/ the shell is quite nice and it's as concise as Python, Ruby et al and yet also typesafe. Win-win.

Also, I wouldn't worry too much about finding Scala programmers-- in my opinion, what you want to find rather is good programmers. And, good programmers can pick up Scala (or any other language) in short order.
For some reason I don't think those $50 billion are what is the main concern of the federal gov't
Capital controls are slowly but surely coming back, it seems.

We're basically in a state of surveillance of nearly all financial transactions.

This is, of course, always a state security goal. Computers make it a lot more scary to me though. Monitoring can be a lot more personal. More individuals can be watched than ever before, with records kept accessible for longer than ever, with better software for reporting than ever before. And it's never been easier to lose control of large quantities of information now that gigabytes can be copied in seconds.
I'm guessing we'll start seeing more competetion for similar services from Hong Kong, Singapore, and some of the newer Easter European banks with pretty innovative and low-cost financial services.

I'm not sure this bodes well for the American banking system in the long term; today's migrant workers are the parents of tomorrow's entrepreneurial children.
I remember how weird I felt in first year university taking frequentist based statistics. Unbeknownst to me, my statistics training in high school was completely Bayesian and when the university prof started talking about how we needed to sample a certain population set in order to come to an accurate conclusion I felt very uneasy with the whole mess.

I know both systems are useful and reasonable in their own sense, and often even equivalent, but I found the Bayesian way of thinking so much more intuitive than the frequentist way.
Or you just put a $100 bill in an envelope and put a stamp on it.
No, it IS bad and the complaint that 'people use it badly' is simply an excuse to cover for its deficiencies. In many ways, its deficiencies (which YAML/JSON do not have) are an incitement to use it badly, but that's far from the only problem with it.

I am not complaining about being forced to use bad schemas in enterprisey situations, either. That is merely the icing on the cake of the badness that is XML.

I am complaining simply because there is not one instance I have ever come across in my entire programming career (12 years now) where XML would have served me better than an alternative (assuming I had a choice). Zero.

For example:

>With XML I can do this:
>
><experience> <title>Manager</title> <company>Veridian Dynamics</company> <description> Responsible for doing all manner of things. </description> </experience>

Yes, you can, but so what? You can do that in YAML and JSON too. Furthermore, your YAML/JSON parser is 10x less complex, faster, less likely to have buffer overflow security issues and less likely to have memory leaks.

Furthermore, while my app that consumes this markup will probably have to treat <experience><title>Manager<company>Veridian</experience> as valid, because consuming badly formed XML is standard and expected (your product manager will probably treat not parsing it as a bug), my app won't EVER have to treat invalid JSON as valid.

>Of course, we could make it suck

Yes, and there's a 90% chance somebody will. Whereas with JSON and YAML the chances of it being made to suck are far lower, because so many of the unnecessary avenues which are used to make XML suck are closed off in YAML.
Ask HN: Am I the only one tired with their bullshit?
I am wondering if it is me, or if other people (genuinely interested in Entrepreneurship) are tired of (generally non-tech) people (usually business majors) who wrote articles about how to achieve success when they have themselves never achieved anything particular?

Am I the only tired with hearing the same "motivational crap" over and over, again and again.

Am I the only one sick of the vultures only attracted by the "fast-money" and who don't give a damn about real change and who are 10,000 feets away from reality?

Sorry for the rantings, but I really need to know if I have anger management issues or if the hacker community is really becoming more and more poisoned by those people.
How often do you visit your parents 2 states over, or your parents-in-law who live far away from any airport?

Sure, "kids these days" will soon grow up and figure out what they need to get to those places. But the answer might not be "Buy a minivan." It could just as well be "Use this app to rent a self-driving minivan."

Having 3 kids, of course, is a different problem, but a lot of it depends on where you live. I have a hunch that many "kids these days" would hate to live in the same boring suburbs that their parents raised them in. And who knows, maybe Americans will finally rediscover the courage to tell their kids to take the subway to soccer.
So we formally defined the schema in the repository -> https://github.com/jsonresume/resume-schema/blob/master/sche...

That part on the homepage is a documentation generator I made for any given schema, it's suppose to be more of a go to reference manual but I guess that is unclear on the homepage.

All the modules have to pass the validator which is based off the formal specification in the repository. I think that is what you mean and as far as JSON is concerned, will keep at it for a bit and see how far it can go, if it's impossible hopefully a new standard in a correct format will take off and use some of the same tooling that we have built.
It's probably a case of selection bias as well :) Most of my friends are the nerdy programmer types, so perhaps it's natural that we're not interested much in cars (although I feel that sentiment among my not-so-geeky friends as well).

I do have to object to your statement that EVs aren't practical yet; while I admit that they probably aren't great for urban environments, my dad has loved his Spark EV, and it's hard to beat the price after rebates. (To be fair, we also have a gas-powered car for longer trips, but it's rarely ever used for drives that the EV couldn't handle, and in those situations a rental might be more economical, anyway.)
> Nowadays serious industrial-strength languages are emerging that are grounded in theory and informed by practice.

This seems a bit overly optimistic, but it's nice to see this kind of positive attitude for a change instead of "Why invent yet another language?".

I am very excited about Swift and I have some respect for what Rust is trying to accomplish, but none of these languages have much foundation in category theory or the ambitious kind of type system that Haskell has been pioneering for a while. And the fact that Go is seeing some traction is a stark reminder that we still have ways to go.

Still, it's nice to see some of these concepts becoming mainstream (lambdas/closures, fold and functional iteration, phasing off inheritance based polymorphism, etc...).
https://raindrop.io/ looks pretty nice. Was discussed here https://news.ycombinator.com/item?id=7608302
Google Docs is down (in India at least)
Not Google drive. Open docs.google.com and boom
And delete the query string at the end of the URL ("?...").
TSA is not a waste. It's a business model (for some).
I remember my Calculus I and II text book always seemed to skip an important step.

1. Some Math

2. A therefore obviously B

3. Q.E.D.

It was always the "obviously" part were I was lost.

The proofs in my more math heavy CS classes (especially Automata) were always a lot clearer even though I thought the material was conceptually harder than calculus.
> everything but everything is character strings

Actually it's worse: they're byte streams. They don't have to be decodable as any encoding, can contain weird control characters, etc.
The camera filming itself in perpendicular mirror? Would we see an appreciable delay for each diminishing image, or what?
Quick-sort as Hungarian folk dance
Isn't this a good thing for Bitcoin?
We are a team of 4. 2 owners and 2 employees. Our employees are paid hourly. They punch in at 8AM and out at 5PM (give or take time, or overtime if needed). We need to track their punch time to pay them their hourly rate. We also need to track their task time to bill for the work they do. Sometimes they work on things that are internal and are not billed out. Price range isn't a major deal. We are flexible in that aspect. I am actually a programmer and could do this custom, but we have 0 time. We are extremely busy, just hired on a new employee to keep up with work and are looking for a solution ASAP. We use quickbooks for billing and payroll, so integration into that would be a plus but not necessary. If we can't find anything, I will plan on building it. Just looking for something to work NOW! Harvest is great, but doesn't do punch time. Thanks.
I find myself moving farther down the stack rather then picking up the "new hotness" framework etc. Right now I'm very interested in embedded / low level systems. Someone still needs to maintain and build the actual technology that these young'uns use. :P
Genetic Code of Synthetic Mycoplasma mycoides
This is a joke, right? Reliably earning $250k is not easy even in the tech industry (bonuses and stock options are not even remotely reliable and hence should never be factored into the affordability of a mortgage payment). But on top of that, now you have to marry a spouse also making $250k. You're saying you have to borderline be a gold digger.
Passengers flying to US may have to switch on mobile phones for security
And do what with it? How will they spend it locally? They can basically only spend the money with US merchants - that doesn't help them very much.
My first gig was at a start-up. They could only afford to pay someone for ~10 hours a week, which fit perfectly with my school schedule. When I left school, they offered me more hours, but I was adamant about working no more than 25 hours, and by that time they had seen how productive I was at just 10 hours a week. There were definitely some rough spots when they had tight deadlines, but for the most part, they scheduled things so they worked with my schedule.

My current gig I got through a personal connection. They were in desperate need of a senior level front-end dev, and I was just upfront with them from the start that I would only be interested in working 25 hours a week. It helps that they have a team of devs to rely on when I'm not there.

My advice: if you want to be part-time, either be an expert in your field, or find an early stage startup that can't afford a full-timer. This sounds kind of shitty, but it's hard to convince people who are ingrained in the 40 hour work week. Also, telling people you're a student helps. I've found that people look down upon me when I tell them I have no desire to work 40 hours, but if I tell them I'm a student, they're all for it.
Three years ago, smartphones were rare in Mexico. I had to go to a specialty dealer who unlocked AT&T iPhones to get mine.

This year, I've been shopping for phones again in Mexico. Every network and every shop is full of nothing but smartphones. Almost all monthly plans come with data. Accessory shops with cases and covers and headphones and stuff exist in every town.

Mexico's bitcoin infrastructure is ready to take over the money transfer business if the government and the banks make it hard or expensive to go through official channels. All it will take is enough expense to make it worth learning to use bitcoin. The network of small entrepreneurs that would do the actual cash exchange already exists: Mexico is a land of small shops and informal businesses.

Erecting arbitrary barriers is more likely than ever to create a black market.
Matt Rutledge launches his next venture: A Mediocre Corporation.
> failing nations pay the bills ... stop letting people take it out of the country

No it's not. You have it completely backwards!

Failing nations are delighted for the local currency to leave.

Failing countries won't let foreign currency in.
...or perhaps it's an astro-turfed propaganda campaign inspired by "scared straight" programs.</tinfoil-hat> But still, don't take everything posted on the internet at face value.
New relevant xkcd: http://xkcd.com/1390/
I think Machine Learning will become much more common place. It's a radically different approach.
As someone from a country with very different resumes, my suggestion would be to be more explicit about this being about US style resumes. If you want decent rendering, you need to focus on one style anyway (too much variation), so just be open about your scope and optimise the hell out of it, saving you a lot of i18n worries (names, addresses etc.).
Foreign banks operating in the US are still going to be subject to the same restrictions, but I'm surprised this isn't already handled by non-bank remittance services.

Here in Hong Kong where around 1 in 20 people is foreign domestic helper, there are are an enormous number of services competing for the remittance business [1].

[1] http://www.bbc.com/news/business-26284493
I recall reading that when Niko joined the Rust project, he kept uncovering places where the type system was unsound and was instrumental in making Rust type-safe. Can anyone confirm?
I'm over 30, and been working in the industry for ~6 years now, and I say don't worry. Yeah, there's segments of the software world that push out new frameworks and languages at a breakneck pace that nobody could keep up with. There's no reason why you need to know them to work, though. The vast majority of developers out there are working in time-tested languages and frameworks. C++, C#, and Java for most of the enterprise and big business world. Most of the web work that uses any other language is Perl and PHP. There are jobs out there in the latest cool stuff, but they're a small fraction of the overall market. I haven't really worked with that side of the industry, but I'd have to guess that any company there knows that they aren't going to find many people on the market that already know their stack, and so will be open to teaching you.

Don't worry about trying to keep up with the latest stuff. Do pick a language and framework, and go build something in it. Make it do something useful and solve somebody's problems. A proven ability to execute on a business idea is worth far, far more than knowing the latest languages and frameworks off the top of your head.
Do we have room for craft?
Encourages you to spend it locally instead, supporting the nation's economy.
Yes, sure. We are already commoditized. Capital is the commodity. Startup talent is a commodity. Ideas, of course, were a commodity since the very beginning. The stage is set, the only option is to play.
> Isomorphic JavaScript allows you to literally not repeat yourself. You write code to solve a problem and you never need to worry about that problem again.

If only that were true, but that's where my doubts are. You write:

> If you're sharing code, you just write a function to check the rules and call it in both places.

But you can only use that function if you can use Node on your front end. Most fronts today (native iOS apps, etc.) won't be able to reuse that function, and you'll have to reimplement it anyway.

I would only go with Node if I absolutely knew that incompatible front end won't be required for the project in foreseeable future—but I'd need to be a CTO to decide on that. Besides, what about when browsers get an additional runtime, with better tools than JavaScript? (Okay though, this one may not count as ‘foreseeable future’.)

I'd rather reimplement the function every time if I know I may need to reimplement it an unknown number of times. Perhaps in that case I'd try coming up with some language-agnostic specs instead so that validation function can be reimplemented on other platforms without breaking UX consistency.
dotted with $1.5M single family houses and $4,000/mo apartments

What about Hayward or East Palo Alto? Or Oakland? I thought there was still plenty of cheap land in the Bay Area, but people all want to live in the ritzy bits.
One aspect of the Bayesian/Frequentist "controversy" (which amongst working scientists isn't very controversial) is the supposedly subjective nature of probability under the Bayesian system.

I think this is mostly a conceptual error on the part of Bayesians: we should be treating the "degree of belief" in the Bayesian system as precisely that, a degree of belief, and nothing more. It is not a "probability", which I'm happy to leave with a frequentist definition.

That is, Bayes' theorem should read: p(h|e) = P(e|h)*p(h)/P(e)

where the lower-case "p"'s indicate plausibility (degree of belief) and the upper case "P"'s indicate probability as measured by frequency of occurrence.

Probabilities under this system are completely objective. Plausibilities are--naturally--subjective. As someone who advocates for an epistemology of a knowing subject (that is: there is no knowing without a subject that knows, and the central question of epistemology is how that subject knows) it is entirely natural that the degree of belief in a proposition should be subject-specific. After all, whose degree of belief is it?

This is not a failure of the Bayesian approach, but a virtue: it allows us to successfully navigate the many traditional paradoxes of subject-free theories of knowledge, which put "truth" outside of the realm of the knower and pursue a false goal (certainty) much like pre-scientific alchemists pursued the false goal of the philosopher's stone.
Israeli here, flying to Europe couple of times/year. They don't make you turn on all electronics in Ben Gurion, that's just not true; asked me to boot up my laptop once or twice (probably because it can be used as a case for explosives due to its size), but not cellphone or an iPod.

Maybe they do check Muslims more thoroughly, that would make sense. I never took any interest in it, so cannot confirm it. (In the Army, I would totally pay much more attention to Arabs than to other civilians, but that's so painfully obvious, right?)
letsfreckle.com/
While financial remittance regulation is held up as a save-the-children, anti-terrorist poster child, in reality it's primarily a political, surveillance and profiteering tool.

This move will directly benefit businesses such as Western Union, criticized by consumer protection groups for preying upon immigrants and other disempowered groups. (Western Union has an extremely long history of abusing and maintaining monopoly... see http://arstechnica.com/tech-policy/2011/05/how-the-robber-ba... )

For an impressively useful World Bank resource on typical remittance prices, see http://remittanceprices.worldbank.org/en
Do VCs have an age bias?
Not everyone in federal prison is a rapist/killer. Half are there on drug offenses.
>I've come to the conclusion, that science will never be able to even define consciousness, let alone explain it.

I think the real problem is that people don't really want consciousness defined. They want to keep it as this magical, special thing.
his was my opinion..and I was silenced as a result of it. I wish the progressives on HN were more about being open and free, rather than closed.
If I say something that anyone here even remotely disagrees with, I am down voted.
This is why people like me will stop coming here and eventually leave the HN community completely.

I will keep posting this until I get my point across.