[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/biz/ - Business & Finance


View post   

File: 75 KB, 482x427, d90.jpg [View same] [iqdb] [saucenao] [google]
17490286 No.17490286 [Reply] [Original]

Dubs decides what I tell my parents when I get home today

>it was a junior dev job
>push my code to branch
>merge conflict
>git documentation unhelpful
>senior dev tells me to figure it out myself
>decided to reset my entire git history and in the process deleted the original master which was used for a live dashboard during client meeting
>RIP.jpg

>> No.17490301

>>17490286
Yeah git can be really scary bro

>> No.17490306

>>17490286
Tell them that you're a fucking failure that should have never been born.

>> No.17490315

>>17490286
Did you at least scream “FUCK NIGGERS” as you left the office?

>> No.17490334

Come out as gay and that you want to look into becoming a fag pornstar

>> No.17490347
File: 148 KB, 322x527, 1574561856125.png [View same] [iqdb] [saucenao] [google]
17490347

>>17490334
>>17490315
>>17490306

>> No.17490375

>>17490334
Have fun explaining that to them OP. Hope they’re liberal af.

>> No.17490388

>>17490286
This is what you get for having push access to master.

How do you even manage to that you had to do git push --force to work???

>> No.17490397

>>17490286
Hi mom, dad. I have some very unfortunate news. *go into some long story and make it seem like you're terminally ill, place value on life, talk about the shortness of it, talk about cancer statistics, be indirect*. Then after you have set up the conversation so that they will likely percieve you as terminally ill, tell them you got fired. Easy as that.

>> No.17490449

>>17490334
This will probably soften the blow a bit.

>> No.17490534

>>17490286
tf no backup?

>> No.17490636

>>17490286

Well, just tell them what happened. How/why did you push the deleted master? Did the place not expect you to know Git coming in?

>> No.17490640

why would they give a fucking junior dev an access to master branch? their fault.

>> No.17490646

>>17490286
"I quit my job today because it fucking sucked. I'll get something else."

>> No.17490655

>>17490286
Lol. No big deal anon.

>> No.17490659

Sounds like a douche bag senior. Git is quite complex and annoying to get up and running with

>> No.17490672

>>17490640
That's what I was thinking.

>> No.17490678

>>17490388
It's clear that the place where the OP worked is badly run. Firstly, the company should have had a daily backup that they could have restored. Secondly, as you say, the company should have done a better job of defining access control to users.

Finally, what kind of faggot is the senior developer where he will not lend a hand to a recent hire? The senior developer, if he has any responsibility for training up the junior developer, should suffer some sort of consequence, too.

>> No.17490684

>>17490286
>senior dev tells me to figure it out myself

what an asshole though... the whole senior-junior thing is supposed to be a cooperative learning process, not some lil bitch telling other people what to do

>> No.17490701

>>17490286
Nice larp, mate!

>> No.17490705

>>17490640
Also this.
>hire you without the experience, and then expect you to kust know.

t. Guy who was blamed for losing an important doc, even though it was likely thrown away by someone else or taken off the desk

>> No.17490716
File: 20 KB, 403x504, FB_IMG_1582648031719.jpg [View same] [iqdb] [saucenao] [google]
17490716

Mom, dad, I was molested by a senior dev multiple times and today I've had enough

>> No.17490724

Just recover it from the reflog.

>> No.17490733

>>17490678
Git is scary like >>17490301 said but holy shit, a single junior shouldn't be able to ruin a project in 3 commands. Unless that client meeting was pivotal, can't say I would fire OP. I did something almost that retarded in my first job too and my boss was pissed off but understanding (sorta).

>> No.17490738

>>17490684
>senior dev tells me to figure it out myself
You know what op, be happy. You just screwed them over you just flipped it on that jerk
>junior dev tells senior dev to recode it all

>> No.17490750

>>17490684

There are some things he should let a junior try to figure out on his own for a bit before stepping in, like basic issues with the software that he can fix, but something procedural and critical is something he should always be helping out with

Generally speaking anything that a senior already knows is old hat and can teach in a few minutes is something he is obligated to take the time to share with juniors, from a team cost perspective

>> No.17490764

>>17490286
Tell them they are going to pay your bills

>> No.17490791

>>17490286
larp, but you can probably restore the state with git reflog

>> No.17490800

>>17490286
lmao imagine not being able to understand git

also
>one post by this is
fuck off larper

>> No.17490859
File: 71 KB, 523x320, 1575142254972.jpg [View same] [iqdb] [saucenao] [google]
17490859

>>17490678

This.

You have excellent three points there.

The fourth point that tells about a piece of shit company is that after all that has happened, they dodge responsibility and fire the new guy.

This is not a "accidents in IT" stuff. This is "piece of shit company practices" stuff.

>> No.17490928
File: 57 KB, 680x521, 1581288863970.jpg [View same] [iqdb] [saucenao] [google]
17490928

>>17490286
>yeah idk Coronachan just wiped out the whole office and now I'm out of a job.