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.
Something like that happened to me yesterday. I reviewed one PR, then some Important Guy came in and said:
- it is nice you reviewed my work, but we need to push this to production right now.
- just fix these things, I described you how. Just copy/paste these snippets
- these are cosmetics, I don’t care
- “cosmetics”, huh? Your shit may just crash
- gfy and push this to production right now
- well, ok
Of course, lack of these “cosmetics” caused crash in production. It’s my fault of course.
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.
Having a hard time determining whether this is sarcasm or not. Then I see the phrase “JavaScript Engineer” and become doubly confused.
I really wish LinkedIn would add an anonymous cringe emoji. I would use it on like 90% of the content on that site.
Stop transfering people from sales to engineering!
But Elon’s annoying!
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.
Do we have a Linked In Lunatics sub on Lemmy?
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.
