Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
![](/static/devrant/img/pipeless-devrant-banner-white.png)
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "rip logic"
-
> In office for first time in awhile
> Run into group of 4 people I don’t recognize in far cubicle corning laughing in hushed voices eating of an impressive spread of food
> See me and immediately look at each other with panicked expressions
> Confused, I put my hands up to indicate I come in peace
> They relax a little and say they thought I was from HR since they didn’t recognize me
> Ask why HR seeing them would be such a big deal
> They say their potluck is not “sanctioned”
> …?
So apparently HR just could resist ruining one of the only good things about coming into the office and one of the coolest things about the company’s culture. At least once a month there would be a giant potluck where everyone would bring some home cooked dish and share it. I can’t tell you how amazing these are in Canada, 50+ plates of authentic food from all over the world.
Unfortunately HR didn’t agree as 1. They didn’t cook so felt bad taking food. 2. Nobody asked them permission to put on these events they just happened organically. 3. Some people were bringing in food that they felt was culturally inappropriate (ie. caucasian guy bringing in homemade sushi).
HR recently banned all “unsanctioned” potlucks and all future potlucks needed to be approved through them with the following stipulations. 1. You could participate without bringing something by donating to HR $10 2. If you brought something you still had to give HR $10. 3. Things you brought in had to be approved by HR
Naturally the first and only potluck under these rules only 4 people brought something in as many couldn’t get their dishes approved because HR didn’t like what they were planning to bring (started out as being because culture and turned into HR just being picky), most just brought $10 so there wasn’t enough food to go around and so after HR took a giant group photo to post on the company’s social media accounts to show off how good the company’s culture is most everyone had to go out for lunch. HR sent out an email later that day exclaiming what a huge success for charity and the company brand the potluck was and they can’t wait for the next one. (I have the HR communications email marked as spam so I never saw the email). Nobody ever organized a sanctioned potluck after that.
However people still missed cooking and sharing their favourite recipes with one another so potlucks still occur but they are now very small, secret, invite-only, hush-hush affairs.
…What in the ever loving fuck22 -
My new favourite commit message:
"All changes as of 18th Sept"
How tremendously useful? There I was looking to know what changes were made to enable a feature / service, thought I could look for that in the commit message, but no you've given me a much more efficient way of finding out.
I simply need to download the contents of your memory, find out what date you made a change, and then dig through the massive commit to find the piece of info I need.
Forget experience using Git features, managing merges, following Git flow, or even any other SCM ... how can people be so tick when it comes to recording what they've done.
Heres a little cheat sheet for those struggling:
- Commit message
Describe what you actually ****ing did. Don't tell me the date or the time, thankfully Git records those. Don't tell me the day of the week, if I need to know I can figure that out, just tell me what ... you ... did.
- Feature branch names
Now this is a tricky one. You might be surprised to know that this isn't in fact suppose to be whatever random adjective or noun popped into your head ... I know, I too was shocked. The purpose of this is to let other people know what new feature is being worked on in this branch.
- Reusing feature branches
Now I know you started it to add some unit tests, and naming it "testing" is sort of ok. But its actually not ok to name it testing when you add 3 unit tests ... then rip out and replace 60% of the business logic. Perhaps it would have been wiser to create a new feature branch, given you are now working on a new feature.2 -
My leader was yelling at me cause i couldn't relate two tables, the first has a decimal(15,5) PK and the second has char(20) as a FK.
WELL TELL ME HOW THE FUCK SHOULD I RELATE THEM YOU STUPID FUCKING CUNT ??
Decimal !!! I could not believe my fucking eyes ! And Fuck keeping the clients satisfied!
Well, sorry, i just wanted to let it out.1 -
Having a meeting with an old client of our company's today, guiding him through the deployment process for his front and backend, because he thought that we were withholding information, and at one point in the call he asks me if the './' at the beginning of the deployment script was a special security measure put in place by us... 😂