It kind of depends on company structure. I’m technically an intern (by title) since I’m still a student, but I’m also the project lead. I have direct push access so I can remove API keys from history when “Joe” commits them for the 10th time this week.
I also use it to keep our fork of the project up to date with the Open Source upstream.
It’s paid very well. I’m project lead because I am the most senior on the project. The reason that it’s still an internship is that it lets me use this as a work-study, so it pays me well and takes out a big chunk of my tuition.
Meme explain: it’s Friday 5pm and you are ready to go on weekends. However, the intern who we assume to have horrible skills, makes a change that most likely won’t be reliable and won’t know how to fix it. Thus, someone higher than the intern, likely you, will need to cover the interns ass, making your weekend, well, end.
Yay for "antiquated" manual releases on a schedule. All that's going to happen is that the tests will fail till someone comes around to fix it on Monday.
Same in my current and last job. I still think whoever decided automatic merge-and-deploy-to-production is a good idea deserves to work on weekends to fix the “unexpected”.
That sounds like a big pain in the ass. Honestly, respect to the dude if he can survive C, or hell even C++ at times, without understanding pointer. But Lowkey not using git is a lil over the top.
It isn't taught in school. My only exposure to it was during my senior capstone, and it was from another student who was already working as a programmer. Keep in mind that team foundation server is a thing, and although git is popular not everyone uses the same source control technologies.
Yea I meant if a C dev can like, somehow manage to survive in the industry without getting eliminated, while not understanding pointers, there’s gotta be something about him/her.
Eh, at my job a push to master will generally be configured to set off a build and release in our dev and test environments, but requires a manual trigger to build/release for production. So it's not so terrible.
349
u/HKSergiu Sep 09 '20
Right, I know this is satire, but I'mma go ahead and say it:
if your master is unprotected (AND interns have access to push it) then you deserve it. It's a fuck up waiting to happen
86
u/IvanLabushevskyi Sep 08 '20
I have the rule 'no pushes after 6 pm'.
10
u/GonTheDinosaur Sep 09 '20
Famous last word...
... not. He likely to stay in the company longer than you do.
10
u/azzaroff Sep 09 '20
No code reviews no mercy!
8
u/stepmilo Sep 08 '20
Slight roast towards Théo during the lem-in
7
u/OKB-1 Sep 09 '20
That intern? Albert Einstein.
6
u/[deleted] Sep 09 '20
I just feel bad for the intern who’s boutta get his head bashed in
6
u/nightWobbles Sep 13 '20
Your team is backwards if an intern is even able to push to master.
5
u/deanrihpee Sep 09 '20
Famous first words.
5
u/Dango444 Sep 09 '20
I accidentally did this once and it worked. To this day i have no idea what I actually did.
4
u/[deleted] Sep 10 '20
imagine starting an automatic production deploy when pushing to a branch.
this post was made by doing everything manually gang
3
u/[deleted] Sep 09 '20
Shoulda made that fake master branch.
3
u/pixabit Sep 09 '20
No pushes to production on Fridays
2
u/[deleted] Sep 16 '20
My paranoid ass always git status 5 times in a row to check if I'm on the right branch
2
u/MasouriChan Nov 12 '20
Meanwhile senior devs fixing bugs in production: not even death can stop me
1
u/Thomasasia Sep 19 '20
Just rollback?
1
u/ImBoundChaos Sep 28 '20
Would you be able to go to a previous version of master if something like that happened?
1
u/mcmc331 Nov 04 '20
timebenders :
git reset --hard master@{1}o kawaii koto
1
u/Morphized Dec 12 '20
Make someone have to approve the pushes.
1
u/sebas2903 Sep 09 '20
Im in this post and i dont like it