3,368 karma · joined March 5, 2010
QED.
Again, generally speaking, no one should have more than one of these meetings a week unless they really have a good reason to be actively involved in multiple independent teams.
The real meeting-smell is when people have lots of weekly recurring meetings. If you're not a manager then two would be expected for most people, a 1hr team meeting and a 30min 1-1 with whomever they report.
These are streets where there is usually not room for two cars to pass in opposite directions and pedestrians, dogs and bikes are frequently going to be hazards.
https://www.statista.com/statistics/1224844/monthly-pay-of-e...
Gmail and Calendar are great. Drive is also sub-par in experience when compared to Dropbox (probably Box as well though I've not used it)
Oddly Sheets is the only one I like. It is good enough for most use cases and simpler and easier to use than Excel.
I've never even considered using Docs or Slides.
Often the interviewer is looking for fairly short and concise answers to their questions so they can direct the flow and conversations to what they need to hear through further questions. Filling all the available air time either forces them to rudely interrupt you (which feels awkward) or wait for you to finish even though they aren't that interested in the content.
As an example, if you are asked a very open ended question like "tell me about about role X and company Y.
Start with a brief overview of the role, the company and responsibilities and then pause. Then if they don't immediately ask a more detailed question about the role suggest something. "Would you like to me get into some details about my most recent project/success/challenge?"
Staying brief helps the interviewer get to what they want to know and eases your own burden of maintaining all of the flow in the conversation.
It isn't terribly exciting stuff. Simply remove the unnecessary ceremonies and "rituals" and instead focus on practical and effective solutions to the problems you actually have. Continuously try out new ways of building the software better, measure your results, continue to improve. The heart of the agile manifesto I suppose.
1. Upon entering you must write and demonstrate one failing test
2. The manager asks you if you want someone to pair program with you
3. You are not allowed to leave until the test is passing
Average life expectancy is just shy of 30,000 days, making this an effect of less than 0.2%. This would be impossible to even measure definitively.
This article seems to be nothing more than logical conjecture and opinion. The related evidence also seems to be tangentially related at best.
A purpose built algorithm designed to thwart watermarking however is far more likely to be successful than a compression algorithm that is designed to maintain the integrity of the audio.
I did note that one of the links on this page goes to a Canadian white nationalist site so that's great...
?