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.
That could still be trolling. But LinkedIn is so full of utter garbage like this that it’s believable
I think the latter makes clear that this is a joke account, doesn’t it?
Node: “Am I a joke to you?”
Yes.
Yes.
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.
Yes, 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.
Who me? No, must be someone else with my name you’re thinking of.
Don’t hurt their morale!
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
Oops boss just did a
git push --mirror
Stop transfering people from sales to engineering!
But Elon’s annoying!
I really wish LinkedIn would add an anonymous cringe emoji. I would use it on like 90% of the content on that site.
The best thing you can do with that shithole of a site is ignore it as best as possible. Don’t give them any engagement. They’re no better than rage-baiters on Reddit and TikTok
I wouldn’t even do it anonymously if I still had a linked in account
I’m having a hard time figuring out whether this guy is a fucking moron or a fucking idiot.
pete’s a fucking genius
Exactly, this is how you pay off your mortgage
Both?
No integration is as continuous as editing in prod.
Unironically worked for a company that did this. Don’t test it, don’t even run it, just put it in prod.
Me too, it was glorious that time someone accidentally pushed on a Friday evening and stopped production lines for the following week.
I miss when internet services was literally down because it was being developed in place
Amateur. You want real performance? Code in prod. Literally could not be better for collaboration to have the whole team working directly from production servers. Best part? You get INSTANT feedback.
Another benefit is you never have to worry about merge conflicts
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.
My old boss (at a sturtup with some ten ppl) loved to do this. When you’re done with your work, merge to master. Boss-man would then revert the commits if he didn’t like the result. Since the branches all were merged, no-one knew what was actually in prod. Fun times.
🫠
I just commit directly to master with auto-deploy like a real cowboy, yee-haw!
Why review at all when the users will do this for you? Merge, deploy and move on. If it’s broken they’ll tell you.
I’m definitely going to start doing this at work. We don’t want our embedded firmware for medical devices to get stale.
Right? Who needs a QA team when you can use real live customers for testing
It’s the Microsoft way.
If somebody actually did that it would be grounds for removing their privileges to merge into master. THIS, THIS is why the JavaScript ecosystem has gotten so bad, people with mentalities similar to his.
‘i help JavaScript engineers become framework architects by getting them forcibly reassigned.’
Do we have a Linked In Lunatics sub on Lemmy?
This is why I include those preservative libraries in my projects. My code doesn’t go stale for a whole three weeks longer.
Better yet just edit files live on prod from Notepad (not plus plus) over Samba for “xtreme moral” boost
The amount of times where I had to fix things in live production servers is not a small number. Then again, we are only humans. Backup often and you are golden.
