So is there a guide for error messages when the message is not client facing. The grammar, format, etc. +1 if it also provides language specific info , for example in Java use e.getMessage() etc?
The problem is that you guys can't even see how wrong it was. Only when it is starting to gain publicity and blowing in your face, then you are even "starting" to have a discussion about it.
There were very disappointing answers by mozilla employees on r/firefox.
While one pager resumes are the standard advice (and yet not many people know that), I see that the author of this article is biased towards the resume skills of a person.
You are not judging the person on his technical merits and suitability of the role but rather his resume skills. Unless the role you are hiring for is creating resumes.
Again, "tell me why I should hire you and in plain english" is just a bad question and a bad intent. You as an interviewer need to judge that and rather say here is why you should join.
Can you also suggest how much time one can expect to spend on a particular codebase (which are listed) to get any meaningful take-aways?
I am interested in exploring codebases now that I have sufficient experience and feel confident (and not initimidated). This will be useful because then I can start from the smaller (simpler) ones and move on to the complex ones later.
My main gripe with Chrome is it takes too much time to load for me even if it has to load no tabs on opening. Comparing this with firefox, FF always beats chrome (and note that firefox will always have around 60+ tabs to load, it probably doesn't matter). I have had 3-4 machines (without SSDs) and this difference is always there.
I didn't even used to keep Chrome installed a couple years back , it took an astonishing ~60 seconds or so to start.