falsedan

no it's the geography, too hard and bumpy or waterlogged to drill tunnels

There might be some old red rattlers in sidings of rural stations, my dad made a deal to get one and the fittings from its sibling when the owner wanted to use the bogeys and trays for a tourist train. That was a fun few summers of unscrewing everything from one unairconditioned carriage and and reattching it to ther other.

> Wait, I think I know the answer: if they admit that fiber isn't coming any time soon (if at all) people might go to a competitor for faster service!

It's the opposite: if they say they'll string fiber in 2 years, they get drowned by anrgy requests for status updates if they slip. It's lose-lose for them: commiting to a delivery date gets people angry at them if they slip does to regulatory/admin delays, not commiting to a date gets people fed up and impatient.

> I'm not sure what you are expecting.

> The tiles aren’t marching squares though, and calling them after how they were generated is confusing!

I don’t understand how this could be misunderstood by someone reading in good faith. I think that, if a reader remarks “this is confusing because…”, you shouldn’t tell them they’re wrong and it’s not confusing.

We won an internal hackathon by writing the API and no front end, using a browser extension instead to manifest the client on the third-party page we couldn’t get API access to in time. It sure was easy to write.

Follow-up from the related article last month (which was discussed in https://news.ycombinator.com/item?id=20285242).

It might mean that the company is selecting for skills other than raw problem-solving talent

That’s the algorithm, sure. The tiles aren’t marching squares though, and calling them after how they were generated is confusing! If they produced rectangular or other non-square tiles would you still insist on not calling them Wang tiles?

Calling Wang tiles “marching squares” will confuse the heck out of any graphics programmer.

Enterprise bought out the car share system which started in the city I live in.

That’ll be fine, a post mortem will show that ops weren’t the cause and their comp package will help them get over this little package of stress

probably not all of those things, did you check their specs page?

Terrible maintenance costs for ventilation, plant vehicle access, widening (e.g. temporarily for roadworks), poor kerb access for deliveries/emergency vehicle access, plus a firetrap in the case of a burning vehicle

At least that's what I've worked out from Cities: Skylines.

Still struggling, if requests from X were slow, caching their responses would only drop or maintain p99. If those requests were fast, p99 might increase & alert... but if you were caring about performance at a user-level, you can imagine you're dimensioning on users too, and you'd see the p99s for each user hadn't changed, and would shrug and bump the alert threshold up.

If it were me, I'd probably start by caching the slow requests (that are above the p99) first & adjusting the alert thresholds to match the new performance.

Manipulating/aggregating metrics is a giant pain, you have to understand what exactly the implementors though `max` or whatever means and try to match it up to what you need.

One thing the article doesn’t address is that logs have to be accurate and metrics should be consistent, but not vice versa. If your performance metrics are always 10% out, they’re still perfectly usable (as long as they’re always 10% high or low) to alert on or to compare to metrics from a known-good historical period.

But your p99 for endpoint B hasn’t changed, why would you alert based on service-wide stats? It’s easy to tag/dimension metrics by urls

If you don’t have a long-arm stapler for binding, you can take two normal swing-arm staplers and use the anvil from one to strike against with the other. Not as neat but can do in a pinch.

Also I mush prefer PDFs that aren’t formatted for print: printing booklet order is trivial, but undoing the formatting into single-page is a nightmare

Who cares what they’re called as long as they’re fast and don’t crash when running at scale/fill the disk or memory

Tests don’t prove anything, they just show the intended behaviour. Only full verification proofs show correctness.

Too often I’ve seen “tests show it’s correct” suites horribly fail to provide value when the behaviour changes in a unit of business logic and the brittleness needs to be unwound and replaced with robust assumptions.

And if you do need a mock (for something with hard-to-undo side effects), you set it up with stub response & canned data in the test fixture, and never assert anything against it in the test.

Part of the problem is that most test fake libraries support mocks (usually they even have it in the name), those mocks have complex “verify the 3rd call was function doDoAction with parameter (‘yes’, ‘really’)” and then people think that full-blown mocks are the only way to guarantee 100% correctness.

There's a clear conflict of interest: moderating comments critical of the organisation who employs you can easily be considered biased to a disinterested party. It doesn't matter if there is bias or not, the possibility that people will see it as biased is enough for people to recognise it and lost trust. This kind of moderation should be done by a disinterested party, and the Google employee should recuse themselves from addressing it (just refer it to another moderator).

Guess who just finished their Conflict of Interest yearly refresher!

It worked for you but consider the vast population who are not as privileged to have easy access to health care. Do the ads help them? Will their lives be improved by more ads, or by removing barriers that make it harder to get medical assistance (physical & mental)?

Nice. Dear gods I forgot what nonsense plugs were before USB. Did it plug into a? MIDI? port??

Yeah, see, here your GP would refer you to a psychiatric provider (probably a nurse) or you’d see it a pamphlet in the waiting room when you came to talk about how you feel because you saw your doctor more than once every 2 years because you weren’t terrified by how much it cost/if you would lose your job taking time off work.

Probably not. More like the HMOs can see the deals each other are getting & maybe new entrants in the market can budget accurately before launching.

What would be best if this was a way to collect medical cost trends for a couple of years to pave the way for price regulation.

> the old MS joystick that had a throttle, extra buttons, and especially the yaw twist capability of the stick

The sidewinder? I don’t remember it having a throttle though https://en.m.wikipedia.org/wiki/Microsoft_SideWinder#3D_Pro

Looks like there were relaunched and you can still get USB models from retailers.

lol no it assumes a US account. it's not even listed in the app stores here. people mostly use bank transfers for everything since it's free and fast

> If the abstractions are designed and named well, why should the reviewer need to jump to the declaration of the function in the if statement?

How will the reviewer know if the abstraction is well-designed or named without reading it? Code quality attitudes change over time so sometimes the standard project-provided helpers end up not matching the intuitions of more recent contributors.

I think Yelp do a pretty good job of avoiding this, simply for the fact that they don’t have a cushion of associated traffic: people use Gmaps for this because they use Gsearch or navigation, and if Gmaps isn’t great at filtering out spammy listings, well it’s plenty good at other things. But if Yelp get a reputation for poor business data quality, users wont want to use it for that and there’s not a lot else to get them to visit & keep monthly active user counts up & give sales impressive stats to quote to businesses when they call.

Also without quality business listings how would sales know the number to call to pitch ad campaigns??

It’s a pity this approach doesn’t scale as wildly as search, Yelp shut down all the non-North American sales stuff in 2016 presumably because it wasn’t profitable.