Service meshes like istio.io start to solve a portion of this.
Almost certainly there is endless complexity but I bet you can come up with something useful. Good luck!
379 karma · joined May 11, 2010
Service meshes like istio.io start to solve a portion of this.
Almost certainly there is endless complexity but I bet you can come up with something useful. Good luck!
> In 1991, the United States Congress passed the ISTEA Transportation Authorization bill, which instructed USDOT to "demonstrate an automated vehicle and highway system by 1997." The Federal Highway Administration took on this task, first with a series of Precursor Systems Analyses and then by establishing the National Automated Highway System Consortium (NAHSC). This cost-shared project was led by FHWA and General Motors, with Caltrans, Delco, Parsons Brinkerhoff, Bechtel, UC-Berkeley, Carnegie Mellon University, and Lockheed Martin as additional partners. Extensive systems engineering work and research culminated in Demo '97 on I-15 in San Diego, California, in which about 20 automated vehicles, including cars, buses, and trucks, were demonstrated to thousands of onlookers, attracting extensive media coverage. The demonstrations involved close-headway platooning intended to operate in segregated traffic, as well as "free agent" vehicles intended to operate in mixed traffic. Other carmakers were invited to demonstrate their systems, such that Toyota and Honda also participated. While the subsequent aim was to produce a system design to aid commercialization, the program was cancelled in the late 1990s due to tightening research budgets at USDOT. Overall funding for the program was in the range of $90 million. (https://en.wikipedia.org/wiki/History_of_self-driving_cars)
7 years later there was the first DARPA Grand Challenge, where no cars completed successfully. There's a great episode of startup podcast with interviews of the original competitors: https://www.gimletmedia.com/startup/grand-challenge-season-6....
It's interesting to wonder whether and how much farther we'd be with self driving cars and computer vision in general if the government had continued to put its resources behind this project.
1. Use empathy to both overcome resistance and do the right thing. The strategy in Step 2 for reframing an interaction in a way that gets the person to understand that you're trying to help them, and also reminds you to remove your ego and that the goal is to improve things for everyone, is one I've used a lot. Not because people think you're trying to be difficult but because it overcomes defensive barriers and helps ease them into the context switch of thinking about the problem.
2. Get a foothold with iterative progress. The author did this by splitting adoption and (the process for) configuration. Especially with tools and processes, people will often try to jump to the final state and if they can find any holes or issues with the proposal as is they'll be inclined to throw it all out at the start. If you instead make it clear that we're a) trying something new that will b) be improved as we learn more about it and c) can always be reversed if we decide it was a bad idea, people are usually much more open to it.
One thing the article mentions though is "spending" leadership capital. I like instead to think of it as "investing" capital. If the decision you invested it in ends up being bad, you lose it. If it ends up making people's lives better, you've gained more. Thinking about it this way also can get junior people, as mentioned in the article, to be more inclined to help with decision making. They don't have a lot of capital to spend but they can choose to invest the little capital they have in order to grow it.
The actual problem is more likely that in the vast majority of incidents officers DO NOT KNOW what they're doing is wrong, that for instance they're acting with bias or unreasonably against someone of color in a way they wouldn't act against a white person. The ACTUAL purpose of the body cameras is to create a record that allows ACCOUNTABILITY for officers ("I felt threatened" with no evidence is no longer enough to justify a shooting). Only with that accountability can we start to PROVE that officers are acting unfairly whether they consciously intend to or not, and then fix the problem (with "training" as the article says but with no detail may as well have been saying nothing).
Worse yet, trying to make tech people feel bad just for finding a job they actually like and going to a city where those jobs exist! If only we could all be so lucky. Like the job or not, I haven't seen very much indication that people are going into tech in droves just for the money (unlike what I assume you see in banking).
I very quickly found early limitations of the jamboard like (iirc) not being able to copy drawings or group text and drawings. I'm sure over time the programming will get better.
Another good one is the SNL Seinfeld monologue https://www.youtube.com/watch?v=6HS9h4xFRww. Because of the audience participation you crane your neck around to see who's talking.
https://www.google.com/search?q=roll%20dice
https://www.google.com/search?q=random%20number%20between%20...
Probably fairly easy for engineers to add these
> Always-on Hotword Search Enabled No
It's already disabled.
I don't understand the outrage here. I remember chrome asking me if I want it listening all the time for "Ok Google", I thought "Obviously not" and said no, and that was the end of it.
It doesn't need to scale especially well for the vast majority of customers. If your first reaction is "this doesn't scale" or "this doesn't eliminate programmers" you have to be a professional point-misser. I'd want to see how intuitive the interface for making this is but it's cool stuff, and as it matures I'm sure will only get more interesting.