HN user

adamb_

348 karma

Engineering @ https://www.thousandeyes.com

Posts9
Comments125
View on HN

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/

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 :)

iPhone X 9 years ago

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

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"

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.

Switching to a new industry can be tough... and often landing your first job is the hardest part. As such, I would NOT be choosy at this stage. There's a ton of companies out there that don't have customer-facing software, but desperately need developers. These positions may not be exciting (e.g. improve intranet app, clean up reports, etc) but they're always there, the competition for them is generally lower, and they serve as fantastic proving-grounds for newcomers.

Usually form validation occurs on the server-side, written such that if a form's post body is invalid, a human-readable set of errors will be returned to the client to display. In this context, the password is just another field mapped to a specific conditional check -- which, if evaluated as false, simply means adding a canned message to the said set of errors to return.