Hacker Newsnew | past | comments | ask | show | jobs | submit | PaulRivers's commentslogin

No, theen who don't consider it get laid while the men who do consider don't get anywhere.

You'll notice these themes are always repetively "sex bad!" with no "sex good" elements ever.


The agile methodolgy claimed we needed to switch to it to increase quality.

Quality got worse.

In this scenario it's the fault of agile, as the reason for doing agile was to increase quality.


"The agile methodology" doesn't really make claims about what a specific group of people need to do.

It's a tool/methodology that can help you increase quality.

If quality isn't a priority, a methodology that helps to better align your work with your priorities isn't going to improve quality.


No it's not lost. It gets the same though longer winded results of saying "no". The b.a. product owner complains to your manager that you're not a team player and you get into trouble with your boss.

Even if that didn't happen you're never going to win, because the b.a.'s have no other job than playing this verbal judo, while you also have to spend your time getting conplex technical things to work. You're like someone who goes to a karate class twice a werk fighting against someone who's life is dedicated to training.


I'm highly suspicious that every time there is one of these threads, agile-consulting companies simply monitor the web for them and send a bunch of posters over to make up fictional srories about how agile is going great where they work.

I've never been in an environment where you could say no to the b.a.'s under agile either. And I've tried being more articulate as well and that just results in the same claims to your manager as "no" does that you're not being cooperative, a team player, etc.

I'm pretty sure after working several places that did agile that most of these "worked great for me" stories are made up.

I've never met another dev in real life who did something other than agile and preferred agile.


> Trust your engineers to do the right thing on their own and they might just surprise you.

I mean - trust but verify. While I largely agree with you it's always demotivating for the team to realize one dev is doing no actual work and getting away with it. Obviously not good for the business either.


Manipulative people copy commonly know (often stereotypical) stories as cover to whatever they're really doing.

Real stories, and manipulative fake stories , would be almost exactly the same, because one is copying the other. The manipulative stories are often slightly more realistic or interesting as the person telling it has had a second chance to refine it from the original version.


Yeah, this article was very "See if you're a good person like me you'd never go nazi".

If the SJW's taught me anything it's that the people loudest yelling that they're the good people would be the first people to go nazi. It wouldn't be the same nazi's nowadays - their uniforms would be different, their slogans would be different, the group they scapegoat all their problems on would be different.

But they'd still be plowing through imprisoning and killing people who fit into their nearly arbitrary category not caring what kind of people they actually are because "their group is the reason why bad things happen!".

They'd simply go on their facebook feed, be told who they should hate this week, and gleefully post about how they're being put in camps to slowly die, all the while convinced they were doing the right moral thing.


Ha, that's great!


"Whenever I've had a whiteboard programming interview, it's always been a trivial problem"

I've had a few, and it's never trivial problems. Here's a trivial problem: - Write a method that takes 2 parameters - an Integer, and a list of Integers - and return a boolean indicating if the int param is in the list of Integers.

Instead of something actually simple like that, it's trick questions designed to appeal to the interviewers desire to appear smart and clever.


"I think that the perception that it's just a hazing process comes from a failure to look at it from the company's perspective."

Actually, speaking of looking at it from the companies perspective, in 2010 google and several other big name silicon valley companies were successfully sued because they all agreed with each other not to cold call each others employees to try to recruit them. They actively worked to try to make it harder to switch jobs from one company to another.

Right after that, they started doing whiteboard interviews, which serve the same purpose of making it painful to switch companies, but without the risk of being sued.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: