/explore
|
You are here 
|
www.laac.dev | ||
| | | | |
rkoutnik.com
Technical interviews are terrible because we don't know what we're filtering for. |
|
| | | | | ||
| | | | |
www.e4developer.com
In my career as a software developer, I have interviewed over 100 people. Most of these interviews were face to face interview involving coding on paper or a... |
|
| | | | | ||
| | | | |
www.hillelwayne.com
Caveats: I'm not an interviewer, I've never done serious research on interviews, and I haven't tested this. I propose this entirely as a thought experiment. Assumptions: We interview at jobs to find ideal candidates. WE are looking for candidates who are Good at programming Good at software engineering Can work in a team A "culture fit" (not an asshole). Technical interviews test the first two. They are primarily whiteboard questions, abstract design questions, or "write this program" questions. |
|
| | | | | ||
| | | | |
www.rasulkireev.com
Whenever you building a site with Django that will have user authentication, it is recommended to create a Custom User Model, before the first migration. Sometimes you forget to do that. In this case you have to follow a strict procedure, which I'll show you in the post. |
|
| | | |||
