!!fml

"Root, go fix this bug. It'll take you two days."

The "bug" is a feature that was never implemented for one particular payment type.

The code in question is two years old, full of typos, smells, junior-isms, and is convoluted AF. The feature's commit touched 190 files and implemented many other features as well. Thus far, I have been unable to narrow down where this particular feature's code lives for the other payment types, nor which code or payment paths lead to it. Burned out, I can barely focus on the screen, let alone follow its many twisting and dynamically-inferred paths. I hint as to the ticket's scavenger hunt nature during standup.

"But I wrote comments on the ticket telling you exactly where to look to fix it," Thundercunt admonishes in front of the team.

"Sure, you did," Root replies. "You reworded what the original dev had said in the comments 20 minutes prior, and agreed with him. His comments were helpful, but it doesn't tell me how any of it works," she continues.

TC scoffs and closes the meeting.

Root stares blankly, seeing neither code nor screen, questions her life decisions, and recalls the previous tickets she has worked on: nearly every one of them busywork, fixing other people's bugs. Bugs she never could have gotten away with if she tried.

"Why do I put up with this?" She asks. "They don't care, and it's killing me."

But the bills remain, and so must she.

"Fuck my life" she finally decides.

Got together with my old dev team (5) who all left the same company at the same time almost two years ago. (Thats a whole other story).

One of them told us he left and went to a new company that measured performance by the amount of commits a dev would to per day. Of course he didn't know that when he signed on.

Three months into the job he had a week where his first commit wasn't until a wednesday and he got called in by the manager to explain his lack of commits and how he was going to improve.

He quit on the spot. Had a new job in less than a week.

Other devs at the company were fixing typo's and just commiting them one at a time to create a lot of commits.

Code works.

Rename a variable for clarity.
Third-party lib behaves differently, breaks things.

Change the var names back.
Still broken.

Stash changes and checkout previous commit.
Everything works.

Diff with stash.
No notable changes. (some comments, ...)

Checkout branch again, pop stash.
Broken again.

... What?

We passed a milestone: 250,000 phpunit testcases.

If it weren't for a heavily parallelized build pipeline which splits it out over 20 servers, it would take about 7.5 hours to complete.

Not hating on PHP, and without tests it would truly be hell...

But still, fucking hell, we outgrew PHP.

Not having a solid type system just means you either accept more bugs, or write thousands of unit tests to guard all the foundational cracks in the system.

On the bright side, I get a coffee break after every commit 😄

i was asked to start a new project, and another dev was brought onto the team shortly after. as soon as he joined, straight away he started an entirely new project and worked on it through the whole weekend, then came back on monday and just sort of pasted his files into/over the code i had already started and was working on, with no regard for folder structure or naming conventions or anything. his work was even split between 2 almost identically named namespaces (both of which were completely different to the existing project namespace) and his shit broke everything i did in the first place. the cherry on top is that none of his work was even functional, it was purely dummy/mockup web pages that weren't linked to any sort of backend.

when i asked him wtf he thought he was doing, he kept saying "i didnt touch your code" and refused to acknowledge that pasting a project over a different project can break stuff, then said it "wasn't his fault that i'm slow and not keeping up". and just kept saying vague bullshit about how i have to do it his way because he "has more experience"

he had no idea what my previous experience was, he had never asked and i had never told him, he just decided that he had more experience than me.

i dug through the shit and found out that he didn't just break my work, he had actually purposely deleted it when he realised it was getting in the way of his spaghetti. i showed him the commit and confronted him with it and all the cunt said was "well the good news is, you know the fix" and kept trying to dismiss me in the most disrespectful ways he could think of. i eventually snapped at him (long overdue at this point) and told him that any experienced developer would not commit code that didn't even fucking compile, especially when they're the one who broke it, and that he needs to grow up. of course he then complained that i was being unprofessional.

our manager decided we should go with fuckfaces """code""" without even looking at the work either of us had done, purely because fuckface is older than me and that's how the world works.

in the end i just told my manager that i refuse to work with the guy and he could either take him or me off the project (guess who he picked) or i quit.

after a few months of the guy failing to deliver any of even the basic functionality that was asked for, the entire project got scrapped, and the dude just quit once everyone realised he was literally just larping as an experienced dev but couldn't accomplish simple tasks.

i never received an apology from anybody involved.

I was only seventeen back then and I was a Java Developer Intern, not knowing much about enterprise oriented coding.

The project leader in our dev team saw a lot of potential and passion in my work, but was convinced I wasn't taught enough to do the right thing.

I was mainly doing shitty mappers and services back then, which were somewhat used but never lasted long and were ditched a few months later, which always bummed me out. I wanted to make an impact on REAL projects that would deploy into production.

