skysight-inc/HackerNews huggingface dataset:
> Is it not possible that general AI is a specialized AI applied over the field of specialized AI generation?

AI problems can be characterised as those where there's no clear path to a solution (otherwise we just call it "programming"); tackling them necessarily involves trial-and-error, backtracking, etc.

Since there are far too many possibilities to enumerate, solving such problems requires reasoning about the domain, e.g. finding representations which are smooth enough to allow gradient descent (or even exact derivatives); finding general patterns which will apply to unseen data; finding rules which facilitate long chains of deduction; etc.

The difficulty is that there's usually a tradeoff between the capability/expressiveness of a system, and how much it can be reasoned about. If we choose a domain powerful enough to represent "the field of specialised AI generation", for example turing machines or neural networks, methods like deduction, pattern-finding, gradient following, etc. get less and less applicable and we end up relying more on brute-force.

To me, this is where the AI breakthroughs are lurking. For example, discovering a representation for arbitrary programs which allows a meaningful form of gradient descent to be used, without degenerating into million-dimensional white noise; or to take deductive knowledge regarding one program and cheaply "patch" it to apply to another; and so on.
See a good employment lawyer. Unless you were fired for unethical practices, harassment, theft types of reasons, almost certainly a contention for wrongful termination can be made in a case like this. Your employer has taken a ridiculous risk.
For a brief moment, I thought it was the other C guy.
Can you send someone a $10 project donation using a wire transfer?

Won't the wire fee be like 30 bucks or something? 300%.
Anything the company would want to share in retaliation—true or not. Look at the shit storm that came out of Julie Horvath’s treatment at Github. Or heck, why not extrapolate this and consider the situations of those such as Snowden or Manning? In a perfect world, of course those wronged would have the full backing of the community and the employer in question would own up to their wrongdoings. But the world isn’t perfect and sadly, in reality, whistleblowers often “get to” ride-a-long in the muck as well…
We adopted buck at work for android & objective-c ios and it's been amazing speed & low-bullshit wise:

https://buckbuild.com/setup/getting_started.html

If gradle is killing you, I would suggest trying it out.

Warning: we have a few guys in a mobile developer experience team, so I don't know how good it is for indies.
No paywall, but rather video ad!
Cached version as it is down:
https://webcache.googleusercontent.com/search?q=cache:dFoTDF...
Avoid Paywall through GN: https://www.google.com/search?q=America%E2%80%99s+Dazzling+T...
Do you have any public docs on how you will integrate with your f5's?
I did both iOS and Android for a few years and it was fine. The only issue was the lag time for our customers for features across the platforms. With a small team it takes a lot of time implement on both. We have since rewritten the app as a SPA app and share 90% of the code across the web and Android/iOS using Cordova.
Facebook Helped Drive a Voter Registration Surge, Election Officials Say
This is why I think I'm in favor of basic income. With robots doing all our labor, "a job" is not how we can support basic needs like food and shelter. (Money still changes hands with robots doing all the work, so we can tax that and use it to fund basic income for everyone.)

This assumes that people want a job because they want the income, not because they want to do something rewarding all day. Not sure how to solve that problem.
I always heard people switch jobs every year in SV.
I think most libertarians have evolved into the alt-right. We're unlikely to see a non-socialist president again unless we halt Hispanic immigration.
Small team here... 20 customer on-prem. It takes more than a year to update all of them. In some cases "policy" want us to connect staging over TeamViewer sharing mouse with the the DBA.

CI is basically impossible to accomplish.

It is hilarious discovering a bug after both (us and customer) approval to go live with the last version.

The most exotic technology we have implemented is a CDN to speed up some component's delivery. And... In some cases we did not yet have authorization for that.

Honestly... on-prem is perfect to preserve your job... but man...
Gradle has problems, but it doesn't seem worse to me than making builds in Eclipse was. I would love to hear why people think it is better or worse.

