HN user

parasj

89 karma

Systems ∩ ML

Contact/Email: https://parasjain.com

Posts0
Comments22
View on HN
No posts found.
[GET] "/api/user/parasj/stories?hitsPerPage=30&page=0": 500 Failed to fetch user stories

DeepScale | Mountain View, CA | Full-time | ONSITE

BUILDING PERCEPTION FOR AUTONOMOUS VEHICLES

At DeepScale, fast and efficient neural networks are critical to the success of our product that enables cars to be safer. We have a team of top engineers working on the problem of perception in Autonomous Vehicles. Traditional approaches use different sensors to solve different perception problems – for example, LIDAR data to find the objects, and Camera data to classify the objects. Our solutions integrate all the sensors to solve each perception problem, yielding higher accuracy and safety. We are committed to bringing together the best people to pursue solving this problem.

DeepScale is a venture funded startup in Mountain View, CA. Our investors include Greylock Partners, Bessemer Venture Partners, and Autotech Ventures. Our founders are Deep Learning experts from UC Berkeley with strong academic and industry track records. We have multiple early customer engagements with key OEM, Tier-1, and Tier-2 customers/partners.

We are actively seeking candidates for the following positions:

- Deep Learning Research Scientist: https://deepscale.breezy.hr/p/b826c8695051-deep-learning-res...

- Head of Quality (Automotive): https://deepscale.breezy.hr/p/bf69b505b3fc-head-of-quality-a...

- Product Manager: https://deepscale.breezy.hr/p/bbd956433dd8-product-manager

- Software Engineer: https://deepscale.breezy.hr/p/7a41fe40e416-software-engineer

- HPC Systems Administrator: https://deepscale.breezy.hr/p/2e610fa815b7-hpc-systems-admin...

It used to be a mixed bag - it's good to hear that they've improved their attitude to battery issues.

I remember taking a bulging in-warranty battery for a white unibody-era Macbook into the Valley Fair Apple Store and being told that it was my fault the battery was damaged. Genius bar wanted to charge for a battery swap and wouldn't dispose the battery for me if I didn't pay for the swap.

TL;DR: It's great for realtime apps, but not so much for the traditional web app as compared to something like RoR.

My perspective as someone who has been using it since its release. It depends on what kind of app you are building.

Coming from RoR, Meteor actually is more of a pain given that it still has edge cases that can eat developer time, especially once you dive past the initial levels of tutorials and documentation. RoR also has well established best practices and norms, unlike Meteor and perhaps Node.js as a whole. This means you will be writing a lot more boilerplate code. Meteor has some memory issues as well at times. You have to be aware of memory leaks and will frequent the profiler often, especially with large client-side applications. I've had some projects that I've worked on in Meteor hit 1GB of RAM client-side. Recent releases have been working on this, though. Live reload and hot code pushes are kind of a moot point with something like the Live Reload plugin for Sublime Text or equivalent.

For realtime applications, Meteor is a whole different beast. Realtime applications are much easier to code. I'm comparing this to making a realtime Node.js application. Meteor takes care of the boilerplate for you, pushing changes automatically to the client. It's not difficult to do something like socket.io and node.js but it is nice to have that all handled for you.

It's great for getting an application off the floor - it has a lot of that magic RoR had when it was released. Once applications get more advanced, the structure and maturity of RoR make it easier to work with. These issues are things Meteor is working on, especially in terms of stabilizing the spec/API and working on fixing the edge cases. With 1.0, it seems they are bringing some more stability to it by making it production ready. Its strengths are much more apparent in realtime applications as compared to a traditional web framework.

Edit: As compared to other node.js frameworks like Express, Meteor is much easier to work with - I probably would not go back to raw Express after Meteor. It's been moving fast to 1.0 where many of the issues I've had with it should be resolved with stability and as edge cases are resolved.

I've been using Meteor since its release and its been great at making apps at maximum velocity.

You mentioned that some people are already scaling Meteor across multiple servers. Looking at it, round robin load balancing won't work given requests to a server seem to be stateful. How is that being done as of now? Do you guys have any guidance on how to do that?

[dead] 13 years ago

Linux driver support with the proprietary Nvidia drivers has always been iffy, if it worked.

World 13 years ago

Whoops, I used backticks instead of spaces to mark it as code.

World 13 years ago

Here this is, formatted so it is more readable.

  p = "<" + "pre>";
  for (y in n = "zw24l6k\
  4e3t4jn`t4qj24xh2 x42kty24wrt413n243n\
  9h243pdxt41csb yz43iyb6k43pk7243nm\
  r24".split(4)) {
    for (a in t = parseInt(n[y], 36) + (e = x = r = []))
      for (r = !r, i = 0; t[a] > i; i += .05) 
        with(Math) x -= .05, 0 > cos(o = new Date / 1e3 + x / PI) && (e[~~(32 * sin(o) * sin(.5 + y / 7)) + 60] = -~r);
    for (x = 0; 122 > x;)
      p += "   *#" [e[x++] + e[x++]] || (S = ("eval" + "(z=\'" + z.split(B = "\\\\").join(B + B).split(Q = "\'").join(B + Q ) + Q + ")//m1k")[x / 2 + 61 * y - 1]).fontcolor /\\w/.test(S) && "#03B");
    document.body.innerHTML = p += B + "\\n"
  }
  setTimeout(z)
* Edited for formatting