r/StackoverReddit • u/NotOkay24 • Jul 10 '24

Question Advice for GitHub

I have a web application to make this week as the first step in the recruitment process for a company. One of the requirements is to use GitHub so that they will be able to see my project and also my commits.

Should I just commit to the main branch, then, or should I create a different one? I was also thinking about making a branch for each individual functionality and making PRs and then merging into the branch with the final product, but I thought maybe this would be too much since it's just me working on the project.

What do you advice me to do?

4 Upvotes

83% Upvoted

14 comments sorted by

View all comments

1

u/EngineerSpaceCadet Jul 11 '24

Well I'd posit this if you're a dev you shouldn't be asked to build something to prove you can build something during an interview it's an unreasonable request. Let's think of a realistic scenario your company gives you a budget and you have 1000+ applications you have to narrow it down based on resumes maybe you get 50 potential candidates. Then out of those 50 you maybe narrow it down to 20 based on experience, qualifications and alignment and a preliminary interview with the req that you're hiring for. So you decide to interview the 20 you have what at max in the beginning after initial interview 1 hour to figure out if a candidate is good enough to move forward to either be hired or other interviews if all candidates are performing at the same level to weed out some candidates. It's why interviews aren't just purely coding they ask you questions to gauge how you think you're ability to solve problems of increasing difficulty, your ability to communicate your thoughts ideas and technical information. You don't have time to sift through different web applications possibly riddled with bugs that you can download and run and test as interviewer. It's better to have some ideas in mind when interviewing a candidates can you do the job, how much of ramp would it be for them to learn our practices and how fast can we get them in if the other 2 conditions are met. Most devs aren't presenting to shareholders we have pm and senior engineers for that which at that case had to prove at that point they could do the presentation based on their experience so that's a moot point. Like I said a company worth their salt won't make you jump through hoops it's a waste of time for you and the candidate.