I agree multidex is terrible. Google please fix this.

I do not know when I should use a fragment instead of a view. I know the layout reasons google gives in their developer guide but I don't think I have seen a piece of code that really uses fragments that way. So why?

I do like Android development though.
Ballmer yawns off Google Apps threat (2007)
I've had a fantasy of not just using different browser profiles (effectively) for each site, but routing requests for each site through a different personally-run cloud-hosted proxy.

Someday maybe I'll get around to setting it up. Maybe.
If you misroute a wire transfer (get some detail wrong), the receiving bank will get the money anyway. They will wire it back---with probably close to a hundred bucks missing.
The link from HN redirects me to https://raptureinvenice.com/its-been-real-android-why-im-ret... with this error:

The raptureinvenice.com page isn’t working -- raptureinvenice.com redirected you too many times.

Anyone having same problem?
Double that complexity if you also want a web app that works across all modern browsers.

I wish the big 4 would get their act together and stop pissing on each others legs.

FB is the most recent entry into this clusterfuck. They should be ashamed of the Oculus/GearVR developer experience, it was the determining factor in my abandoning Oculus.

It is the developer that pays the cost in the end.
He doesn't have to specify 51 weeks on glassdoor.
Especially for something like a small donation, or a small purchase!
LTCM failed too because they did not consider confidence intervals on its models.
Honestly, I can't stand websites that decide to waste 70% of screen estate. I can see the first site almost without scrolling. It is 2 to 3 pages on the other iterations.

The only things I may agree with is https and zipping.

"Fits on all your shitty screens" Does mean that it FITS ON ALL YOUR SHITTY SCREENS. Mine is a 1920x1080 (which is the minimal nowadays) and the 2nd and third iterations DO NOT FIT IT.

That thing around the web page, it is called a fucking window. It resizes. I'll do that if I want your fucking column-format.
This is how I feel too. It doesn't help that the links posted on HN always come from another URL and the article starts out without giving any indication of what it will be about. It feels like a bait-and-switch every time it goes from some really interesting, difficult to tackle issue being posed to "My product, Wolfram Language, was built to do exactly this." By the end of it, I'm left feeling like I just read a massive advertisement.
You seem to imply that an employee being somewhere for one year is a bad sign. That seems like a prejudice.

Sure, staying somewhere only 6 months can be a lack of fit. Staying somewhere a year, though, doesn't mean anything negative. Especially with startups. The startup could have pivoted. The employee could have felt that it was a good fit, then the startup pivoted and they gave the company an additional 6 months. The employee might have done great, but the statup founders chose to hire form outside rather than promote within (Showing a lack of loyalty to their own employees, and to the ones who took the greater risk by being there earlier.)

Also, you should never look down on an employee who chooses to leave after one year even if you know they are doing it because of the cliff.

The option structure of four years of vesting with a 1 year cliff is employee hostile (And startups should not be doing this because it incentivizes your employees to leave.) The first years and even months of a startup are most critical. Therefore, vesting should start nearly immediately, at most a 90 day cliff.

Secondly, the startup cargo culture is set up in a way that does not have a level playing field for founders and early employees. Founders often get RSUs which are 3X as valuable per share as startup options. An employee on a 4 year option plan should quit every company after that first year cliff.

In that way, after four years they have options in four companies... rather than all their eggs in one basket.

RSUs solve this problem by giving them real skin in the game rather than a lottery ticket that is subject to all kinds of founder shenanigans down the line.

Franky, all employees should be getting series-A preferred as it is silly that a Venture Capitalist an put in $10k of 10k shares and get preferences while an employee who gives up $70k in salary gets $70k options that he has to spend another $20k to exercise and even then only gets common.

Why is a VCs money more valuable, dollar for dollar than an employees? It's not because the VC is really going to help the company execute in any significant way-- yet the employee is.

And the delta between market price and salary you're paying employees is a real financial investment on the employees part (another reason you should not have vesting cliffs.)

