mgce
Joined 10 years ago
Joined 10 years ago
Without commenting on the above statement:
> For example, Bazel throws away your analysis cache when you change flags that have nothing to do with what's being built or how, like flags that change what tests are run.
I don't think this is a good example. Bazel's analysis cache clearing is to preserve correctness in the context of a legitimately algorithmically difficult problem. The fact Bazel has this limitation is a testament toward its correctness strengths. I'm not aware of systems that have solved that algorithmic problem but curious if anyone knows any.
Also Bazel avoids that problem for most "flags that change which tests are run", since that subset of the problem is more solvable. --test_env was a notable exception, which was fixed (https://github.com/fmeum/bazel/commit/eb494194c1c466f7fd7355...) but not sure if it's in the latest Bazel release yet? But generally changing --test* has much smaller performance impact.
That image is incredibly outdated and has become an increasingly tired cliche.
This applies equally to the outer boroughs. Poorer neighborhoods (in any borough) are scrappier, of course, than the rich areas. But they're just as full of life and vibrancy.
I really take your point on the media projection. It's relentless. And it really keeps an outdated image alive, especially in the minds of people who don't live here and can't directly contrast with their own eyes.
You seem to be implying per capita is a bad measure of safety. But you're not being clear why. Can you elaborate?
Different kinds of tests offer different levels of confidence at different levels of time and investment.
A fully integrated shop should think this through carefully and design their own comprehensive end-to-end process. Which feedback is most helpful at which point of the idea -> deployed product pipeline? What value does it offer to the larger process? Feed in org-specific variables like release timelines, team structure, customer expectations, money, compute resources. Use appropriate tools for each piece and remember the largest goals to keep the company reliably delivering whatever makes that company valuable.
We all know he’s acclaimed. That doesn’t invalidate any of the points you’re trying to retort, and your disrespect for people with different viewpoints is an uninteresting contribution to this discussion.
> Census data show that more city residents than suburbanites drive to work in Manhattan every day, according to Mr. Schaller. He estimated that 263,000 people in 19 counties in and around New York City drive regularly to jobs in Manhattan below 60th Street. Of those, 53 percent, or 141,000, live in the five boroughs, Mr. Schaller said. The greatest numbers are from Queens, with 51,300, and Brooklyn, with 33,400. About 23,900 auto commuters live in Manhattan, while 17,400 are from the Bronx and 15,200 from Staten Island. The suburban area with the most auto commuters to Manhattan is Nassau County, with 22,091 people driving to work in the borough, followed by Bergen County, with 19,975.
So 53% from NYC, 10% from Manhattan, 47% from outside the city. Only counting commuting as you note.
I suspect you're right: it depends on the specific card/bank, not whether it's credit or debit.