Move fast and break things.
Merge vulnerabilities.
Double the work.
Merge code without tests.
Anything, but don’t let code become stale.
You must log in or register to comment.
Having a hard time determining whether this is sarcasm or not. Then I see the phrase “JavaScript Engineer” and become doubly confused.
I don’t think it’s satire, this guy is actively defending this on Linkedin: https://i.imgur.com/SlJPG85.png
I distinguish four types. There are clever, hardworking, stupid, and lazy officers. Usually two characteristics are combined. Some are clever and hardworking; their place is the General Staff. The next ones are stupid and lazy; they make up 90 percent of every army and are suited to routine duties. Anyone who is both clever and lazy is qualified for the highest leadership duties, because he possesses the mental clarity and strength of nerve necessary for difficult decisions. One must beware of anyone who is both stupid and hardworking; he must not be entrusted with any responsibility because he will always only cause damage.
– Kurt von Hammerstein
LinkedIn is Facebook for that last type.
That’s a relief because I thought I’d stumbled into LinkedIn Lunatics for a hot second.
Linkedin is for lunatics. Just a bunch of goobers giving digital handjobs to each other.
Wow, of course he’s pretending the response is a misrepresentation of his opinion instead of defending it in good faith.
I think the latter makes clear that this is a joke account, doesn’t it?
Having to go through the process of merging hurts morale and slows performance. Give everyone on your team the right to force push to master.
Oops boss just did a
git push --mirror
Do we have a Linked In Lunatics sub on Lemmy?
Stop transfering people from sales to engineering!
But Elon’s annoying!
What does “stale code” even mean in this context?
Does that mean it falls behind stable? Just merge stable into your branch; problem solved.
Or is this just some coded language for “people aren’t adopting my ideas fast enough”. Stop bitching and get good.
Developers: “Move fast and break things.”
Things: break
Developers: surprised Pikachu face
I really wish LinkedIn would add an anonymous cringe emoji. I would use it on like 90% of the content on that site.
No integration is as continuous as editing in prod.
Let the users do the testing
Oh hey a fellow game dev, how long you been in the industry?
I kind of with the sentiment. Review pre merge though, but only block the merge if there are serious faults. Otherwise, merge the code and have the author address issues after the merge. Get the value to production
Get the value to production
Ugh, not this SAFe Agile ™ cultist bullshit. The “value” is working, bug free code, which you get when you put it through review and QA before it gets to production.
There is no value in spaghetti piled on top of rotten spaghetti. Tech iCal debt is real and if you’re just shippin it and plan to fix it later, y’all gonna have a bad time. Nothing more permanent than a temporary workaround.
have the author address issues after the merge.
Hahahahahahaha. Sorry, you’ve merged, next ticket, PM needs shiny results for execs this QBR!
This is how bug backlogs grow.
Yeah, I see your point. Maybe my employers are different, it’s never been an issue explaining why the ticket isn’t closed just because the PR is merged
Oof, I felt this
Nothing improves morale like the on-call having to unfuck production for the third time that hour because mUh VeLoCiTy decided code review and testing in CI was too slow.
Techbros are fucking cultists.
Test it? Meh. Just ship it.
