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.
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 :)
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"
Not thinking about team morale until it becomes a issue. Negative mindsets can spread through a team quickly, and once they take hold they can be hard to root out.
"The main problem with memristors is no one has figured out how to make large numbers of them that are reliable enough for commercial electronic devices. Researchers continue to puzzle over the best materials to use and the most effective way of manufacturing them"
Everyone on my team has an automated sit-stand desk. Just walked around the office and not a single one is in "stand mode", and that's not likely to change. It's a neat idea, and I've known people who swear by it, but in practice it's one thing extra to have to think about.
I work in this space as well and can say that Google just making noises about entering the market as aided in bringing renewed interest (and investment) in developing better tech from the established companies.
This topic is highly speculative, but my guess is something that's only possible via another technogical wave -- perhaps AIs that post interesting context of our lives on our behalf, or a new accessible medium better than text / photo.
Checkout this video analysis from the team on the hijack: https://youtu.be/YXm4GJMUlP0