Move fast and break things.
Merge vulnerabilities.
Double the work.
Merge code without tests.
Anything, but don’t let code become stale.
I dunno but xtreme programming sounds like something straight outta Musk’s wettest teenage day dreams.
Imagine if you will: You have a red button and a green button. You are allowed 10 seconds to review the code before rejecting or accepting & merging. Think fast.
deleted by creator
Modern agile is just waterfall with steps.
Wait… waterfall is waterfall with steps 🤔
Agile just adds routines and extra steps
Didn’t knew KenM was on LinkedIn.
Developers: “Move fast and break things.”
Things: break
Developers: surprised Pikachu face
Except instead it’s: Developers: fuck ops, they stuck at their job
The “send it” school of PRs.
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.
removed by mod
It can work if you have a test zone and only a small amount of people work on a given code base.
Also checks to ensure the code compiles and tests pass before merging, as some quality gateway.
Having a hard time determining whether this is sarcasm or not. Then I see the phrase “JavaScript Engineer” and become doubly confused.
I think the latter makes clear that this is a joke account, doesn’t it?
Node: “Am I a joke to you?”
Yes.
Yes.
I don’t think it’s satire, this guy is actively defending this on Linkedin: https://i.imgur.com/SlJPG85.png
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.
That could still be trolling. But LinkedIn is so full of utter garbage like this that it’s believable
I don’t think so. I just made a screenshot of one random convo he’s having about this, but there’s loads more in a similar fashion.
And all of his other posts besides this one seem legit on the surface.
So it would be pretty weird if he randomly has a very bad take, and then just claims “Lol this was a troll post, gotcha!”… That’s pretty much the 4chan defense when you get called out - “Haha guys, I’m actually not r-worded, I’m just trolling!”
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.
Test it? Meh. Just ship it.
It compiles = it goes to prod!
This is why I include those preservative libraries in my projects. My code doesn’t go stale for a whole three weeks longer.
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 --mirrorYes, especially the newbies who don’t know what they’re doing.
Keep everyone awake and on their toes.
You’re not truly part of the team until you cause a massive outage.
New employees are responsible of at least 75℅ of documentation clarification and process overhaul.
I’m totally on board with process overhaul. Ours was stupid when I started, I said it was stupid, and nothing changed. If someone else comes in and can say it’s stupid more convincingly than me, that’s great.
I honestly wouldn’t see this as a problem. But if you break something it’s up to you to fix it. But we also don’t do CI. We release features in batches after they have been tested and seen to be working.
I don’t know if sarcasm because there are actually maniacs like that in this world
Stop transfering people from sales to engineering!
But Elon’s annoying!
At my company we’re so agile that we directly deploy branches from developers’ local machines to customers for A/B testing.
Call it “container orchestration” and charge an extra 20% to the customer
As one of our most important customers, we’ve greenlit you for our cutting edge early access. Most people need to wait weeks for the features you get today!
We’ve been doing that the wrong way, offering a discount if they were willing to try the early features.
This is the big money reasoning that I should suggest to the bosses.
Pete was Heard, but was he Listened To?
