skysight-inc/HackerNews huggingface dataset:
Right, but your statement was about NP hardness in general.
Actually, very few workflows at film studios rely on batch renders these days. Far more important to artist productivity are interactive workflows - being able to work in context at scale in and between DCC's, and therefore load speed was actually a huge design consideration for usd, and integration of USD's gl imaging system, Hydra Stream, into workflows, has been a game changer for many interactive workflows. Check out the paragraph "Maximize artistic iteration by minimizing latency" on the USD website's front page... or better yet, actually try out USD (usdview) with a modern allocator like jemalloc (since both ingestion and imaging in usd extensively leverage multithreading).
Were the movie and TV show named after the project for plausible deniability? Ironically, this is something the TV show itself suggested.

https://youtu.be/gT-Vf_x4Dc4
Doesn't matter. They have an established history and have been making cars for almost a hundred years. I drive a Mazda now. If it's looking like drive-by-wire technology is too dangerous, I'll just keep driving that and hope my cruise control doesn't decide to cause an accident.
There are ways to deliver on time & budget but most developers are not going to like it neither are their "clients".

Use the frameworks exactly as they are intended, don't try to invent new solutions that aren't native to the framework.

Anything that takes you outside the beaten path in development is going to be a potentially infinite black box.

In other words, a lot of software engineering can't be put in timeboxes because it's actually R&D more than it's development and where each little step forward can add a potentially infinite amount of new tasks to be done or problems to be solved. Add to that the constant need to update, upgrade, improve, re-design and you know it's just not doable.

So the primary problem IMO is that we think about a lot of development as if it's something that can be put in boxes. Some can of course and the better and more solid the team becomes to better they are but the teams who struggle are mostly struggling because the expectations for what they are actually doing (inventing problem-solving) isn't matching up with what they are being paid to do (build)
Stupid question but don't insurance companies require access to this data? Seems odd.
And TFA's suggestion (use our magical time tracking software) isn't going to solve that problem, either.
I understand their benefits. But why refuse to support standards as well? I don't think Apple is short on resources.
I have a selected blindness with ads.

However what I found recently was so do others. I was with my friend, and we wanted to know the exchange rate, so my friend fired up his phone and googled it.

We got to a web page with tiny white boxes with black text, and a half screen booking.com ad. I asked him what his thoughts were on annoying ads shifting the content down like that, and he said "I haven't seen an ad for years mate".

The glaring device screen was mostly ad and he failed to even make the connection.

It makes me wonder, are ads really so easily ignored, or have ads went down some psychological hole where you think you are clever but a few years later you are foaming at the mouth as a booking.com customer?
Thanks for your insight. I haven't used AP but the general consensus seems to be that it performs better than its peers, so my complaints aren't regarding the quality of the system, just about the claims made versus the lack of rigorous study so far. Though I'm not a huge fan of how the tesla.com/autopilot page is primarily focused on full-self driving (including having the only video be of the 2016 FSD demo, as opposed to AP functions).

I read r/teslamotors pretty frequently. It seems a common theme in the threads about AP-related crashes for users to argue whether the road conditions were right for AP. Seems like there's a lot of assumptions and confusion about what AP can actually do, and ambiguity about computational features can lead to problems of its own. Hopefully the safety stats that Musk said they would start publishing will give us a better place to evaluate things.
Are you using something like dumb-init or equivalent? That's a definite requirement as _not_ having it results in zombie processes hanging around (which do retain some memory footprint). Read more about that here: https://github.com/Yelp/dumb-init#why-you-need-an-init-syste...
> If you really want the app store exposure ...

thanks. i got a lot out of your comment, but then you lost me when i read that.

i mean, what are the benefits of app store exposure? it's a needle in a haystack. the standard experience after putting an app in the store is crickets. do users pay more attention to app store listings than they do to mobile web sites?
We really don't know what his position on a play on words in a feature article in The New Yorker written in 2018 would be. He's been dead for 50 years, and I'd venture to say he'd be more concerned about poverty and criminal justice reform.
This is one of those things security people say that just does not jibe with reality. Everything in security is a trade off with usability, and not having your site on http, just for a redirect to https, is just completely not feasible.
There are literally hundreds of methods and tools; it doesn’t matter which one(s) you pick.

I’m quite serious.

The thing you need to realize is that you’ll get it wrong, no matter the tool... until you invest time in reviewing past estimates and plans.

People think because they’re engineers they can just magically make estimates... but its a skill. If you don’t have a feedback loop to measure your progress and adjust your actions, you’ll literally never improve at it.

...that’s why even ‘Senior’ developers and ‘technical leads’ are often terrible at this; they’ve simply never bothered to seriously make an effort to learn how to do it.
Didn't you get the silly valley memo? The sheep that use our products aren't people. They're wallets with intent, and it's our job to program that intent.
And then you make a good plan with buffers and it fails too.

