I don't know the access to resources, sheer scale, research, and good pay would make it pretty enticing for me. But really it comes down to what you are looking for long term. Do you want to optimize, finances, lifestyle, work in a particular space, learn more and eventually start your own thing? A job at Google probably scores well along most of these dimensions.

Meal Replacement Companies such as Soylent will continue to experience healthy growth.

Chip Manufacturers like NVDIA and AMD will continue to experience over average growth.

Meditation will grow and we will become aware of the mental health of individuals (Trump etc)

Machine learning will be the best field to be involved with.

Probability of a bad event Nuclear/Bio/AI increases.

Bezos will emerge as the best entrepreneur of all time.

It's sampled.

> Playing fucking candy crush.

This is not balanced at all. We also use it to connect, relay information, learn, translate in realtime, coordinate events and meetups...

- Docker - Javascript - D3 - Node - Google Compute Engine - Google NoSQL data store,

Ya Google has a counterpart product to that - https://cloud.google.com/vision/

Regardless Google and Microsoft have offered a narrow slice of what can potentially be done in this space. They are still not seeing that we really need is a marketplace that has the ability to let machine learning specialists surface their work to businesses for a profit.

I just changed that to take the public key, thanks!. Users get a private and public key, the private key will work in all areas but should never be exposed. The public key can be exposed and in the dashboard you can white list the allowed origins.

>You have docs for accessing it but I can't find any for me building an api endpoint. The docs also seem to suggest I use a client library called "kittn", which I'm pretty sure is wrong.

No you are absolutely right. The docs are not built out yet and you are seeing the template data. We will curate this process and provide documentation. But a quick overview is as follows.

The API endpoint is static.

POST https://macgyver.services

The payload is a dynamic JSON object that has the following properties.

program id, user key, program_data (as defined on the program input page)

It would look something like this -

{ id: "9s9z6J6b", key: "private-live-6w9c2p10G5p3b6y" program_data: {} }

As far as how the program should function I can just show you the addition program as example.

The program should be called "main" with a file extension that corresponds to the run time you want macgyver to call.

So the addition program is a javascript file called "main.js"

// user specified data format

var data = '';

var sum =0;

data = JSON.parse(data);

for(var i=0; i<data.values.length; i++){ sum += data.values[i]; }

var result = { "sum" : sum }

// This gets returned to the client

console.log(JSON.stringify(result));

The variable 'data' will have it's string content be populated with the clients payload send data at the time of execution.

https://askmacgyver.com/explore/program/addition/2c2c5w7W

There is some information on that here.

https://askmacgyver.com/how-it-works

Didn't notice the URL - I've changed it. Thanks.

It shouldn't be an issue - the API currently sits on Google's Cloud Platform which provides the infrastructure and tools to scale the service. IMO Snapchat's usage of the platform really speaks to the stability and capability of it.

If I am going to trust you my API I want to know that you have top notch SLAs on your service, and since I am providing the code you are going to want to monitor the heck out of it so that you know that in case of failure whose fault it is.

Understood, we will work on finding that info and surfacing it on the site. As far as monitoring and errors go, the program is actually hosted by us in this case. So unless the program is faulty in some way any response issue is probably our fault.