sumodm

FYI: Gukesh is 18 yrs old and the youngest World Champion. He is also the 18th champion, in its 138 years history.

Something along this lines is the real danger. People will understand common failure modes and assume they have understood its behavior for most scenarios. Unlike common deterministic and even some probabilistic systems, where behavior boundaries are well behaved, there could be discontinuities in 'rarer' seen parts of the boundary. And these 'rarer' parts need not be obvious to us humans, since few pixel changes might cause wrinkles.

*vocabulary use is for a broad stroke explanation.

Cruise isn't at fault for the collision with pedestrian, since it was a second order impact. The primary cause being Nissan Sentra and pedestrian. But could cruise avoided the impact and is this how humans react when we drive? Here is the timeline from the report.

  - AV starts moving at -9.2s, after light changes
  - Prediction output shows pedestrian path crossing AV travel lane: -7.7s
  - Pedestrian leaves AV's travel lane: -5.3s
  - Pedestrian pauses at crosswalk : -4.7s
  - Contact b/w Nissan and Pedestrian; -2.7s

> When the light turned green, the Nissan Sentra and the AV entered the intersection. Against a red light, a pedestrian entered the crosswalk on the opposite side of Market Street across from the vehicles, passed completely through the AV’s lane of travel, then stopped mid-crosswalk in front of the Nissan Sentra.

I wonder whether this flagged alarms in Cruise's systems when the pedestrian crossed in a potentially dangerous situation. These kind of 2nd and 3rd order conditions seems particularly hard to train for.

Two cents:

My bg: Grown engineering teams from 1 person to 20-25 strong and have done this 3 times at various early stage startups. So you know can judge whether this might apply or not.

Depends on people: Are they task oriented / goal oriented ? You can detect based on how they talk about previous projects. Do they say they did x, y, z or do they talk about the big picture of the problem being solved, why they chose what they chose, its features/lack of features etc.

1. Task oriented folks want detailed action items and they don't mind you being super specific. With these folks, have a detailed plan of what to implement, how to implement, break it down into day by day plan. Try to be aggressive w.r.t goals (don't do this, if they are already demotivated), goals that are slightly harder to reach. But ensure that even if they are 60% is done, you will get a workable soln. Ensure that each days tasks are done and checked off and you can track daily progress. Catch up for detailed meetings every 3-4 days. This would be rescheduling of tasks, addition/removal of specific tasks that are no longer valid/requires to be done, re-prioritization/reorganization of tasks etc.

2. Goal oriented folks would want you to give them the vision and overall direction. But watch out for digression that lead to long discussions during such meetings. Tell them what you want to build and why you want to build that, how will the user use it. Then they will figure it out and you can have review meetings. They would not like to you put detailed line by line plans. Ensure you have high alignment during stand-up. Have check ins every 2-3 days to ensure that they are not going in completely wrong directions and you couldn't catch it due to brevity of scrum. But these are usually shorter meetings.

TartanSense Robotics | Computer Vision/Machine Learning Engineers, Robotics Engineers, Full Stack Developer | Full Time | Bangalore, India | On-Site

Tartan Sense is building small robots that can help farmers with various time consuming manual tasks. From weeding, to sowing and more. Farmers struggle with unpredictable availability of labor, low yields compounded with pesticides/herbicides that are often quite harmful. We want to help change that by a combination of precision agriculture, predictable availability and insights for farmers. If you have deep skills in one of the above areas, email us at [email protected]. Please use subject of email as HN | <ROLE> . If you are looking to spend some time in India, in a startup doing interesting and important work, you are most welcome to join us.

Technically, it could be 2.5T because they never say annually. So may be they are talking about 100 years :|. That said, the QZ title is really misleading and click-baity. They have a simulated environment test and yet to tested for real world conditions.