So Mister Mentor (GDPR forbid to use the actual name), who was always first to come and last to leave the office, taught me what it means to code for real.

We stayed after 5pm until 7-8pm multiple times a week and he taught me in a deeply understanding and calm way how to:
- Git (SVN)
- Refactor
- SOA
- Annotate
- Deploy
- Unit Test

And most importantly:
- How to debug like an absolute BOSS
(We even debugged native Java Libraries just for fun to see if we could break them)

Fast-forward a month later and little intern me made his first commit on production.

Without Mister Mentor, I wouldn't be half as good of a developer as I am today.

It is time. I have to admit it.

I don't understand Git.

I just memorized some basic commands: git commit, git push, git push -u origin master, git clone, git checkout [-B], git merge. That's it, that's the full list. I use them like they're some kind of magic spells that do what I need. Everything else, those intricacies like rebasing, resetting, HEAD and all that shit, is beyond me.

I'm not a real programmer. Real programmers know Git.

Story of WTF happened to my job

During my employment in (name censored) was stressful, They claimed I didn't complete my task on time which they constantly remove me from git and documentation(which have to follow their style of returning data), I kept emailing, slack, WhatsApp calls them, mostly and predictably got ghosted and blocked.

So How the fuck am I supposed to push my code or code without the documentation (I can actually, prevent refactoring every time, following the documentation is the good way to go.)