Given that we have this cargo culture where things are not thought out from first principles and everyone emulates what other startups did we have not only job titles from the 1950s (eg: 21 year old "CEOs" of 4 person companies) but we have option plans that have not changed since the 1970s!)

The right thing for an employee to do in the market where companies are not giving them real skin in the game is to move every year, so that they diversify their lottery tickets.

It's the only smart move.

And that's just looking at options.

When you consider the only time most engineers ever get a raise is when they leave to go work elsewhere, from a salary perspective they should leave each year too.
They're notorious in tech circles. How notorious are they in the circles of small business owners and HR mangers?
Click the link near the top of this page which says "web". Basically does a Google search and then you can get in if you click the first search result.
I don't think lifecycles, phone rotation etc. are much of a problem, because once you know them, you know them.

I think the problem is Android keeps changing the current best practices. I'm not even sure how to know what those are - if you enter code from the Android tutorial into Android Studio, much of it is deprecated.

In January 2011, the way to do tabs in Android was via LocalActivityManager. Then in February 2011, ActionBar.Tab was added. By July 2011, the LocalActivityManager way was deprecated, and ActionBar.Tab was was pointed to as the way.

Then in November 2014 with the release of API 21, ActionBar.Tab was deprecated ( https://developer.android.com/reference/android/app/ActionBa... ). So what do we do for tabs now? Who knows? The most current tutorial ( https://developer.android.com/training/implementing-navigati... ) is still telling you to do it in the way that was deprecated two years ago.

That's what is maddening with Android - they have a way to do tabs, add a new way, deprecate the old way within five months, then three years later change their mind and dump the new way - without changing the documentation and telling you the new way to do it, it's all just deprecated.

The tutorial is full of deprecated code. What's the new way to do it? Who knows?

A few years ago some corporate director at Google must have gotten a directive to push Google TV. So then they were pushing all apps to work with Google TV. I guess that fizzled out. The latest thing is making sure our legacy apps work with Chromebooks which allow multiple apps on the screen at the same time.

I don't mind Google and Android continually chasing the new shiny, but I wish they wouldn't have a tutorial full of deprecated code, I wish they didn't change how they do things such as tabs every three years (three new ways to do it in three years). I wish they fixed bugs instead of implementing new features. On code.google.com, developers post bug reports, then many other developers jump on saying they see the same thing, and...a few years later, it just closed for being obsolete.

Another example of continuous churn - Google Analytics looks like its going by the wayside, to be replaced by Firebase. Admob is now integrated into Firebase. So that's a whole other thing that needs to be redone in an app. You have to run to stay in place.
It is still impressive to see 2.1 released already!
> To have an explicit legal system would need the explicit spelling out of these prejudices and at least provide a coherent narrative which can be argued against with data and alternatives.

I really can't see how this is so.

What about a law
Does this mean I can implement Tesseract on my home server without using php's shell_exec to perform magic on my files? I can just use Jscript instead? Cool!

My current HRCloud2 project could benefit greatly if I ever get around to it. Currently I make the php interpreter jump through hoops and move stuff all over the place to OCR images and docs. This could save a ton of time and shift the processing to the client instead of my server.
I think this is a great list, and I'm so glad Susan took the time to lay all of this out!

I have to add these two books to the list. I was surprised to see they didn't make it, even though she nailed some of the other "bibles". The following were my favorite books as an undergraduate physics major:

- Introduction to Mechanics by Kleppner and Kolenkow
- Electricity and Magnetism by Edward Purcell

No true physics education would be complete without reading and going through the problems in those books. I knew physics was my passion before, but these books helped me fall in love with physics even more.
Companies have to pay some or all of your unemployment, so it's in their interest to say you were fired for a reason bad enough that you shouldn't get unemployment. If they are found to be right, you don't get the unemployment benefits.
The company might respond a little more aggressively, and again, it would all depend on whether or not someone has anything to hide. Accusing an accuser is an old and sadly, proven technique. That said, I'm tired of getting downvotes from people who can't imagine bad behavior of this type, so...
Read the blog and react to that instead of his motivation for writing it. There aren't too many selfless acts in the world.
I hope this question is fine to ask, eternal beginner here. The few times I've looked for alternatives to stripe I'm inundated by choices and unfortunately, stripe doesn't work in my country. Nor is Atlas an option. What are good alternatives to them?
the filesystem wasn't a clue? ;-)
I find it more plausible that tech billionaires are just more likely, as a group, to believe in technocrat rule, etc. than are people who are not tech billionaires. Being an immigrant from Communist countries or a child of such immigrants is just as likely or more likely to make one despise top-down solutions as it is to make one favor them. People with such backgrounds have direct experience of the sorts of problems that arise from heavy-handed government involvement in society. Based on what I've seen, I speculate that financially successful immigrants from Communist countries actually tend, as a group, to favor hands-off government.
Facebook Has Repeatedly Trended Fake News Since Firing Its Human Editors
SW; DR. But I think SW is partly right. I think AI systems will parse and assess new legal documents and laws, but not to compile them into code. Instead the AI-based legal engine will simplify, disambiguate, and debug informally specified legal documents of all kinds into a form that is logically consistent and narratively standardized. Every AI-post-processd document will follow a legal template, simplified. clarified, and systematized by the bot.

I'm sure it'll be a while yet before AI-processed legalese can make deep use of common sense or real world knowledge. But I think it should be possible soon to at least symbolize the concepts specified and confirm that the logical premises and constraints are well formed, based on a small domain-specific knowledgebase customized to each use case.

For example: real estate contracts. The terms used in leases should be fairly few, and the relations between owner, lessor, lessee, et al should be straightforward enough to allow a bot to build and maintain a sufficient world model of relations to represent all the necessities to capture any property's purchase, sale, or lease.

The advantage then is that the AI processor could look for anomalies or unusual attributes (present or missing) and reveal them to the signatories, perhaps interactively, as well as rewrite the legalese into a very standard format that any human could understand quickly, since all terms and constraints would be presented in the same standard sequence every time.

If such an AI capability then could be extended to handle contracts of other kinds, I don't see why, one day, all contracts could not be subsumed by the bot. Plausibly, as the model grows, the bot might scale up to accommodate other application areas of law and all the other uses for legalese.

Once the models for each application area of law are induced derived and matured, such an AI bot should be able to create and flesh out any legal document simply by applying an efficient Q&A with the consumer or lawmaker, meanwhile offering advice on potential gaps, unintended consequences, and loopholes. Then the need for encoded legalese like what SW proposes would disappear as the fundamental tenets of legal verbiage disappear into the representational workings of the [Deep Net or whatever].
> Developers do need to pick a set of core technologies, and stick to it or a career can fall apart I bet

I hope not for my sake :) Im currently contracting writing C++, but my previous contract was with the ASP.Net stack. Before that I was working on a lot of Java services (introduced Scala to good effect)

