Skip to content

Instantly share code, notes, and snippets.

View Djidiouf's full-sized avatar

Antoine Lang-Cavelier Djidiouf

1 follower · 3 following
View GitHub Profile
@Djidiouf
Djidiouf / gist:ee6289e1a69443b4f451
Last active February 16, 2016 05:51 — forked from blalor/gist:c325d500818361e28daf
redhat init script for consul
#!/bin/bash
#
# consul Manage the consul agent
#
# chkconfig: 2345 99 01
# description: Consul is a tool for service discovery and configuration
# processname: consul
# config: /etc/consul.conf
# pidfile: /var/run/consul.pid
@Djidiouf
Djidiouf / interview-questions.md
Created October 4, 2018 06:29 — forked from jvns/interview-questions.md
A list of questions you could ask while interviewing

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?".