You may be able to get a list of law enforcement license plates through a FOIA request and then use this plus a network of many highway cameras to show a map of where law enforcement was last seen.
778 karma · joined September 18, 2013
Currently CTO of Roca Robotics - https://www.rocarobotics.com
You may be able to get a list of law enforcement license plates through a FOIA request and then use this plus a network of many highway cameras to show a map of where law enforcement was last seen.
Either way super weird and creepy.
The whole SCO vs IBM case was pretty unscrupulous, sleazy, and opportunistic, I agree. I'm not arguing that I have the solution to stop abuses like this. I'm saying that limiting financing is not it.
While abuse of the legal system is certainly a problem, the way to solve it is not limit financing. That only increases economic inequality. It's like saying we can solve the SF housing crisis by banning mortgages.
With normal FIFO queues you're free to abandon your place in line if, for example, you decide it's taking too long and you'd rather do something else. If later the line dies down you're free to go get back in line and you're not being a jerk.
However if you get stuck too far back in the LIFO queue, then it's actually in your best interest to abandon it and come back later. But there's no socially appropriate way to do this.
I think if you tried to do this in the real world it would quickly devolve into a mob. Random order would probably work better.
As a research project, a lot of the research is on the motion and mechanism design. Given limited resources (both budget and people), battery power was removed from the scope of the project until there's a strong reason to do it. It's more of an engineering challenge than actual science if that makes sense.
This video is relatively old. Here are some more recent videos of where the technology is now:
Overview of the most recent robot design: https://www.youtube.com/watch?t=64&v=te4M-b69fVs
Video of the "Snake Monster" made with multiple snake robots as legs: https://www.youtube.com/watch?v=AMVO6rI5mL4
Main webpage about the project: http://www.snakerobot.com
I definitely learned a ton from that job.
While I think that these sorts of people are rather rare within the population of engineers at large, they appear much more often in the interview process as they are more likely to need a job, and probably have to interview many more times before they find their way into a company.
That said, I do agree with the author that extremely deep technical interviews are also unreasonable. Variants of FizzBuzz are generally enough to weed out the terrible engineers and it's pretty hard to tell the good from the great until you've actually worked together.
Basically a flat field image is an image of a completely uniform illumination pattern (i.e. given a perfect sensor and lens with no vignetting all pixels would have the same value). This lets you measure all sorts of things, but comparing flat field images of before and after dust/tape were applied would actually highlight the exact effect.
Using flat field correction, you can even correct for these issues to a great extent by scaling the pixels as appropriate to basically account for their being light paths between the object in the scene and the image projected onto the sensor.
We don't tell employees what to think about or talk about at lunch. Sometimes it's work related and sometimes it's just shooting the shit. In either case I feel like both employee and company win.
Is sitting together and talking about your job ONLY beneficial to the employer? I feel like better communication and more discussion hopefully leading to doing a better job is also beneficial to the employee. Working on a more successful team probably leads to higher satisfaction and better long term career prospects. Even when I've worked in places that didn't provide food, all or almost all of the team still usually ate together, just because we liked what we were doing and enjoyed one another's company.
My point is employees aren't losing anything by taking or not taking the perk. We wouldn't pay someone more not to eat the food. Aside from all the weird bad team dynamics that would cause it would also be a net-loss to the company. When people work from home, we also don't pay them any more, despite that we order less food and they have to buy/cook their own.
I think most people get more value you out of the free food than if they were simply paid what it cost to provide. In the case of free food I see it as where both employer and employee do better with the in-kind perk than the equivalent cash alternative.
I would actually recommend trying what you suggest on cadavers. You'd have to inflate the lungs first though.
Apply at http://www.terravion.com/careers.html or email hr@terravion.com.
Hardware / Systems Engineer We have an opening for a hardware / systems engineer and are looking for talented, hard working, innovative candidates interested in working in an early stage company. We are Y Combinator alumni, venture backed, and growing fast. Our core product, OverView, has seen over 200x growth in the last year. If you live to deploy scalable hardware to the field, this job is for you. You will have primary responsibility for building and maintaining our imagery collection system, which mounts on to the belly of a single engine airplane. The first version is already flying and generating revenue, but you are going to design the fleet.
Responsibilities Architect, design, and build hardware and software for imagery collection which can be reliably deployed in the field Assist in data processing activities - this requires training and working with our ops team on new features you will deploy Communicate with stakeholders (operations and customers) to determine requirements for imagery collection system and imagery calibration Interview and evaluate potential engineering job candidates Assist in other activities as necessary in an early stage company
Requirements Bachelors degree or higher in Electrical Engineering, Optics, Remote Sensing, Software Engineering or Computer Science or equivalent experience Demonstrable experience designing new hardware systems and writing low level software Experience designing and deploying complex systems in the field Experience working in C, Java, and Python on Linux Strong problem solving abilities Very strong hardware and software troubleshooting skills Strong written and oral communication skills Ability to work well alone or in teams, with limited supervision required Ability to commute as necessary to Dublin, CA (our office is a 10 minute walk from the West Dublin BART)
Bonus Attributes (These are skills/experience we would really like to see but candidates without them should still definitely apply.) CAD/mechanical engineering experience Knowledge of radiometry, image calibration, cameras, and optics Interest in general aviation Experience with UAVs or drones GIS experience Farming experience, interest, or connection
However, they're still quite expensive and not really cheaper to operate than a Cessna, and then there are the legal issues. I personally think that once of the things that will drive the cost of drones down quite a bit will be when an autopilot maker comes out with a way to retrofit Cessnas and other proven, GA airframes into OPVs (optionally piloted vehicles).
We intend to move to drones whenever they are legal, cheaper and more effective, but in the meantime Cessnas are the answer.