> How would you see this in ThousandEyes?

Checkout this video analysis from the team on the hijack: https://youtu.be/YXm4GJMUlP0

Thanks! Do you know how I can access that page he is on? I'd like to have a click around myself.

Here's the link he starts on in the video:

https://webysvi.share.thousandeyes.com/view/tests/?roundId=1...

Route 53 DNS queries getting black-holed at a small ISP in Ohio: https://pbs.twimg.com/media/Dbka0oAVMAAFEXx.jpg

Absolutely. Sometimes you just want to output a quick CSV, open it locally in familiar spreadsheet environment, and explore.

This approach only works if you know your resume will be read by a person exclusively, and not machine parsed.

If you're targeting a mid-sized company or bigger, your resume will most likely first be parsed[1], with key skills, education, years of experience (etc) extracted and stored in some kind of applicant tracking system, and then loosely searched against. Your resume will likely not be looked at by human eyes until it passes through this filter, so it's important to consider making your resume as machine-readable as possible: Minimal formatting, key technical terms should be abundant, standard date formats, etc. Only after this should consider how it reads naturally, and make any appropriate adjustments for subindustry (e.g. academically-focused jobs generally want to see education first, etc.) and company.

[1]: https://www.sovren.com/resume-job-parser/

Checkout https://legiblenews.com -- It updates once a day, sourced from Wikipedia.

If you've built a wrapper around the integration in your application logic -- such that handling the actual HTTP requests has been abstracted away from the rest of your application -- then you can use a mocking framework (like Mockito for Java) directly in the unit tests. If you haven't, or want higher-level / isolated integration testing, you can create a mock application that mimics GitHub's API, put it in a Docker container, and use a docker-compose.yml during testing to quickly spin up your new test environment.

Listened to it last week -- The gist is that they've found a new home with the CNCF & The Linux Foundation, which bought the IP so that they could continue working on it publicly. Besides the database (which was always open source) this is especially important for parts of RethinkDB that were meant for "enterprise-only", which the company was working on internally before they shutdown. All and all the community support sounds strong, and after listening I decided to take another look at Rethink for my next project :)

Small edit: CNCF funded the transaction (to free the IP by relicensing under Apache-2.0) but the project is hosted by CNCF's parent, The Linux Foundation.

Disclosure: I'm executive director of CNCF and did the transaction. And, in case you're wondering, I'm thrilled that the community of people able to take advantage of the code is growing.

Dude, really thank you for your hard work on this. Out of curiosity, how did you pull it off?

Initial demo for Face ID failed -- Obviously less than ideal when trying to convince your audience that "it just works".

It was because the phone had been rebooted, and iOS requires a passcode after a reboot.

Still a PR fail though

These things happen in live demos.

That's true but they don't usually happen to apple's. Apple takes great pride for their flawless presentations.

Growing up I initially had tiny regular allowance, which gradually became tied to specific weekly chores & subsequently bigger. As parent myself now I think approach works well, as it balances "I'm giving you this $ because I love and support you" and "hard work should be rewarded"