Facet | San Francisco, CA | Software Engineer | Full-time | Onsite or Remote
Facet is harnessing machine intelligence to make photo editing quick, collaborative, and scalable. We understand that pictures are more than just pixels, so we're building a platform that lets creative professionals edit collections of photographs in terms of the people, objects, and colors they contain.
We're looking for engineers who can think deeply about complex systems and empathize with artists, and are also curious and creative. We use Typescript, React, WebGL, GraphQL, Postgres, Node, Python, and Tensorflow, but it's not a big deal if you haven't.
Our team includes folks from Google, Adobe, and Cruise, and we're backed by great VCs, former Dropbox execs, and AI researchers from Google Brain and Salesforce.
If you'd like to talk, I'm the CTO and you can drop me an email at matt at facet.ai.
Because, while it is a landmark achievement, it has little relevance to which people have access to health care, which people are confined to cages their entire lives, or which people are allowed to make decisions about their own bodies -- and, in the US, other stories are very relevant to these questions right now.
I would love for Hayabusa to get more attention, but the problem isn't that it's being drowned out by nothing. It's being drowned out by stories that will have real and long-lasting effects on people's everyday lives.
Facet | San Francisco, CA | Software Engineers | Full-time | Onsite
Facet is harnessing machine intelligence to make photo editing quick, collaborative, and scalable. We understand that pictures are more than just pixels, so we're building a platform that lets creative professionals edit whole collections of photographs in terms of the people, objects, and colors they contain.
To build this platform, we need engineers (like you?) who can think deeply about complex systems and empathize with artists, and are also curious, respectful, and creative. We use Typescript, React, WebGL, GraphQL, Postgres, Node, Python, Tensorflow, and Terraform, but it's not a big deal if you haven't.
We're seed funded -- backed by great VCs, former Dropbox execs, and AI researchers from Google Brain and Salesforce -- and building out our founding engineering team in SF.
If you'd like to talk, I'm the CTO and you can drop me an email at [email protected].
- Is a signal that the driver intends to turn. Drivers should also be using their actual turn signals, of course, but as a cyclist I would much rather have a driver who fails to signal merge early and turn, rather than turn with no warning.
- Allows the cyclist to more easily get around to the left.
You might check out Mitsuba (http://www.mitsuba-renderer.org/) and LuxRender (http://www.luxrender.net/). Both are more modern open-source renderers with Python APIs, and I know that Mitsuba is quite popular in the graphics research community (in part because that's where it comes from).
Berkeley, CA - Contract - REMOTE - iOS front-end engineer
We’re bringing interactive cinema-quality physics to mobile devices. We need someone to help us build a slick, seamless iOS app to show off our awesome physics. If you want to push the frontiers of computer graphics, work with brilliant researchers, and build a game with the most beautiful interactive 3D liquids the world has ever seen: come talk to us!
Our team is three professors and a Ph.D. student, from CMU and Berkeley. We have a track record of producing great research, with six SIGGRAPH papers among us this year alone. This is a research project, not a company, but we do have a reasonable budget. If all goes well, we'll be presenting this project at SIGGRAPH next year.
If you write fantastic iOS apps, are interested in computer graphics, and (ideally) have some experience with video on iOS, you should get in touch!
Send an email to [email protected] with your resume and tell us a bit about why you’re interested.
In any case, running global illumination often causes a major increase in rendering time. So it's understandable that Pixar, which has to render a huge number of frames at huge resolutions, did not traditionally use it much.
There's also another factor at play, which is directability. Physical correctness is not usually a priority except as far as it advances the artistic goals of the people making the movie. If the director says, "can you make the right side of that table look less red?", you need to have some way for the artist to achieve that goal, even if that's not how the scene would "really" look. I expect that the development of new tools and processes to allow precise manipulation of the lighting in globally illuminated scenes was just as much, if not more, of a barrier than the additional cost in rendering time.
Secord et al. also did a perceptual study in which they determined which features were most correlated with user viewpoint preference and built models for viewpoint preference based on this information: http://gfx.cs.princeton.edu/pubs/Secord_2011_PMO/index.php
What would worry me is that I don't understand what Facebook really wants out of this acquisition, and why this will motivate it to do right by Parse users. It looks to me like a number of other people in this thread don't understand either and are coming up with their own theories, few of which are good news for the developer.
If you sympathize with the author: do not post things like this. Listen to him. What makes you think you were the intended audience? What makes you think you know why he was writing? Do you see the irony in you trying to "educate" a black person on talking about racism?
Don't fault people who have to put up with this shit, day in and day out, for not having limitless reserves of patience. His job isn't Racism Educator, so why should he have to act like it?
I mean, yeah, ideally everyone is infinitely calm and can call these things out in a measured way every time they happen. But you're asking a lot from the victims here in order to spare the feelings of the aggressors. (Perhaps unintentional aggressors, but aggressors just the same.) What you're suggesting isn't easy.
And what's to say that the person he calls out will take it well? Look at what happened at his workplace: they told him that the things he was complaining about were only jokes and that he was too sensitive. Look at what is happening inthisthread: people are complaining about his tone, complaining about his word choice, and insinuating that he's making things up. That's not even going into the people who start out ostensibly agreeing before segueing into what sounds like their main point: how racist they think the author was being.
So give the tone argument a rest. It's one of the most reliable distractions that people fall back on to avoid discussing racism, sexism, and all other kinds of oppression, and it's already taken over way too much of this thread.
It looks to me like the robot just exhibits less motion in general. This might be because (as far as I can tell) the authors optimize only to match a set of static poses, not for physical or perceptual realism of motion.
Better than Apple can without Google? Maybe. Better than the existing Maps app? I use transit directions in Maps a lot and the transit apps I've downloaded very rarely.
No, but your page still makes me play "hunt the noisy tab", and then, if I decide I want to watch the video, requires me to pause my own music to listen to your loop.
I don't object to all audio. Click-to-play and relevant? Great! But auto-playing, un-mutable, and completely unrelated is a terrible combination.
That's not really something I would want to try. Omitting references can lead to accusations that you are trying to claim as your own novel contributions things that others have already done.
I thought it was a little odd that he says the proper way to solve the problem is to have a higher-res screen, just before he says that we can't do super-sampling because it's too expensive.
It's a nice interface, but I'm a little confused about your column adjacency cost function. In particular, why sum only the bottom quartile of pixel distances to get column costs?
advantage leads to more enjoyment, which leads to more practice...etc
I actually agree with you here. This is why I think things like sexist/marginalizing presentations at conferences are a big deal: a hostile environment seems to me a lot more likely to achieve this than possible differences at the bare fringe of the aptitude spectrum.
Do you think there is some huge pool of people good enough for YC who just don't get in?
Yes, I believe that there are probably more than 300 people in the United States who could potentially be accepted to Y Combinator. I'd believe there are a lot more than 3000. We're talking about aptitude here, remember, so you have to consider people who could potentially get in, but don't apply. Do you really believe that the vast majority of the people who could even conceivably get in to YC, given some set of life choices, do in fact apply?
The only point I'm making is that small differences in underlying probability distributions can have large effects in the composition of people accepted into a highly selective program.
Yeah, if we're willing to grant you all kinds of crazy concessions, you can cobble together an explanation. But you're asking for a lot to make YC selective and sensitive enough for your example to be reasonable. The YC selection process has to be consistent and incredibly accurate. Most of the people who are even capable of getting in must apply. Acumen in various areas has to be minimally or negatively correlated, and to even be considered for YC, one person has to have all of the relevant skills.
And this is just to get close to the gender disparity that YC sees.
Sure, I agree that normal distributions with minor differences in variance are very different at the tails. But to get this to explain away the gender disparity in YC selectees? Epicycles on top of epicycles.
(Also: if this is really about the tails of the aptitude distribution, going by the paper you cited and your same arguments, we'd expect to see a lot more Asian women than Asian men in YC. I suspect this is not the case.)
If anything, I suspect your risk aversion point is closer to the mark, but that opens up an entirely new cultural and political can of worms.
Facet is harnessing machine intelligence to make photo editing quick, collaborative, and scalable. We understand that pictures are more than just pixels, so we're building a platform that lets creative professionals edit collections of photographs in terms of the people, objects, and colors they contain.
We're looking for engineers who can think deeply about complex systems and empathize with artists, and are also curious and creative. We use Typescript, React, WebGL, GraphQL, Postgres, Node, Python, and Tensorflow, but it's not a big deal if you haven't.
Our team includes folks from Google, Adobe, and Cruise, and we're backed by great VCs, former Dropbox execs, and AI researchers from Google Brain and Salesforce.
If you'd like to talk, I'm the CTO and you can drop me an email at matt at facet.ai.