On the sprint review, they will complain about me not committing and pushing the code. (I did commit locally, but can't push, they removed me from the fucking repo) and not done.

Tried reasoning, telling the obvious reasons with them, doesn't work. They come out the second reason of me "NOT COMMUNICATING". Sometimes I can get to git merge from dev to my branch and get tonnes of fucked up code. I reviewed the code, and I can't tolerate it.

Lately, I overheard them mocking and cheering me about to get fired over a zoom meeting (I was in there, they forgot to remove me). Their conversation is about me being a coloniser, a jerk, betraying Chinese ancestors for being not Chinese enough.

I was like: "Why the fuck does their conversation sound like they are tucked in the Qin dynasty?"

Frequently I got labelled as unprofessional.

How is cussing about my ancestors, personal and life a professional behaviour?

I'm convinced that playing the piano has allowed me to type faster and commit keyboard shortcuts to muscle memory faster too. While coding isn't about typing quickly, there's a whole bunch of times when I've had an idea, and had to get that down into code as quickly as possible before I forget it - and that's when I really find fast keyboard work comes into its own.

I was asked to look into a site I haven't actively developed since about 3-4 years. It should be a simple side-gig.
I was told this site has been actively developed by the person who came after me, and this person had a few other people help out as well.
The most daunting task in my head was to go through their changes and see why stuff is broken (I was told functionality had been removed, things were changed for the worse, etc etc).
I ssh into the machine and it works. For SOME reason I still have access, which is a good thing since there's literally nobody to ask for access at the moment.
I cd into the project, do a git remote get-url origin to see if they've changed the repo location. Doesn't work. There is no origin. It's "upstream" now. Ok, no biggie. git remote get-url upstream. Repo is still there. Good.
Just to check, see if there's anything untracked with git status. Nothing. Good.
What was the last thing that was worked on? git log --all --decorate --oneline --graph. Wait... Something about the commit message seems familiar. git log. .... This is *my* last commit message. The hell?
I open the repo in the browser, login with some credentials my browser had saved (again, good because I have no clue about the password). Repo hasn't gotten a commit since mine. That can't be right.
Check branches. Oh....Like a dozen new branches. Lots of commits with text that is really not helpful at all. Looks like they were trying to set up a pipeline and testing it out over and over again.
A lot of other changes including the deletion of a database config and schema changes. 0 tests. Doesn't seem like these changes were ever in production.
...
At least I don't have to rack my head trying to understand someone else's code but.... I might just have to throw everything that was done into the garbage. I'm not gonna be the one to push all these changes I don't know about to prod and see what breaks and what doesn't break
.
I feel bad for whoever worked on the codebase after me, because all their changes are now just a waste of time and space that will never be used.

Look at that. The very fucking smart colleague spent 40 days implementing a repository pattern (WHEN WE'RE USING AN ACTIVE RECORD ORM), breaking stuff left and right. Does he use that fucking pattern at the very least?

Of course he doesn't. And along the way he's making sure to create conflicts with the stuff he broke (and I'm fixing). By the time I fix the merge conflicts of one commit, he pushed 6 of them.

So today, again, I discovered the importance of unitests.
I was solving this performance issue, in which we had a few update actions for multiple entities in mongo, but it took FOREVER to complete, even when I unified it into one bulkWrite command.
Since the unified write did improve performance slightly, and we wanted to move on, we decided to let this bug go.
So there I was committing my changes when I got a rejection from the pre-commit hook since I didn't have enough unitests coverage.
Ok, let's start writing some unitests.
Some unitests also needed to test the bulk write. So there I was comparing expected with actual result, and suddenly I got a huge facepalm.
Apparently some rogue for loop iterated all entities again for each entity that needed update. So instead of getting one update per entity, I got N identical update commands per each of the N entities 🤦‍♂️
Needless to say, fixing this fixed the performance bug entirely.
Thank you unitests and pre-commit hooks!

Linux is an amazing, stable operating system.

Until you decide to upgrade it, then you realise the update failed, your DE is broken and after using Timeshift to restore the system, your GRUB decided to commit seppuku.

I wish my classmates didn’t know that I’m good at programming.

Recently, more and more often I am being reached out to by my classmates (and especially by one individual) about the problems they’re having issues with. For example yesterday, a guy fucked up his Git commit and made a bunch of merge conflicts, so I helped him fix this, which then lead to WinForms having multiple declarations of same objects.

And I really don’t wanna be rude, and I always try to help, for the love of god - stop bothering me every 5 minutes while I code, or at 10 PM while I wanna chill out.

Most of the things they have problems with can be solved by 2 minute Googling and I strongly believe that at the university level, you should be able to find solutions for your problems yourself - especially when you’re a programmer.

i don't think that i'm having a burnout but i think that i'm maybe not so far away from it... several people, including friends, my therapist and also a colleague, told me they see me at risk of sliding into a real burnout.

i've known this for longer that i have a crappy work life balance. the habit of making work the most important part of my own life. thinking about work even in my private time, when i fall asleep, when i wake up in the night or in the morning. the tendency to think about problems, plans, coworkers, not being able to quit work mentally. the idea that i have to prove to everybody at work that i'm awesome. the feeling that, after a work day, i'm just "waiting" at home for the next day, in idle mode, so i can continue working on a problem (like a bug) that's occupying my whole mind. and at the same time, feeling totally empty after work, having no energy. i've lost interest and quit several hobbies in the last two years that once were important for me. and i think one important reason is that i didn't have any mental energy left to deal with that.

another factor for this development was also the pandemic for sure, because for some time, i had no real social life except for that at work.
but more important is probably that i find my job most of the time really fun and am highly motivated. i have the tendency to say yes to everything and to really commit to and own the problems that are handed to me. (right now, however i feel like there's not much motivation left)
then again there is the feeling that what i do is never good enough, i have little self confidence in my own abilities as a software engineer. there's a big discrepancy between how i myself perceive my work and how other people do (not only at work). on a rational level, i know that what i do is at least "good enough", otherwise i wouldn't have this job, and i wouldn't receive this amount of positive feedback from people. but it's hard to really deeply understand this thing, when there are deep-rooted beliefs like "only perfect is good enough" or "your colleagues will be disappointed and get a negative idea of you (and something bad will happen), if you don't give your best"... and there's also this idea that i have to be this super nerdy person who also codes in their free time, reads IT magazines and stuff, because only then i will fit this stereotype of a software developer, and only then i can be taken seriously and be good enough. no matter if this is fun for me or not.

anyway, right now i'm at a point in life where i'm realizing all this not only rationally, but with full emotional impact... :/ my life feels like it's gone stale and empty. i've lost creativity, warmth and human connection and that hurts a lot.

i'm trying to change my life.
one thing that really helps me right now is to talk with people who have (made) similar experiences. can you relate? if yes, how do / did you address those problems? i would really appreciate to hear your stories...

- be any programmer hired to a job
- do some cool thing that helps the business
- gets labeled as a smart programmer and a helpful team member
- get questions and cries of help from everyone at the office
- get burnt out and refuse to help some people
- get labeled as lazy, bad at my job, and having a bad attitude
- gets shadow fired
- cycle repeats

It’s time to burn down the houses of every rich person - and I hope we actually fully commit this time :)

Now we wait and see if they make change this commit message 🤣

Binary searching my way through the git history to find the commit that broke something. 😄

First day back at work and I already want to commit to alcoholism

Happy new year I guess

The coworkers I work with are really smart and capable at their job. PRs with 20+ commits. So guess what? all the PRs are squashed “by default”, so every commit in the history has 100 file changes. Fan fucking tastic. I totally don’t want to kill myself. As an added bonus, all of it is in an Azure repo, so we can’t actually search PRs which is awesome. Plus, all the BE developers want us to do their job! It’s an amazing learning experience!!!

If my stomach start rumbling in the middle of the next zoom meeting, I'm prepared to commit Seppuku on zoom.

Can't take being more embarrassed. 😒

/jk

'I don't want to push this commit yet'

Proceeds to write commit title and presses push.

'Wait, fuck ..'

In only I were 1.15 times faster or had better planning (why didn’t I use the Saturday Sunday at the end of the first week 🤦🏼‍♂️), things would’ve happened differently. I think I’m becoming stupid and my tolerance levels are going down too.

So this happened a while back ..

I was given a code base which didn’t have any changes in the last two years and I was asked to add a feature to this. This was my first task in this new group I was part of. I had two weeks to do this starting on a Monday.

Partway through implementation I realised that the code base is a pile of shit and I wasn’t doing myself or anyone else any favours by shitting on it.

It’s Wednesday. I’ve dealt with many other codebases before but the urge to rewrite this particular one was just unlike anything else. And so I started changing code and before I realised, I modified almost all the important files.
I got sick of this mixed up code and started a rewrite from scratch. It was Friday and I finally had just the basic mechanics of the whole thing working. Now I needed to add all the functionalities and also my new feature.

It should be noted that at no point did I tell any of the superiors I was doing this fearing what they might say and also fearing going back to adding shit to shit.

By the end of the second week, the rewrite was complete and I only had the new feature to add. The rewrite was significantly smaller, compartmentalised and well commented because I did the bloody commenting (where it was not obvious from the code). So on Friday, I was asked about the progress and I told them that it needed some more work and that I need a couple more days. And I got shit for it. I was told it was a mistake giving this task to me and that I am not competent enough. One of the superiors told the other superior about perhaps giving me something more suited to my level. To be fair to them, they were expecting the work in the two weeks to be for the new feature.

And in two days’ time, on Monday (I worked on Saturday and half of Sunday), I finished the whole thing and gave it to them. New feature was working. And I still did not tell them what I did. The tool worked fine so they had no idea what happened because this project had no version control and I pointed them to a new directory with the new code with a first commit.

LMFAO

nice one dude. i'm gonna approve this one time just to show you i'm a good boss.

....of course not.

Almond: "This isn't right, we need to use <blah> instead"
Phil: <Marks as resolved>
Almond: "This still doesn't look to be resolved"
Phil: "IT IS RESOLVED IT WILL BE PUBLISHED AS PART OF MY NEXT COMMIT WHICH I WILL PUSH ON SCHEDULE LATER TODAY"

🙄
...yeah, that makes sense...

That time when I ranted about wanting to commit suicide but not having enough energy to go and buy a gun.

That day in the evening, I asked my GF: "I think that the whole life is a humongous rationalization on top of biological avoidance of death".

She has an untreatable neurological disease. She told me "I found out it's a consensus among different philosophers. It absolutely is. I just prefer not to think about it".

Meaningful commit message !

Just some random thoughts looking at the soon-to-be new filtering feature.

Wouldn't it be nice if DevRant had a QR login like WhatsApp for easy login on desktop?

What about a "top rants" on profiles?

Oh what about an activity mosaic like GitHub's commit timeline?

Just some thoughts I had while punching my punching bag, it can get tedious.

git commit -m “changes” 😈

Creating a git repository and forgetting to commit and push. And not only after ending the project or nearly ending the project...

And fucking commenting stuff

A custom script that makes a Jira ticket, assigns it to me, marks it as in progress, check out a git branch, set the commit title and the Jira title to my command line argument…. Push, open a PR, and fuck it, merge that shit too.

I checked all the corporate boxes and you got the typo fixed.

I am in a situation where I am tired to give suggestions or implement any improvements to the company's app. I am in a situation where I will just do as told, nothing more, nothing less.

Regardless of how many suggestions or improvements I had made, the boss is constantly sceptically asking for "BLACK AND WHITE " proof. Sometimes, something does not require proof but cause and effect. As the application constantly prompts a DataType issue, which is a common bug in this app! I declare datatype the issue went away.

I wonder how this application can go further when they declare every variable as `var`, not using `const` for constant value, and redundant methods everywhere, most methods are not specific (in dart when you do not specify the method, the method become `dynamic`), a long list of nested if-else for something can be easily solved with switch case, etc.

So, today, right now, I will revert every improvement, and keep the original structure. If anything goes wrong, I know why it happens (deep down I will say "I told you so"). I am here to work for food, not to reinvent the wheel.

I'm so exhausted to the point where I will just go along and tell my co-worker "as you wish"

No more me suggesting.
No more me giving ideas.
No more me pointing the mistakes .

I will let them find out themselves is much better than I say it, just to prevent getting unnecessary hatred from them.

The best punishment to give somebody is to never mention their mistake let their ego do the job of consuming them into ignorance and asleep, and never wake them up. Let them commit the same mistakes repetitively until them realised there's no way to revert.

And today, Ubuntu decided to commit harakiri after a self-suggested update.

Shit has been hitting the fan since, like, Thursday. Left and right, bad news and issues. I feel like I'm reaching my limits tbh.

closedAt: 1; DROP TABLE `users`; --

IT CAN'T BE THAT HARD

1) A CONTROLLER RETURNS HTTP RESPONSES, computed using data received from
2) A SERVICE\MANAGER\YOURMOTHER, which fetches data from a DB\external service\whatever

LITERALLY 2 FUCKING STEPS. I'LL TAKE THAT "SENIOR" IN YOUR TITLE AND CHISEL IT ON YOUR FOREHEAD SO YOU'LL REMEMBER WHAT YOU'RE SUPPOSED TO BE WHEN YOU COMMIT THIS FUCKING GARBAGE

Reading JS written by “creative” types:

var myArray = []; //un-sorted values

var SortedArray = myArray.sort();

OrderedHtmlElement.innerText = myArray[0];

Look here if you are going to do it wrong at least commit to the wrongdoing!!!

Intern - adds commit message like "added two files"

Me - Hey Intern, I've added commit lint, please don't disable precommit hooks.. so let's follow standard commit message format

Intern - commits like "feat(app): fix changes"

*later*

Me - Hey Intern, please commit with short meaningful messages like what actual changes were made

Intern - commits like feat(app): whole long story of what he couldn't do and some changes..

Me - 🤦

The current project I'm working with had 3 devs including myself until Jan 1st. Now we're only two, because our lead/manager started to work in other projects and trusted us.

Since that happened, my first PR/Commit of the year was in Jan 5, and it's still open, without any kind of review or comment, as well as my other five (eight in about a day) PRs, while he's making commits directly into develop/main branch, causing conflicts everywhere on what I did...

I'm leaving on friday because the contract is ending.

Good luck I guess.

Burnout is the absolute worst. Feeling like you can’t bring yourself to do anything even though you really want to work on the project. You know logically that you want to get it done and you do genuinely care about the project. But you just can’t bring yourself to commit to it anymore because you’ve given it your all for far too long. You keep telling yourself that you will get us back to work tomorrow or the day after. But rest never feels like enough rest it’s exhausting. Baby steps I guess. I feel like at this point I’ve just developed a habit of putting it off. Time to build a more constructive habit.

One of my coworker change the code from

```
void foo() {
if (condition)
{
}
else
{
}
}
```

to

```
condition ? ifTrue : ifFalse;
```

and add it to changelog

```
- fix bugs // yes with an "s"
- feature added
- some list of the bug fixed.
```

I refer back to the commit, only one Fucking commit and on changes. Bro, what the fuck?

Thanks GitLab.

After I get notifications about the final replies to my 6 month quest of updating someones GitLab README, I didn't expect MY fork to have been modified ( and thanks to that, made ugly / they removed all spacing, vertical & horizontal )

Where the fuck even was the option that GitHub offers where it prevents people from just doing whatever to your shit in a PR?

Why the fuck isn't this a permanent setting for either ( lab & hub ) so I don't have to manually turn it off every single time.

I didn't even think about that option up until now, since the maintainers didn't touch anything and everything seemed fine, but now that it was about to be merged, they suddendly got the bright idea of squashing everything into one commit and that on my fork itself, .. really helpful.

Man I am tired of my company's dogshit software release process.

We have to commit to fucking estimates for 6 months (2 quarters), SQA shadowing dev by 2 weeks, and freaking estimates and work done at the end are not even close. And then we call it a minor release. These shitty estimates are based on requirements that basically say "we want feature x, plz make it work". It's some fucked up agilefall garbage that does not work for shit.

We rush like motherfuckers during the final weeks because estimates are bullshit but we are still expected to be done with every story points which somehow are days instead of other better metrics.

I swear this fucking bullshit has been designed by the board so they could plan their money entries based on the software release.

The only reason this company actually still holds itself up is because the engineers are good at their job.

Go fuck yourself high management.

Reason for rejected pull request on hacktoberfest: "wrong commit message"

...are you fucking dumb or what?

damn robot machine clowns, you wonder why you don't get better at your craft

"we love open source, making it so prohibitively convoluted to participate!!! why won't anyone contribute to our repo?!?!?!"

clowns, absolutely everywhere i swear

Pre commit hooks serve no other purpose than to be annoying.

Runs linter
168 files changed
"Yeh not gonna commit that because other will think I worked on it and send questions my way, I rather live in peace"

Wasted a day as Shitlock Holmes with the build chain.

It would not reproduce the firmware hexfile that had been checked in. Reverse engineering that along with the mapfile to find out the cause, it was a const string that was guarded by an ifdef from another file that was auto-generated as prebuild step via a script that fetched some version control info.

Or, it would have been if the installation instructions had been correct and someone had described that no spaces in the absolute path name of the project are allowed. Otherwise, that shit just failed silently.

I then had to reverse engineer the intended workflow from the commit history in the version control to figure out that the last dev obviously hadn't quite understood the project specific workflow and how the version control interacts with these build scripts.

At least, I finally did get a matching hexfile.

"housekeeping" or "refector" in commit messages..

Ok finally, I can tell now.

There's a college project I'm in with 2 more people that uses Python and AnyLogic (separately).
We also need to write some LaTeX, so as I was already using PyCharm for the Pyshit, I used it for the LaTeX and for Git.
I used it for Git too because I didn't know how it used Git and was worried that if I used the console it didn't recognize something or glitched out or something. And what the hell, it's a mature IDE, what could be so hard or possibly go wrong?

I had to re download the repo a couple of times because between pushes, pulls, merges and commits something happened and the repo ended in a weird state.
These are all the things I do:
Add, commit, create branches, merge, push, pull and delete branches.

So, I hadn't opened in some time. The last time I tried to bring something from another branch, and stayed up late to finish something. I was waiting for my classmates to join the call when I thought something like "Hey, I should commit what I did until now, it worked great.". When I examined the IDE I found out I was in the middle of a rebase or something. I start clicking buttons to at least try to commit. I press "Skip Commit". I lose everything.

What the fuck‽ As you can see in the comprehensive list above, I never do something similar to a rebase. Apparently when I tried to merge a couple of branches, the stupid IDE thought I tried to do a rebase and never asked me to finish it. Why do something I have never asked? Plus, why haven't you prompted me to finish the operation? That's so stupid. I'm never trusting IDEs again.
I was so lit for losing so many hours of work I did a couple of weeks before, I would have to think it and do it all over again because of something I never asked.

We spent an hour looking for a way to recover the lost code.
Why an hour, you ask, if you can use the Local History for that in PyCharm?
Because none of us had used it before and the articles we found said that you had to open it from the toolbar. From the toolbar it was greyed out.
Then I found the option in the contextual menu of the files. Recovered the LaTeX files but on the AnyLogic files, it was greyed out.
I had to open the Local History of the folder containing the AnyLogic file.
And that was that.

I almost faint.
Fuck Python, fuck PyCharm.

We've all been there before mastering git commit --amend, rebase, and squash

Tru-lyfe CTO (CTC) stories:

I spelled a juniors name wrong in a commit message...

Am I an asshole?

P.S.: it was 100% fully NOT on purpose, it's just an alternate spelling of the name, i.e. Jakob instead of Jacob (not the name of course, for privacy purposes, just an example)

Yeah sure random tech recruiter, I like to be emailed directly on my email account that is only visible in that one regretful commit I made several years ago.

Definitely won't make me paranoid about your privacy practices.

On the other hand, it's refreshing to know that I'm somehow eligible for a senior position after 3 years experience

I hate these Mondays. You start really motivated after a nice weekend of seeing lots of old friends, but instead of your own work, you have to pick up the mess a coworker left for you while fleeing into holiday and because that's not frustrating enough, you try to review code from that new senior developer and get confronted with the probably most awful commit history someone ever managed to create.

Of course he also needed handholding and multiple trys to stop breaking like every coding convention we have for branch management...

I am still a junior and I feel pretty disappointed when being confronted with people being so..confused with stuff like git even though they have like 10 years of experience.

While I was still studying, I somehow imagined this industry to be much more...sophisticated?

Happy Valentine’s day to all the lonely gang who are coding while everyone else is getting cuddles.

Like who needs cuddles amirite?

Cuddles are temporary
Your commit however stays in the second arctic vault for 1000s of years

Fuck it... Right in the middle of a commit and github goes down, no fucking early Friday for me you bastards......

So I had got a company called me a week ago and scheduled an interview via Google Meet which was supposed to happen yesterday in the afternoon. I checked multiple times and was convinced that they didn't send me any invitation or any sort of URL to me as they told me they will send me on the day I will be interviewed.

Yesterday I didn't get any URL, I request the URL and asked them whether the interview is cancelled. They saw the messages I sent them but never reply. Until this noon, I receive a long message that they suggesting to put the blame on me for 'being Gen-z bad attitude worker who didn't show up in the interview and not responsible '. I was confused. Why would they make such a statement as yesterday hours before the interview I was sending them messages and emailing them continuously asking for the URL to the interview session in Google meet. I can't join the interview without the URL obviously.

In my defence, I did follow up with them just to get the link to the interview and get ghosted or silent treatments. As strange as this sound, magically their colour was revealed to me after they put the blame on me for their negligence.

Lastly, it is not a heavy chore to admit mistakes. Lucky enough for me that they revealed every plausible red flag to me before joining their team. I definitely do not want to work for a company that put the blame on me whenever they commit a mistake.

If git merge automatically performs a commit to the main branch, how do we add a message to that commit?

I want to commit a crime

for the 3rd time ive tried introducing some version control on a project that really needs it because it has multiple people working on it.

And because the last time my efforts got shut down because in practice people thought it was too much of a hassle to develop locally rather than on the shared development server directly, I made a feature that would let people checkout branches on said server...

Apparently the action of; saving > committing > pushing to your feature branch > merge after aproval, is still too much for people to comprehend; "I think this is too convoluted can't we just keep pushing to the production server to check our work and then commit and push to the master branch"

So I just got pissed and said fuck it, no more git then, I'm not even going to put any effort into changing tooling here anymore, and this is a massive project where we have to manually remove code that isnt ready yet from the staging environment.

Are the people I'm working with just this stupid or am I really overengineering this solution because I think 4 people should not be working on the same file at the same time without any form of version control and just direct upload to FTP.

(and yes, I know I should leave this job already, but social anxiety of starting at a new company is a big obstacle for me)

can someone tell me the buzzwords and trends currently in the market? i want to leave the company, because if not, i am going to commit suicide.

so my mom said that if i try to live away from her, she will not be able to live life normally. if she gets even a false news about me or related to me, she will have a heart attack/ commit suicide.

hello new world. I am just a visitor to you and your opportunities of happiness, i will be going away to my mom's lap after this to remain sad, useless poor and unhappy

I HATE, HATE, HATE, HATE TEEN TITANS GO, IT RUINED TEEN TITANS FOR ME AND I HATE THOSE LITTLE STUPID DUMB VERSIONS OF THE ORIGINAL BETTER TEEN TITANS.
IT SHOULD'VE NEVER HAPPENED AND NEVER EXISTED AND I FUCKING HATE IT AND IT SUCKS!
WE SHOULD CANCEL TEEN TITANS GO AND RUIN THE PEOPLE WHO MADE IT AND DIRECTED ITS LIVES. I AM FILLED WITH HATRED AND RAGE, AND WHEN THEY MAKE THOSE STUPID UNFUNNY "JOKES" IT PISSES ME OFF AND MAKES ME WANT TO COMMIT MURDER! I AM SO PISSED OFF AFTER WATCHING AN EPISODE OF IT, THE CREATORS SHOULD BE SUED.

THANK YOU FOR YOUR TIME AND ENJOY WHAT I HAVE TO SAY.

Believe it or not, I'm new to Github.
I only want to commit the main project files to my branch (not all the automated files that occurred when I exported the project)
question - how do I safely get rid of the visible list of "changed files" that I don't want to commit? Can I just "discard changes", or does this actually do something to the files?

I selected "ignore all XXX selected files (add to .gitignore)" but it has neither added to gitignore nor removed them from the list.

I mean, I could just leave these files in the list of "Changes"...but my OCD doesn't like a list of files in my face.

little typo making my day now, and let to this little "improvment":
$ git config --global alias.vomit commit

GitHub defaults to only allow squash merging feature branches, and suggests that it is "safe" to delete the feature branch that contains all the detailed commit messages at the place where they belong. Losing history, plus creating unnecessary "conflicts" after continuing to work and adding fixes to the same feature branches later.

Sometimes, using git feels like performing a particle experiment in physics.

When I have some added lines staged for a commit, then remove those lines and stage it too, the changes annihilate into no changes at all.

Lines add and lines remove is like particle and antiparticle.
The energy that is released upon annihilation is equivalent to the joy of having a clean commit with few changes.

You deliver a new feature. After the functionality, how do you prioritize?

- having clear variable- and function names
- having meaningful and orthographically and grammatically spelled commit messages
- having a clean commit history
- having perfect linted syntax
- having it covered with unit-tests
- having a wonderful documentation

Okay, I have a desktop and a laptop. I don't think that's surprising.

I do sync the contents of both via git. Also not surprising.

But I thought, hmm, I hate having to do temporary git commits. Stuff like

git add .
git commit -m temp
git push

Just so I can remove it alter via

git reset HEAD^

I hate it because it forces me to force push. So, how do I sync stuff I do not want to commit yet?

Well, I just set up an instance of owncloud. Was easy. 20 minutes and everything is running. Can recommend. But...

For some reason it doesn't work. It syncs stuff just fine... But it also syncs my .git directory... I thought it wouldn't be a problem.

Saves me a pull. Don't have to pull what's synced, right? Also setting up new projects should be terribly simple. Just add it normally. So, git just versions and does pipelines. And I copy everything inside the git directory over.

Also allows me to have more private .git/info/exclude files and hooks...

But for some reason... everything is synced. Dot-files are being synced as well. Everything works... But running git status on one side tells me everything is commited... Doing it on the other side it tells me there are new files.

How is that possible??? I kind of expected that even a branch checkout would be synced... Was curious if that would lead to issues, but I didn't expect it just not recognizing changes. Git doesn't hold projects in memory, does it? Nah, that doesn't make any sense. So, why does git status disagree? Git log is identical... Git status is not...

It makes no bloody sense.

I used `git commit --allow-empty` today, and I almost teared up. It reminded me of my life.

Git is overrated. There's absolutely no good reason that `git add` should be default to call before `git commit`, if people don't want files added that should be the exception not the rule. But where it all really falls apart is mono repos. There's no good way to make a repo inside a repo, which is fucking stupid. There's no good way to clone just a chunk of a repo, which is fucking stupid. And -- just in general -- every aspect of git feels like it wasn't designed to be usable. For instance: there should be a command `git save "message"` which does the default `git add ., git commit -m "message" git push`. Or rebasing, that doesn't need to be so hard at all.

This is just a rant and all, but I'm so tired of git being clunky and poorly designed from a UX perspective. And not supporting mono-repos for shit.

dude why there so many dum fuck in this industry like people who just graduated , and don't know shit about tech or anything but flex and complain about shit just can accept that they don't know any shit this many years fucking noobs nothing like why are they , this don't deserve jobs just make bug and always call for help like why cant they figure out their shit, its just cant just spoon feed they every time, like i dont know what happens to this people after or they just survives in it? just tired of getting my ass on whenever they suck dude they dont know how to commit git lol , but never accepts , i am not talking about one person its like a species now , they dont even try to learn even tho they get jobs for no way , itrsucks

The project needs to make bigger changes to a module. A guy starts doing the changes. It turns out that the task is bigger than we though originally. Team lead has a brilliant idea: you need help. So he'll assign couple of more guys to do the same change.

What's the catch? The catch is that we are now all changing the same files. The code is a mess and tweaks and hacks are needed all over the place. So basically one guy changes the files and others just watch YouTube and wait for him to commit. The it's your turn to change the files and the first guy watches PornHub.

You could all just try to edit the same files at the same time, but we all know how GIT feels about that. You change random lines, he changes random lines, someone else changes random lines, all merges go to shit, nothing works and we spend 2x more time on just trying to get it compiling again.

Cherry picked my first commit today, am proud.

Luckily I'd done all the work for a develop MR in 1 commit and could just cherry pick the 1 commit into master.

Not sure how I'll go with a commit range lol

Hi, Please those of using VScode here, is there a way to commit to Git without "Git Comments" ?, I am asking this question because of my Personal Project.

GitKraken is a piece of shit, there’s no other way to word it.

I’ve been working on a branch on my own for a while committed most things I did except the very last things. Since the branch was quite old I decided to rebase onto develop to be more up to date. So for the modifications I didn’t commit I stashed them, then I started rebase, thinking it was done I poped my stash. Then I saw there were rebase conflict so I pressed cancel rebase thinking it would just revert to the state before the rebase. BUT GOOD LORD NO, YOU GOT IT ALL WRONG…

No it just deleted my stash in the process as well 🤦‍♂️

Git: "Your local changes to the following files would be overwritten by checkout. [...]
Please commit your changes or stash them before you switch branches.
Aborting"

Fucking nitpicking, that's not "Aborting", that's meant to be:
"Dear user, would you like to overwrite your current changes, even more so as you are currently in a so-called detached head state anyway, as you obviously just checked out an old tag to try a temporary rebuild of an old project state."
Yes, the build targets are checked in, as this can be very useful in some scenarios.
It's just! some! CSS! from the SCSS!
Stop "Aborting"!

Is there a Git client for Android that WORKS (without rooting)?

I've seen quite a few but would love your recommendations. Looking to just pull, push, commit.

Would probably connect to Github, maybe Bitbucket or Gitlab

It do be like that sometimes.

My day:
-continue working on a project which i haven't -committed for 3 days
-add 20 lines of code
-mistakenly deleted the route file
-restore the file (thinking I'm saved)
-open the file
-50+ lines of code gone