Are they really bad apples, or just the first ones to notice the team is headed for a failure? Poor management will eventually effect attitude changes in everyone on the team; the "bad apple" is just the team member who is most easily frustrated.
Tag lines of the jerk include: Are you kidding me? Have you ever actually taken a [fill in technical area of expertise] course? Do you have any idea what you’re doing?
no wonder whole /prog/ population is NEET. You're all jerks.
Name:
Anonymous2015-07-10 7:20
Maybe the problem is expecting the workplace to be a social gathering. Perhaps the fault isn't with the person who called their code shit, but with the shitty coder who sulked about it for the rest of the day and didn't get anything done instead of trying to make it better or deciding that the other person is just a cunt and ignoring them, then getting on with your day.
I hope this gets applied iteratively. Every month, the team votes on who gets kicked off the island fired for not being a team player. Voting blocs will form and politics will rule, but it will cause everyone to be bitter and suspicious, and kill the company. Then those louts who couldn't just do their fucking job will starve to death and society reaps a great benefit.
Name:
Anonymous2015-07-10 9:14
>>4 Yes, people are often the problem, that's the reason we despise them. But jokes aside, you are right imo.
Name:
Anonymous2015-07-10 10:21
this is racist against functional programmers!
I was born coding lambda how dare they ask me to program in the WORST LANGUAGE EVER java
Name:
Anonymous2015-07-10 15:16
If ``The Jerk'' made an operating system, it would be called LoperOS.
Agile is bad. Imagine a construction site with agile. There would be no engineers, only a a bunch of workers running around doing whatever they felt would be best. Instead of following a floor plan, they would just put walls where they felt was best. The building owner would be on site at all times directing things instead of an overseer. If they ran out of insulation they would just start packing gravel and sand in the walls. The workers spend half the day in meetings about what they are going to do, but nothing is decided in them because no one can tell what the fuck is going on. In the end, the building owner gets a shitty building that falls over when he breaths on it, and the contractor is left to sort out hundreds of millions of change orders and takes twenty years to come up with an invoice.
Agile is an apping paradigm, where the goal is to fling as much feces onto the fall and see what sticks. You don't see the most successful open source projects using fucking bento boards and ichigo diagrams that are made at 9AM and ignored by 10AM. Yeah, waterfall is shit because problems often arise that are non-obvious, but it doesn't breed the culture of idiocy and chaos that Agile does. And that's fine, because no one actually follows waterfall anyway.
Then again, Agile wouldn't be much of a problem if it weren't for people being dipshits who fuck it up. But that's still Agile's fault for not taking cunts into account, because there's always going to be jerks and downers on the project. It would be better to use a process based on reality than throwing your hands up in the air and beseeching God to send you better workers.