I also have started a side business helping small companies by making small apps helping with their everyday stuff - sometimes Ill make iPad apps with Swift, but more recently Qt/QML to make something that runs on both OSX and Windows desktops natively. I also made (very small!) web apps for them hosted on both Azure (MS stack) and AWS (linux stack)

After a while learning the core aspects of a new language doesn't take very long, and they generally have to address the same high-level concerns. That said, learning iOS development was a continual hassle but feels like it was worth it to have a native app that I can deploy easily using HockeyApp etc.

edit: I will undermine my whole point here by saying that I abandoned a personal Android project because the dev environment felt so ad-hoc and duct-taped. I spent a ridiculous amount of time trying to get the simulator to render GL properly without any luck (on Windows)
> It's the same reason that we could but won't lower all speed limits by 15mph or 30mph. It would save many thousands of lives per year

You make the erroneous assumption that drivers will suddenly obey the new speed limits. That isn't going to happen. Second the fatality rate and total number of motor vehicle crashes is lower now than it was when the NMSL (National Maximum Speed Limit) was in effect.
Your profile says you want to hire people, but your comment here says you are prejudiced.

You're operating from the 1950s veiwpoint which is really a cultural hold over from the great depression- that employees should be desperate to find a job and companies should be free to screen them out for any arbitrary reasons. Let me guess, you make them write code on a white board too.

