End to End Testing Flakiness - at my last company we spent a large amount of engineering time automating end-to-end tests. In the end we found them flaky, maintenance heavy and couldn’t get to 100% browser coverage. E2E tests are of huge value but their costs are still too high.
Yep. We were just getting a handle on it and then the new wave of frameworks have largely broken it again due to browser DOM's not being stable. Basically gave up automating testing of our last VueJS project after 5 years of successfully automating traditional web stacks.
I actively do, at least 1 person (I don't know) each year who's in my career track as well as the people who work for me. The way I get people to mentor is by telling colleagues that if they know anyone who might benefit from talking to me send them over and we'll see if we hit it off. That gets me about 1-2 people a year, some whom still seek me out years later.
I didn't start mentoring anyone until 15 plus years into my career, or so I had thought. After I was first asked to mentor I read up on what it is and realized I'd mentored many people in software since the moment I'd left college. Not all mentoring looks the same but the thing it always has in common is listening, asking questions, listening more then hopefully getting the mentee to listen to themselves. The best book I ever read on mentoring was "Inner Game of Tennis" despite it being intended to teach coaching. I highly recommend it.
I think you can mentor people outside your discipline if you know what questions to ask. It's not always about having a superior technical insight, if it is then it's probably coaching. FWIW I see mentoring as advising someone through personal growth area and coaching as directly training someone on skills improvement or change, the former initiated by the mentee, the later the mentor.
Everyone here is smart and has something to offer. Seek out mentors yourself and in turn mentor others when the chance arises, you'll grow tremendously.
Awesome. We need bulk requests (one or more lat/lng), and reverse geocoding with locale components (state, county, city, neighborhood) Extending tzaman's localization request, a globally unique identifier, e.g. ISO code, for every piece of locale when reverse geocoding is critical for us. When storing reverse geocoded points in our own database I want to key off the unique values but lookup the locale specific versions later on client devices (ideally via REST or an offline API if possible).
Can I dig a little deeper into this as your example has me indulging in some furious head scratching.
Providing language synonyms makes perfect sense where these exist (cf: London in English, Londra in Italian, Londres in French).
But your example implies translation of place names into their language specific equivalent. Kings County in Washington state is, unless I'm mistaken, Kings County in all other languages. Although the local residents may disagree, this county isn't blessed with a language synonym as it doesn't fall into the (ill defined) category of "well known place with a language variant".
Unless you're suggesting that if, say, French is requested as a language, a geocoder should translate place names so "Kings County" would (maybe) be "Comté Roi" in French. Although this approach sounds odd to me as (AFAIK) no one else refers to this place in this way?
Sorry for the confusion, let's see if I can clear this up. We'd like to see these locales translated to the same names that the native map program on a device would show (which is what I rely on now). For example, on my iPhone, when I switch to French and I'm in the Mission District of SF it says "Etats-Unis" / "Quartier de la Mission". Actually, that's a bad/rare example, a better one is a multi-lingual country like Switzerland where you can have 3 languages at once for some cities/neighborhoods. I want to pass the locale of the speaker to the API and get back what they'd expect in their local dialect.
I do have to ask how realistic this is. It makes sense for places that do have multi language versions. So "Etats-Unis" for the US, when in French, makes total sense.
But does translating the Mission to "Quartier de la Mission" make sense? It makes me go "errrr?".
To put it another way, taking the ever present UK "High Street" as an example. I'd expect to see this as "High Street" regardess of language and not as "Grande Rue" because no one ever says this of uses it.
So yes, I think passing the locale to the service makes a lot of sense. Supporting those places which have multi language versions makes a lot of sense too. Translating all place names to a specific language makes less sense.