Cause you forgot so many things that cost time: you'll catch a cold, the warm weather distracts, ignored the existance of family & friends, computer breaks down, ...
Invest time in determining the right approach and planning it out.

Most of that will be doing spikes: http://agiledictionary.com/209/spike/

It's one the most underappreciated agile concepts. I wish people would shut up about standups once in a while and give more thought to doing spikes.
It depends on the application. You might want to use the data to verify your intuition, which may not be consistent with the data. Or your intuition may have been based on the very same dataset but overfit to it.

I do think that people that think that ML = big data are mistaken. ML is about making the most of your data, however much of it you have.
Appreciate the feedback! I'm undergoing a massive redesign of the site that should be much friendlier. What you're seeing right now is the work of one person under tight deadlines :)
I would say failure by definition cannot be held up as a goal.

The upside of failure is that it teaches more reliable lessons than success, there's no survivorship bias at play when learning from failures like there is with success. Jack Ma's lengthy interview at Davos this year touches on the subject if you'd like to see that perspective defended by someone with authority.
It singles out Tesla and provides no broader context. Specifically there is no mention of the policies of other car companies. It is like saying that Kumo tires have been in 5 million car accidents. Sounds bad for Kumo, but there is no context to other types of tires. Will BMW or Lexus provide vehicle data after a crash? Will Google provide Android Auto data upon request?
I think this is what "The Men Who Stare Goats" is based on.
So the author of this has a vested interest in their "solution" being the correct one, but I fundamentally disagree with it.

I agree with their hypothesis that we are bad at planning/estimating, but the solution is not spending more time on it, but rather less.

Firstly I really like this humorous look at the problem: https://www.quora.com/Why-are-software-development-task-esti...

You cannot estimate what you don't know, and you don't know what you don't know and no amount of upfront planning will surface those. In their own example, you can't know upfront that there is a road closed or an accident or that only one cashier is working until you get to that point.

In my opinion the most reliable solution is to break the work down into small pieces that deliver value (ideally less than a week's work). Prioritise and then deliver the first piece. Have regular reviews/checkpoints with stakeholders to decide whether any value was delivered, are there new learnings that we need to apply to the rest of the project, or indeed new 'pieces' that we've discovered now need doing, what is the next piece we need to do and is it worth continuing.
Just a point of clarification as I was confused reading the description. The $1000 to access data isn't on an event by event basis. It's for the cables to connect to the EDR so presumably once you have them you can access all the data in the EDR at any time. http://www.crashdatagroup.com/tesla-edr-kit/
Yes, western and southern states are growing faster than northeastern states, this isn't new information. It's almost like that part of the country was settled first and then saw two Great Migrations in the 20th century. When those migrations ended in the 1970s, the population began re-orienting towards the south and west and away from the northeast and midwest.
Recent discussion:

https://news.ycombinator.com/item?id=17154355
It will need Apple to introduce in Safari the same kind of prompts that Google has introduced in Chrome, to make saving to the home screen discoverable. At the moment there is no clear distinction on iOS between saving a standard web page to the home screen and saving a PWA, and a non-expert user simply won't make the conceptual leap to thinking of the PWA as an app.

All this seems quite carefully calculated by Apple, not to miss the boat on service workers, but also to hamstring PWA's just enough to make them non-competitive.

I think the most interesting area is apps which are written with web technologies, and then deployed to different platforms. For example, that could be a React Native codebase which renders to Android's native toolkit, iOS native, and HTML, and through that to a PWA and perhaps a Windows UWP app. There's a lot of flexibility there, to start just on HTML, or just on the native toolkits, and expand organically as appropriate.

Under the current circumstances, businesses will certainly want to be on the app stores, but there are a lot of services where just having an app is limiting, for instance I was looking recently at banking services for amalgamating accounts, and every one that I could find available in the UK has a website which is just a marketing page with a link to Google Play and the iOS Appstore. But surely most people also want to be able to look at their bank accounts on their computer, not everyone owns and iPad and a smartphone is a small form factor for that kind of information. A PWA, responsive, installable and offline-capable, is a good way of handling that.

I think, PWA will probably end up being a third target, not a replacement for Android or iOS.
Shopify or Etsy to MVP until there's traction. Don't prematurely optimize by thinking you need to use Django or write the shop yourself in the beginning.

> Budget for building online store is very low. I want to full control over it and independent?

Don't do this. Your time is worth something. Just keep an eye as things develop as to how you're going to get the data out of your prototype into a bespoke system, eventually.

Source: I've helped ~5 people setup online shops this way, including quilting and artisanal yarn shops. Total time to setup was 2-3 hours per store with a screen share while on the phone with the person.

EDIT: OP: To your point about learning Python; find small consulting projects that are just beyond your skill level, and take those on. Iterate along that path. This is not the path to your Python Enlightenment. I understand it's difficult to learn a programming language when you don't have a real problem to solve, I face the same problem myself.
It is a mistake to call it "the terminal". Consoles are not terminals.

It is a regular thing for Linux/Unix people to talk about making a "better terminal". The irony of your talking about Windows in terms of "the terminal", is that pretty much all of the ideas that people put forward for making a "better terminal" have actually been done, decades since, in the worlds of MS/PC/DR-DOS, OS/2, and Windows NT. OS/2 version 1.0 had the MOU, KBD, and VIO subsystems, which introduced device independent input event streams, 2D screen buffer addressing, a handle-based API, and API calls rather than escape and control sequences. Windows NT took this further into the Win32 concept of a console.

* http://jdebp.eu./FGA/tui-console-and-terminal-paradigms.html

Command-line interpreters are not terminals, either. Powershell doesn't modernize "the terminal".

* http://jdebp.eu./FGA/a-command-interpreter-is-not-a-console....

And the most common interface between programs has never actually been the C ABI, not on DOS, not on OS/2, nor on Win32/Win64. The most commonly used convention has to be the one used by applications softwares to make system calls. Thus the most common calling convention on 16-bit OS/2 and Win16 was in fact the (Microsoft) Pascal calling convention. 32-bit OS/2 and Win32 used different calling conventions, APIENTRY and WINAPI, that still weren't the ones used by plain C functions unadorned with calling convention specifiers.

* http://jdebp.eu./FGA/function-calling-conventions.html
I think answers here will be skewed, since people who work on trivial programming tasks often don't visit websites like this.

I've worked on moderately interesting problems in some positions, and I've also worked in positions where everyone with experience was sucked into fixing infinite streams of fuck-ups from junior developers and contractors, who end up doing all the actual development.

IMO, it mostly boils down to control. If you have control and you are knowledgeable, you can solve "boring" problems in interesting and fulfilling ways. If you don't have control over how you do your job, programming can quickly turn into glorified data entry.
Congratulations, you won a Dunning-Krueger!
This is what I've initially noticed as well (app will run for several days and eventually the account will cancel due to unavailability ... you'll get paged).

The screenshot I showed in that post is an instance that's been running for _months_ under high load. I can't stress enough that using tabs/pages will always result in frequent restarts which can be really tricky if there's other sessions that need to gracefully finish.
Oh my God.
I'm still glad such experiments were done and even that they continue to be done. We should be open minded enough to ask crazy questions from time to time.
The thing is that the law requires exactly that. So it will be interesting to see the consequences.

They are currently just trying the waters, see what they can get away with, most certainly already have a backup plan they will enable at the first sign of trouble.
They seemed to really believe in them at the time:

https://www.cia.gov/library/readingroom/docs/CIA-RDP96-00788...
Will San Franciscans Vote to Ban Flavored Vaping?
5G could help close the gap as well.
Landline telephones used to operate similarly, before the massive AT&T breakup. Time is a wheel.
I fail to see how Tesla's refusal to release data is a public policy issue and that legislation is required to fix that state of affairs. They could, you know, just release the data. Then the onus is on the rest of the industry.

More to the point, Tesla's wish to be seen as a market disrupter is only going to hold as much water for me as their willingness to do it when it counts. This is one of those "when it counts" moments for me.
Not necessarily. Cross-validation can give you a valid estimate of out-of-sample performance even if you have more dimensions than samples, and even if some of the features you have are (sporadically) perfectly correlated with the target variable. See https://stats.stackexchange.com/questions/295626/does-cross-...
That makes privacy worse than the default setup with Tor since there's no stream isolation. With the standard Tor Browser you get a different circuit for each first-party domain, that's not something you'd have with this.
I think they would view that as destruction of evidence.

The next step in your scenario is "that security camera has data on me, I want it deleted".
The methods weren't "just" morally wrong but a bunch of hokum rationalized as science.

Just like yours.

Heritability does not mean heredity. Even taste is heritable. Results of the GWAS crowd are so bad that Plomin recently truned to praising his levels of signal for being not worse than social sciences. This is astounding from someone previously selling behavioral genetics as a rigorous science up there with actual genetics.

Don't even get me started on IQ https://liorpachter.wordpress.com/2018/06/04/low-iq-scores-p...
Awesome stats, I've actually run across Ahrefs a few times during my development and purview of other products. Really: well done on that, I hold Ahrefs in high esteem
I've never even seen it work in theory.
Our last (ever, I guess) toshiba had the motherboard go out. They replaced it under warranty with a different board with different components.

The new board didn’t work at all with linux. Windows sort of worked, but was unusable for reasons that escape me at the moment (kernel panics, maybe).