If you have a one year cliff you are providing a huge financial incentive for your employees to leave after a year, by shifting the risk onto them.

Maybe that's why you don't have enough people already?
Is he being prosecuted?

Nothing will change until we show that white collar crime is still crime.
> Ito: I generally agree. The only caveat is that there are a few people who believe that there is a fairly high-percentage chance that a generalized AI will happen in the next 10 years. But the way I look at it is that in order for that to happen, we’re going to need a dozen or two different breakthroughs. So you can monitor when you think these breakthroughs will happen.

> Obama: And you just have to have somebody close to the power cord. [Laughs.] Right when you see it about to happen, you gotta yank that electricity out of the wall, man.

Do we seriously think that it would be that easy? I think an a "generalized" AI, if aware of the ability for a human to remove its power and so that as a bad thing, would not be stopped by unplugging it. By the point you realized you needed to unplug it, it would have already convinced a human that to help it spread and it would have found other sources of power.
Yup. And such a chef probably wouldn't publicly berate people for eating meat, or expect being called out if they did.
Yes. I faced similar problem so I went to Google Cache.
http://webcache.googleusercontent.com/search?q=cache:https:/...
>The new CFPB rules are sweeping not just in their treatment of prepaid accounts, but in their broad interpretation of what a prepaid account is. The regulations will cover reloadable cards, cards used for government benefits, payroll cards, and some popular electronic and mobile systems. Venmo and PayPal, for instance—which allow users not only to pay each other directly, but to store money within the platform—will also be required to follow stricter guidelines and assume more liability for fraud, loss, and account errors. The CFPB has included digital-wallet options in its rules in spite of strong objections from the industry, which maintains that its products don’t pose the same risks to consumers that prepaid cards do.
[0]:http://www.theatlantic.com/business/archive/2016/10/cfpb-pre...
Nothing yet but it basically borrows a pattern that we use for nearly all of our Kube-related systems: descriptive configuration files bundled by the developer with their individual applications. So, alongside their code, their Dockerfile, their Jenkinsfile, their Kube specs, 'and monitoring spec, the dev adds a file that describes the load balancing. "This app needs a privatenet-only VIP on port ___, speaking protocol ___. For the health check do this ____. Load balance using ___ algorithm." This file (yaml) would be parsed by our build pipeline and fed to a service that manages the load balancing. This service initiates "watches" on Kube services and nodes and configures the service appropriately on the F5 via the LB's REST API, pointing the pool at the NodePorts of a subset of Kubernetes nodes.

We would probably build this around Kube's Ingress API. We're still a few backlogged projects away from addressing this internally. For now, we manage VIPs by hand. About 1-3 new VIP requests a week.
Containers from scratch(Pt 1&2)
You can implement Your Own languages on pypy so make it 4 :)

Breaking changes I would include would be : remove all the deprecated bits of subprocess or replace it entirely, remove the zip, ftp and other modules in favour of virtual filesystems with a consistent api and finally try and make all the APIs symmetrical (e.g. open always paired with close, push with pop etc).

But then I am too lazy :)
I hated the current incarnation of mobile too. Never owned a smartphone aside from Maemo / Meego Nokias.

But I've found some peace using Android without the mothership. That's CopperheadOS with F-droid:

https://guardianproject.info/2016/03/28/copperhead-guardian-...

It's simple and it works well.

But yeah, things are a bit messy from a development perspective. Too much fragmentation I guess.