Details
Joined devRant on 5/13/2017
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
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
quit that shit show before it blows up
-
MANIPULATOR OF PUPPETS ARE PULLING YOUR STRINGS 🤘🤘
-
John.
-
I was in a similar situation with a boss who was lazy and had no idea what he was doing and was blatantly adamant about it.
> Get on LinkedIn
> Find recruiters and spike up your price
> Get a new job offer
> Drop all tables
> GTFO -
What's that OS ? Ubuntu ?
-
@don-rager i've been working as a FE developer for 3+ years, in my previous companies I either didn't get a chance to develop backend or didn't really identify with the backend stack they were using (ergh .NET).
My current work offers me the possibility to slowly start developing in rails, hence why :P -
The kind of feedback I usually give when I get modals in my face about rating an app..
-
@12bitfloat I push alot, the fear of an HD frying mid-work is real !
But yes, rule #1 of force pushing is know what you're doing, rule #2 is pulling main branch before -
@12bitfloat if you never force push, you can't rebase your branch against master.
This leaves you with merge commits, a dirty and confusing history and the dissaproval of your peers. -
@ElCapitan question was not for me, but no. Force pushing is not necessarily a bad practice, it's more of a safeguard against accidentally fucking up the repo for everyone else...
But that what git reflog is for ❤️ -
Or better yet,
git rebase -i HEAD~<number of commits>
This gives you lot's of control over the commit history, but you can edit every commit message in that upstream branch.
Then, do a git push --force -
@Ranchu programming dopping*
-
@alexbrooklyn not really, we have a separate "architects" team which barely touches the codebase.
Most of the dev team is negligent with PRs and considers them a hassle, and usually the PRs are not even looked at before approval. Luckily my team (React/FE) has the habit to properly look and examine the code. + The front end team usually has 3 branches + 1/2 feature branches per repo while the other teams have dozens of branches open.
So yeah, resigned :) -
@Tayo Resigned :)
-
@010001111 i feel you
We have 4 developers with 81 branches and last week we had a company wide announcement in which they decided to end PRs -
I feel you.... 81 open branches.
Looks like the Pride flag -
📌
-
Cuz 'u cant see me ?'
-
gtfoutta that place :)
-
As a bitcoin HODLER, I do.
-
@ennerperez I pay for the individual subscription and have no issues with private repos :D
GITKRAKEN ! -
@pandas thanks :) lemme know what you think.
-
Spotify
-
I work with a dutch company from 'S-Hertogenbosch. My condolences go out to the families and friends of the victims.
This shit is not normal, specially after the fucker from /Pol/ raided churches in new zealand.
It seems the perpetrator is of Turkish descent. Just ffs don't forget that there are racist fucks on both sides and don't hate on a community who is also grieving on the other side of the world. -
@M1sf3t As a linguist, I was immediately triggered.
-
YOUR*
FFS Figma.... -
@DataJockey was actually expecting this
-
Still waiting for the code.
Also, shouldn't that be a private matter, which will !age well in 10 years like someone said above ? This makes you both look like kids, and you look like an attention hungry one... -
-i :port
-
@lxmcf not really a fan of the pseudo code business, but I admit there are advantages to an engine like that, mainly in map creation