Earlier quoted context omitted.
No it was g+
Or one of the twelve messaging apps that got ignored by the masses because no one longer trusts their products
Right. Everyone is using duck duck go , Proton mail and vimeo outside of HN.
Why do developers at Google consider Agile development to be nonsense? (2016)
191–200 of 239 posts
Re: Why do developers at Google consider Agile development to be nonsense? (2016)
#192Earlier quoted context omitted.
Or one of the twelve messaging apps that got ignored by the masses because no one longer trusts their products
Right. Everyone is using duck duck go , Proton mail and vimeo outside of HN.
Allo me on Google Messenger. Or was it Android Messenger? Anyway, my Duo handle is xxHangoutsDudexx. We start a Google Talk session later.
Re: Why do developers at Google consider Agile development to be nonsense? (2016)
#193"The word 'agile' has been subverted to the point where it is effectively meaningless, and what passes for an agile community seems to be largely an arena for consultants and vendors to hawk services and products." - Dave Thomas (Manifesto for Agile Software Development author)
Re: Why do developers at Google consider Agile development to be nonsense? (2016)
#194The hardest part of working with really smart people is that they can rationalize pretty much anything. Worse still, if they have been on the project for years and you’re the new guy, you’re working from a deficit of knowledge and they’ve had plenty of time to cook up a “coherent but wrong” model of the universe. The only thing that saves a group like that is humility. Trying to see the system through the eyes of the…
You probably know this, but a lot of studies back you up. Being smarter doesn't necessarily make you more likely to be right, but it makes you a hell of a lot better at rationalizing your position and persuading others. Also, that comment about the "old guy with an inferiority complex who sneaks one really profound comment in every meeting" really hit home. We have that guy on my team too. You have to wonder what's g…
I would say that being smart does make you more likely to be right, but overall, your rightness is not the percentage of cases in which you were right, because some bad decisions are far more (and unexpectedly) highly weighted than others when it comes to an overall outcome.
Where smart people fail is because they were "right" in a limited, seemingly appropriate context and it turns out that in a larger context, it didn't matter.
Re: Why do developers at Google consider Agile development to be nonsense? (2016)
#195> This type of innovation takes significant up-front design time, and working on components over longer than one week iterations. Because the projects have such simple external interfaces, and so much internal complexity, much of the work is not even visible to “customers”, so there is no way to write customer visible stories about it. This type of software takes 8–20 months to deliver the first working version to th…
Your post is implying a few things that compel me to ask:
1) There is a pure relative ranking firing cut-off at Yahoo regardless of how well the people at the bottom do?
2) Does Yahoo make this clear when they hire you?
3) Your manager was so incompetent that he could not judge your performance outside of customer facing product?
4) A company as big as Yahoo thinks its going to survive alienating the personality that looks for big company culture with that kind of "make the cut" performance review?
Re: Why do developers at Google consider Agile development to be nonsense? (2016)
#196There is unfortunately a large gulf between “agile” and “Agile” development these days. The former refers to development generally in line with the agile manifesto, with processes tailored to the needs of the team and the project. The latter is a buzzword used by consultants to convince management to put their favored bureaucratic method in place, usually some variant on the scrum system.
Koolaid.
Re: Why do developers at Google consider Agile development to be nonsense? (2016)
#197> This type of innovation takes significant up-front design time, and working on components over longer than one week iterations. Because the projects have such simple external interfaces, and so much internal complexity, much of the work is not even visible to “customers”, so there is no way to write customer visible stories about it. This type of software takes 8–20 months to deliver the first working version to th…
Your post is implying a few things that compel me to ask: 1) There is a pure relative ranking firing cut-off at Yahoo regardless of how well the people at the bottom do? 2) Does Yahoo make this clear when they hire you? 3) Your manager was so incompetent that he could not judge your performance outside of customer facing product? 4) A company as big as Yahoo thinks its going to survive alienating the personality that…
Stack Ranking at yahoo is no more, at least officially as of a few years ago.
Re: Why do developers at Google consider Agile development to be nonsense? (2016)
#198Earlier quoted context omitted.
That’s by design. Keeps the workforce young and insurance cheap.
Why would companies prefer cheap insurance over productivity? If they want to pay less, they can just pay less. People would rather get paid less than get fired.
Productivity is hard to measure. Insurance cost is easy to measure.
Re: Why do developers at Google consider Agile development to be nonsense? (2016)
#199Earlier quoted context omitted.
That’s by design. Keeps the workforce young and insurance cheap.
Less cynically, it also increases the odds of finding good employees. A "bottom 5%" worker is statistically less likely to suddenly rise to the top of the pack than a new hire is to produce at that level initially. And, more cynically, that remains true even if there's significant measurement error in identifying that 5%.
That's true if the performance ratings are cost-free and fairly accurate. A company where firing is based on misconduct and promotion is based on achievement, rather than basing both on quarterly reviews, might actually have a better chance of finding good employees, and perhaps more importantly, retaining them.
Re: Why do developers at Google consider Agile development to be nonsense? (2016)
#200Earlier quoted context omitted.
> How are programmers different from bus drivers? In that programmers are supposed to be creative, over-deliver, etc. You'd worry if a bus driver got from A to B in half the time driving twice as fast suddenly. But you'd be OK if a programmer you've asked to design system with features A, B, C and performance P, also delivers features D, E, F and performance 2*P without being asked!
> In that programmers are supposed to be creative, over-deliver, etc. Like I said, I don't want the programmer in charge of the software that manages my financial or health records to be creative or over-deliver, quite the contrary. I'd add personal-data to the mix, and now I've covered a huge chunk of SV companies. I think that the era of "move fast and break things" should be over by now, unfortunately relatively p…
You'd like your financial and health records to be managed by average-quality software? That is, software that's full of bugs, confuses its users into making lots of eyes, and is insecure? I'd rather have them managed by file clerks on paper if that's what's on offer on the software side.