bonus tip: for more darkness > https://darkreader.org/
After automatically updating Postgres to 10.0 via Homebrew, the pg_ctl start command didn't work. | |
The error was "The data directory was initialized by PostgreSQL version 9.6, which is not compatible with this version 10.0." | |
Database files have to be updated before starting the server, here are the steps that had to be followed: | |
# need to have both 9.6.x and latest 10.0 installed, and keep 10.0 as default | |
brew unlink postgresql | |
brew install [email protected] | |
brew unlink [email protected] | |
brew link postgresql |
Job search sites
- Stack Overflow - http://stackoverflow.com/jobs
- Angel List - https://angel.co/jobs
- Linked In - https://www.linkedin.com/jobs/
- Hasjob - https://hasjob.co/
- Github Jobs - https://jobs.github.com/
- YC Work at a Startup - https://www.workatastartup.com/
- Hacker News Who is Hiring - http://hnhiring.me/
- Hacker Earth - https://www.hackerearth.com/jobs/hiring/
Instructions for getting an ELK stack set up quick on Mac. Paths are opinionated. You'll have to infer and change. Sorry mate. 🍰
Install Homebrew if not already. You probably have. If not, you should.
brew install elasticsearch nginx
body { | |
margin-top: 40px; | |
margin-bottom: 40px; | |
} | |
.chart { | |
width: 100%; | |
height: 250px; | |
margin-top: 10px; | |
margin-bottom: 10px; |
A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.
I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.
I'd love comments and suggestions about any of these.
I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.
I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".