Live data from Hacker News

Building Jarvis

facebook.com

11–20 of 263 posts

Re: Building Jarvis

#11

zuck-mbpl:~ zuck$ php j play some red hot chili peppers PHP as a shell scripting language. Old habits die hard, huh?

It's not a bad scripting language in that case.

Quick startup, a good amount of CLI-specific APIs, available on many servers already, and no compiler or huge amount of tools needed.

It's a bit verbose for little scripts that should be in something like bash, but it's a great alternative to something like python if you are more familiar with it.

Re: Building Jarvis

#13
More than anything else, what stood out to me was his discipline for knowing how to manage his time in a way that enabled him to build something like this while still juggling the n number of other things on his plate.

Re: Building Jarvis

#15

Anyone setting out to do something like this will quickly see how much of a hassle it is to exfiltrate data from relevant services and your own devices. APIs and SDKs cover a lot of use-cases, and that is all great and commendable, but we don't truly own our own devices, data, or the algorithms that make them useful. I think this will continue to hamper our ability to have a truly useful 3rd party (your home in this…

> My experience of ramping up in the Facebook codebase is probably pretty similar to what most new engineers here go through. I was consistently impressed by how well organized our code is, and how easy it was to find what you're looking for -- whether it's related to face recognition, speech recognition, the Messenger Bot Framework [messenger.com/platform] or iOS development. The open source Nuclide [github.com/facebook/nuclide] packages we've built to work with GitHub's Atom make development much easier. The Buck [buckbuild.com] build system we've developed to build large projects quickly also saved me a lot of time. Our open source FastText [github.com/facebookresearch/fastTex...] AI text classification tool is also a good one to check out, and if you're interested in AI development, the whole Facebook Research [github.com/facebookresearch] GitHub repo is worth taking a look at.

Face recognition and speech recognition are the most obvious pieces that look to be proprietary, but there is lots of other useful open stuff that he explicitly links. FastText looks like it would be really helpful for at least the natural language piece of Jarvis-like applications.

Re: Building Jarvis

#16

Anyone setting out to do something like this will quickly see how much of a hassle it is to exfiltrate data from relevant services and your own devices. APIs and SDKs cover a lot of use-cases, and that is all great and commendable, but we don't truly own our own devices, data, or the algorithms that make them useful. I think this will continue to hamper our ability to have a truly useful 3rd party (your home in this…

[deleted]

Re: Building Jarvis

#17
post #7

If it's literally Zuckerberg building all this, I bet it's full of security holes (not that he's a bad dev, I wouldn't know, just that one dev can't reasonably be expected to develop a secure app at a pace even remotely quickly). Dunno what that means, just that it would be mildly funny if someone used this fact to try to get a job at Facebook or something.

Actually, there are some ways to make this very secure that don't take much effort that in are common use around facebook. It is quite easy to build secure thrift services, and to design a thrift api it is just creating a text file with the necessary idl. You can then access the service from most any language by generating the right client. I'm sure same thing goes for gRPC and Stubby on the google side (more familiar with the fbthrift, folly, wangle, proxygen tech stack myself, but I'm sure its just as easy.)

Re: Building Jarvis

#18
post #7

If it's literally Zuckerberg building all this, I bet it's full of security holes (not that he's a bad dev, I wouldn't know, just that one dev can't reasonably be expected to develop a secure app at a pace even remotely quickly). Dunno what that means, just that it would be mildly funny if someone used this fact to try to get a job at Facebook or something.

I've seen people go down this road before, even specifically toward Zuckerberg. It's never actually a good idea, it just makes you look like a psycho. Big difference between revealing an exploit on Facebook and demonstrating a proof of concept to their bug bounty and exploiting Mark's personal home.

Not saying you would do that, just saying for other people reading that it's not really a joking matter when it really happens =P

Re: Building Jarvis

#19
post #13

More than anything else, what stood out to me was his discipline for knowing how to manage his time in a way that enabled him to build something like this while still juggling the n number of other things on his plate.

I find my discipline is much stronger when none of the things on my plate is a fire I lack tools to deal with.

Re: Building Jarvis

#20
post #9
post #5

Earlier quoted context omitted.

The grumpy snarky HN user in me says that a lot of the "I deployed a server to do X" and "I wrote code to do Y" in this blog post should actually say "A Facebook engineer provided me with direct API hooks to do X and Y" , but it's anyone's guess.

API hooks to what though? It doesn't seem like he's integrating with much if anything from Facebook. TBH, he seems happy enough getting his hands dirty that I would imagine he purposely did it unaided just for the satisfaction of it.

He did reuse things that exist inhouse, like the face recognition piece. To rebuild a service with Google/Facebook/Microsoft/Amazon level accuracy in that task, it is definitely more effort than 100 hours by itself.

To use an existing private service, not nearly as much effort.

That being said: Of course he could have learned how to train a model himself, but even in that case he is using training infrastructure and data that is available to him that is not public. I highly doubt he had the time to build those sorts of things himself. But his goal was more talking to his home and using tools to build an interactive home assistant. Sounds like he was very successful at doing that. He wasn't out to build the individual AI pieces, doesn't make it not cool or interesting.

Post reply on HN