My Experience at Apple
771–780 of 840 posts
Re: My Experience at Apple
#772any mirror for reading the original content?
Re: My Experience at Apple
#773Re: My Experience at Apple
#774Re: My Experience at Apple
#775Re: My Experience at Apple
#776Earlier quoted context omitted.
... until you find they finished first by cutting corners and delivering something that is only capable of passing the scant unit tests. Then the "zero knowledge" psychopathic management style doesn't seem so smart.
It isn't a zero knowledge style. It is an experimental, or knowledge-acquiring style. To employ that approach most effectively it makes sense to have competing teams with purposefully different styles.
No knowledge is going to be acquired that way.
It's a manager who has decided understanding the nature of the work is beneath him, when he can deploy someone else's money to wind up some insects that will run around doing the work for him and watch them struggle against each other. Literally zero knowledge, before, during and after.
When whatever result appears they will not analyze the meaning of what happened beyond punishing some insects and rewarding others.
Re: My Experience at Apple
#777Does anyone have a copy of the story? It was deleted
* https://news.ycombinator.com/item?id=25611235
Re: My Experience at Apple
#778Re: My Experience at Apple
#779If it was me, I wouldn't have lasted so long. No way. I worked for mid size companies, and I found envs quite toxic, but this is a whole new level for me. I'm glad I decided a long time ago my life worths more than working at any $faang.
That’s because you aren’t on a visa ?
Re: My Experience at Apple
#780Earlier quoted context omitted.
I disagree that (internal) competition unequivocally leads to better-than-you mindset. If done properly, in an open and sharing mindset – one might call it scientific, with expectations and criteria defined up front and with the projects objectively compared against the criteria, then it will work. I have also this work. It takes effort to come up with criteria and metrics beforehand but that is what makes it differe…
> If done properly Any guidelines? What to think about
In addition, for each experiment you need: a defined time window, up front criteria by which to judge the results, optionally form solution ideas together, give all teams the same amount of time and opportunity, after the experiment is finished each team presents their solution in a fact based manner in perspective of the criteria. After this the teams rotate and see what they can improve on their original solution with the remarks and information from the other tracks. After this decide together or with an informed captain which solution to continue. After this there should be no hard feelings, no personal consequences. Each team should be treated equally because they all contributed to the end goal. This is what will give you a fair competition and help create team safety.
This can be done on all kind of levels, between one day for something small and two/four weeks for the bigger challenges. Making it bigger than this will incur a lot of stakes/vested interest.