Way earlier, I had a 266MHz satellite. That was great, though I think the power brick went out a few months after warranty, and they wanted >> $100 for a new one, so I had to buy third party.
Lifebooks (the ones you bought from Japanese electronics stores) were amazing things. RIP.
That doesn’t bother me but to each their own.
Still no one is giving specific examples.

I spent my first 12 years as a developer doing Windows development,cut my teeth on MFC,ATL, COM/DCOM, VB6 and later on Windows Forms with .Net.

But by mid 2008 the writing was on the wall and I had spent so much time at one company, I found that my skillset wasn't marketable. No one wanted "Windows desktop developers". They wanted web developers. I've spent last 10 years being a boring old corporate Enterprise Developer nowhere near Silicon Valley.

On my list of things that I'm focusing on these days - learning at least one modern front end web framework, learning Node JS (I'm mostly a C# developer now), become more proficient with AWS from the netops/developer/devops perspective (I'm slightly above average now), Docker, etc., Windows desktop development ranks right below learning COBOL.

Looking at the market for front end technology, why would any developer who wants to stay competitive choose to focus on Windows development over Web and mobile.
Sure seems like they are hiding something. It should be impossible to make a pressure sensor read 100% instantly. It would normally take 1/3 of a second and you would see the value increase gradually.

Will autopilot even let you floor the accelerator with a car right in front of you?
>I'm not sure what I'll do when that thing finally dies.

Dual-boot
Computation has made everyone able to connect with each other with practically no barriers. AI will make connection with machines and people seamless. These are super powers.

There is absolutely no reason to be miserable at your day job. You should be preparing for superpowers if not actively using them.

I recommend watching lectures/talks during work, skipping meetings and reading from thought leaders instead of working hard to reach deadlines. Everyone is connected which means you can read and watch what Ian Goodfellow has to say about unsupervised learning or see what the issues with the world computer are from Vitalik himself as easily as listening to your marketing department figure out how to grow 10% in the quarter.
If Apple leaves China, beside blowing a massive hole in their growth strategy, how is users’ privacy enhanced?
curious, what BI tool did you end up going with?
That doesn't really work because if it isn't PII, then they don't know who it belongs to (not having even your name is a field, or else it would be PII) and can't verify it belongs to you before giving it to you.

Like visiting websites while not logged into anything in generating tons of data, but it can't be easily linked back to you.

It would be possible to link some of it back to session IDs or other things you could be linked back to your device, but that doesn't show it was you using the device, so they may be releasing data belonging to someone else using your device to you. And that is before we get into possibilities like cookie hijacking or other methods of falsely tying your device to that generated data.
Gotcha, appreciate the info!

Yea I remember a while back I was looking into the Spotify API and saw those attributes you talked of. Pretty nifty!

Appreciate your work! Sad that you're having trouble monetizing off of it.
yup, and it makes sense -- for each one of us that recoils in horror at the mcafee logo when we first boot a fresh laptop, there's two more who shrug and continue on with their lives and one who pays to upgrade to ultimate bad guy stopper pro (tm) edition
Agreed, not a zero-sum game. The goal of equality falls apart the moment you include people in the equation! We'll be stuck with that at least until everyone has access to genetic engineering.
You don't need root and developer options on such a device. If your device is well supported, you may have regular OTA updates with latest security patches (which is not always the case with stock Android by the way).

Using only apps from F-Droid, I'm reasonably sure no app is doing something shady. Google is probably not spying on you as much as on a regular Android phone. No need for having a Google account to install apps, by the way. Depending on the device, SELinux policies can be enforced (and probably are on a well supported device).

F-Droid requires enabling insecure sources but this is not a problem if you don't download random APKs from the Internet and on Oreo, it seems insecure sources are handled with a permission given per app. Insecure sources can be enabled in any regular Android device anyway.

(edit: and actually, I think enabling insecure sources is not necessary if F-Droid Privileged Extension is flashed on the device (https://f-droid.org/en/packages/org.fdroid.fdroid.privileged...)

I can't verify what are doing the numerous proprietary blobs all over the place, but this is true on any current Android phone so far (and this is my motivation to put "best" inside quotes actually).

Why would this option not be secure enough compared to a regular Android phone?

Sure you have to deal with an unlocked bootloader, but if someone gets physical access to the phone, they can unlock it anyway. They will not get access to the data since it is encrypted (it should, anyway!).

(p.s. for posterity: I meant "pay", not "play" in my previous message)
In the US, 99% of vehicles are bought off the lot because the buyers for some reason think they have 0 power and just have to settle for whatever happens to be sitting around the car park today for their $35k. For the most part, ordering is not 'a thing'.

There's a bit of legal stuff behind it too; my understanding is that you CANNOT be legally held to buy a car that you haven't seen (which, of course, seems like an obviously good thing). But a side effect is that if you order your Porsche in pink with purple polka dots and no stereo, then decide you don't want it when it arrives, the dealer may end up with a car that is not so easy to sell.