91–100 of 145 posts
[deleted]
Oh, how I know this. The worst part is, this tends to stay with you in other jobs. In takes time to consider the possibility that maybe bringing a new idea to the table isn't a risky affair. Now, others already advised you to quit the job — but that's obviously not so easy. But be careful, and if you can, find another outlet for creativity, because this can seriously damage both what you can offer to other companies,…
Earlier quoted context omitted.
[deleted]
"Whether you think that you can, or that you can't, you are usually right." - Henry Ford You can start to overcome this by telling yourself that your are amazing at interviews. Eventually you will start to believe it. At the end of the day an interview is just explaining why you are awesome, and then getting the interviewer to tell you why their company is awesome. I hope you can get out of this toxic environment. No…
One tradition I really appreciate at Google is the post-mortem. Any serious outage or bug will be followed by a detailed post-mortem detailing a timeline of what went wrong and why. Sometimes this will go as far as establishing a "war room", possibly for weeks, dragging in people from a number of different areas to address a particular issue. It's not about pointing the finger or otherwise apportioning blame. It's ab…
And even if there is justification for additional process, they should let the ops/dev teams come up with ideas/solutions themselves: we know our tools and teams best.
Earlier quoted context omitted.
[deleted]
Just as the parent post said: Interviews are hard because there is extremely low correlation between what is asked in Interviews and actual job work. I firmly believe the system of asking stupid algorithmic trivia is hackable and should be hacked because it is a broken rotten system that keeps incredibly amazing hackers out. There has been a ton of stuff said about interviews so I will keep this brief: 1. Get a githu…
Many people can't complete the first item, something that would take me 5-10 minutes. I feel like it's about the equivalent of fizz buzz, but scalable. It also respects their time, since I don't ask them to sacrifice a weekend day to make an app for me or similar and by the end of the interview series and a huddle, they'll have an offer or not.
Earlier quoted context omitted.
[deleted]
Beware. If the environment is as bad as it sounds, the issue may get forced on you sooner than later. Something will draw the Eye of Sauron onto your boss and he will need to fire a scapegoat or get blamed himself. As the guy who doesn't give a crap you'll be both threatening and vulnerable. Getting fired can turn out to be a good thing in the long run but it's stressful and best to avoid if possible.
Earlier quoted context omitted.
[deleted]
Just as the parent post said: Interviews are hard because there is extremely low correlation between what is asked in Interviews and actual job work. I firmly believe the system of asking stupid algorithmic trivia is hackable and should be hacked because it is a broken rotten system that keeps incredibly amazing hackers out. There has been a ton of stuff said about interviews so I will keep this brief: 1. Get a githu…
Earlier quoted context omitted.
Just as the parent post said: Interviews are hard because there is extremely low correlation between what is asked in Interviews and actual job work. I firmly believe the system of asking stupid algorithmic trivia is hackable and should be hacked because it is a broken rotten system that keeps incredibly amazing hackers out. There has been a ton of stuff said about interviews so I will keep this brief: 1. Get a githu…
I hate stupid algorithmic trivia too! All of my interviews have been giving the person a laptop and asking them to make a very simple app while I watch. For iOS for example, I ask them to make a table view that shows 1 to 5. I let them use documentation and the web too. I ask them to add features if they can complete the app before 30-60m, and the more features the better. I'm totally fine with leaving the room too i…
Earlier quoted context omitted.
[deleted]
Scott means practice at interviews. Interview regularly, even when you have a job that you love, so when it matters, you are smooth and natural instead of rough and stilted. Technical skills can only go so far. It is rare that a person who is a technical master but doesn't appear to be able to participate in a design will succeed. Fortunately, that is easily fixed by getting out there and interviewing (with a bonus o…
Earlier quoted context omitted.
Interesting. That reminded me of this book "Start-up Nation: The Story of Israel's Economic Miracle" which says their military runs the same procedure in a similar way after missions.
As an Israeli, I can vouch for the massive ass-covering that goes on there. In fact, we just had a big public ass-covering demonstration regarding the awful flotilla blockade. Regardless of what one thinks of the political aspects and/or morality of that action, the purpose was to examine why were several soldiers injured and Israel's relationship with Turkey, previously a strategic ally, deteriorated. Both these res…
(1) The IDF is "ineffective" on an absolute scale. (2) The IDF is significantly more effective than most other organizations.
While better isn't perfect, you can learn from both.