Personal plug: I'm building a self-service AIOps platform for engineering teams (somewhat similar to this work by Meta). If you're looking to read more about it, visit -- https://docs.drdroid.io/docs/doctor-droid-aiops-platform
Doctor Droid (https://drdroid.io) | ML Engineer (15-20LPA INR) | Bangalore, INDIA | ONSITE | Full-time
We are a DevTool. We help engineers debug production issues faster. We do this thought our Open Source automation tooling for on-call and SRE engineers. We work with tech enterprises to help optimise their DevEx / On-Call routines.
Requirement:
We are looking for someone with 1-2 years experience in production ML/LLM projects at growth stage startups or enterprises. They will primarily work on some of our tooling experiments -- you can see more of our experiments through the products section in the website.
We are a team of 5 engineers. We are a seed stage team, collaborating and ideating everyday at our office, also called casa-de-droid.
email siddarth [at] drdroid [dot] io if it sounds like a place you'd like to be a part of.
Mm. Google Maps will sometimes confidently suggest roads which without that recommendation would have seemed quite unsuitable. So people put their instincts aside and think Google must know better ... only to regret it later.
It would be helpful if Google could add a few qualifiers like "Note that this is a very steep and mostly single-lane unpaved road" or "This road leads through an unsafe neighbourhood", followed by "An alternative route would be ..."
Ha... It's not that they can't do it now, it's just Google fear the uproar the woke brigade will inevitable make about how dare Google classify poor black neighborhoods as unsafe. But yeah I agree with you, that feature would be damn helpful, especially for someone like my wife driving home at night.
I think it is unrelated. Regardless of how dangerous is an area, there are still people who libe there and have to go there or through there for various reasons.
It is not like life stops when places have an higher crime rate. Peoole still conduct business, have family outings and whatnot.
Besides the feeling of safety is totally subjective and some white neighborhoods you might consider safe as a white person might be unsafe to people of colors going there because they will be viewed under the bias of systemic racism and might be seen as a threat to people.
Absolutely. Same with the favelas – locals are safer than strangers.
Incidentally, the UK government website contains specific warnings about using GPS navigation in Brazil:
---------
The security situation in many favelas is unpredictable. Visiting a favela can be dangerous. Avoid all favelas, including favela tours marketed to tourists and any accommodation, restaurants or bars advertised as being within a favela.
You should:
– make sure the suggested route does not take you into a favela if you’re using GPS navigation
– avoid entering unpaved, cobbled or narrow streets which may lead into a favela - tourists have been shot after accidentally entering favelas
If you’re unsure about a location, check with your hotel or the local authorities.
We deployed the change to make it intuitive (similar to what is suggested) yesterday. It's still in integration branch so awaiting merging in main on this.
> i thought perhaps it had executed the step, which the check mark indicating completion or success.
Noted.
> It wasn’t clear that it was an input box since it didn’t have focus, and it wasn’t clear that the check mark was a button.
Noted.
> It seems like it’s the “Data” field, although the name doesn’t make much sense.
It is indeed a dropdown list but we had hard-coded it for sandbox so user can't change the source of an existing step. It is changeable when you host your own version or when you add a new step in sandbox.
> There’s a “reload”(?) icon next to it, but I have no idea what that does.
In case user decides to add a new source on-the-go (say in another tab), reload helps fetch the same list again.
Overall, I do understand that some parts of it are unintuitive and is a focus area for us to improve it asap.
> if I can automate a runbook can I not just make the system heal itself automatically
The runbooks are still codified by a human in the current scenario. We are experimenting with some data to see if we can generate accurate runbooks for different scenarios but haven't found much luck with it yet. I do think that some % of issues will be abstracted in near future with machines doing the healing automatically.
> you should invest in toil reduction to stop having those repeated problems.
Most teams I speak to say that they try their best to avoid repeating the same issue again. Users typically use PlayBooks for:
(a) A generic scenario where you have an issue reported / alerted and you are testing 3-4 hypotheses / potential failure reasons at once.
(b) You want to run some definitive sequence of steps.
