Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "commit"
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.11
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 😄22
Rename a variable for clarity.
Third-party lib behaves differently, breaks things.
Change the var names back.
Stash changes and checkout previous commit.
Diff with stash.
No notable changes. (some comments, ...)
Checkout branch again, pop stash.
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?16
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.5
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!2
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.19
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.38
nice one dude. i'm gonna approve this one time just to show you i'm a good boss.
....of course not.6
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.3
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...4
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".7
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
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"
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 - 🤦5
Fuck corporate managers who set goals without consulting the team as to what they can commit to!! "These are the goals that you need to commit to and you need to get them done in three months!" ... New team. Members come and go (even I replaced one). Low cohesion. Many dependencies. Unclear goals. A PO who's certified in many different ways, but has no damn idea what to do. Sure, let's get this shit thing done in 3 months.. aaaand we're late 6 months. Nice job. Stupid fuckers. I'm so glad I'm just consulting on this project and not a member of this chaos organization.2
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.
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.1
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 years3
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 experience1
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?2
If git merge automatically performs a commit to the main branch, how do we add a message to that commit?16
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)7
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.1
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.4
little typo making my day now, and let to this little "improvment":
$ git config --global alias.vomit commit
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.10
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.3
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.2
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 documentation6
Every time I think it's gonna be different. "This time I'll make a clean repo!". Then the frustration hits and the first "fucking piece of shit" commit creeps in and you push it there. One more repo soiled..5
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.2
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 🤦♂️6
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.11
-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 gone2