Mfcttrf

bldc motor, esc and battery draw, nominal vs peak

What is the philosophical significance of speech acts/implicature?

How to prevent z-fighting in OpenSCAD?

Why was the Spitfire's elliptical wing almost uncopied by other aircraft of World War 2?

How come there are so many candidates for the 2020 Democratic party presidential nomination?

"Hidden" theta-term in Hamiltonian formulation of Yang-Mills theory

Is there any official lore on the Far Realm?

Coordinate my way to the name of the (video) game

A ​Note ​on ​N!

Did the BCPL programming language support floats?

I preordered a game on my Xbox while on the home screen of my friend's account. Which of us owns the game?

Why does Mind Blank stop the Feeblemind spell?

Do I have an "anti-research" personality?

Does a large simulator bay have standard public address announcements?

Check if a string is entirely made of the same substring

Extension of 2-adic valuation to the real numbers

Contradiction proof for inequality of P and NP?

Is the claim "Employers won't employ people with no 'social media presence'" realistic?

Could the terminal length of components like resistors be reduced?

Read line from file and process something

How to write a column outside the braces in a matrix?

How would 10 generations of living underground change the human body?

Pulling the rope with one hand is as heavy as with two hands?

What happens to Mjolnir (Thor's hammer) at the end of Endgame?

What is the best way to motivate your peers to “go read up about it” vs. explaining them everything at that instant?

How to politely ask a coworker to “Google it”Is it true that it is better to get a degree with a specific option than just to get the degree in general?Do I need to convey to foreign recruiters that the education I received from a Catholic university was in no way religious?Inform an applicant that the for-profit school they went to failed them?

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

1

We have many cases where colleagues with different experience levels are in a meeting and debating about some software design. And another set of engineers who don't "get it" and would rather simplify everything - by simplification I mean "simplify to their understanding" and not necessarily adopt the suggested principles/practices in our domain.

At times, meetings have been derailed just so that we get provide a knowledge dump, which is exhausting with all cross-questioning/teaching etc., and then are they on board.

We've had discussion where we've explicitly given them some knowledge dump and provided links/books/references to follow up on the others. However, the "follow up" never happens and we're back to square one. It seems there's resistance in putting up the effort to "read up about it" and then come back with questions/clarifications/suggestions vs. argue about it right there and go back not feeling convinced and just leaving it at a stalemate.

What are good ways to "motivate peers" to "study/learn" new things vs. derailing meetings to explain everything to them?

UPDATE: This is not as straightforward to "Google it". It's more difficult than a keyword search but more of understanding underlying concepts and why things are done/preferred in a particular way. At times, books do a much better job than Google. The idea is probably to go a little deeper into the topic and make sense of the disparate sources of information to understand something that may take a few hours worth of mulling/understanding vs. a few minutes of Googling. It's about "lack of domain expertise" and unwillingness to "build it up" vs. "explain it to me right now".

professionalism communication colleagues education mentoring

share|improve this question

edited 1 min ago

PhD

asked 46 mins ago

PhDPhD

1063

New contributor

PhD is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Possible duplicate of How to politely ask a coworker to “Google it”
  
  – DarkCygnus
  12 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @DarkCygnus - it's not entirely "Google-able" IMHO - this is deeper than just "keyword search" but more like "knowledge gained" - probably multiple google searches linking disparate ideas. Unfortunately it's hard to "google it" exactly so we tend to save books, links, references when we find it...
  
  – PhD
  4 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  what is your job and how exactly this situation prevents you from doing it?
  
  – aaaaaa
  2 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I suggest you read the post and answers, and not just judge a post by its title... There are several answers that apply to the situation you describe here, I am sure they will at least give you some pointers... perhaps it requires several google searches, but in a bigger sense "google it" means "try finding it on your own"
  
  – DarkCygnus
  2 mins ago
  
  

  
  
  
  

add a comment | 

1

We have many cases where colleagues with different experience levels are in a meeting and debating about some software design. And another set of engineers who don't "get it" and would rather simplify everything - by simplification I mean "simplify to their understanding" and not necessarily adopt the suggested principles/practices in our domain.

At times, meetings have been derailed just so that we get provide a knowledge dump, which is exhausting with all cross-questioning/teaching etc., and then are they on board.

We've had discussion where we've explicitly given them some knowledge dump and provided links/books/references to follow up on the others. However, the "follow up" never happens and we're back to square one. It seems there's resistance in putting up the effort to "read up about it" and then come back with questions/clarifications/suggestions vs. argue about it right there and go back not feeling convinced and just leaving it at a stalemate.

What are good ways to "motivate peers" to "study/learn" new things vs. derailing meetings to explain everything to them?

UPDATE: This is not as straightforward to "Google it". It's more difficult than a keyword search but more of understanding underlying concepts and why things are done/preferred in a particular way. At times, books do a much better job than Google. The idea is probably to go a little deeper into the topic and make sense of the disparate sources of information to understand something that may take a few hours worth of mulling/understanding vs. a few minutes of Googling. It's about "lack of domain expertise" and unwillingness to "build it up" vs. "explain it to me right now".

professionalism communication colleagues education mentoring

share|improve this question

edited 1 min ago

PhD

asked 46 mins ago

PhDPhD

1063

New contributor

PhD is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Possible duplicate of How to politely ask a coworker to “Google it”
  
  – DarkCygnus
  12 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @DarkCygnus - it's not entirely "Google-able" IMHO - this is deeper than just "keyword search" but more like "knowledge gained" - probably multiple google searches linking disparate ideas. Unfortunately it's hard to "google it" exactly so we tend to save books, links, references when we find it...
  
  – PhD
  4 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  what is your job and how exactly this situation prevents you from doing it?
  
  – aaaaaa
  2 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I suggest you read the post and answers, and not just judge a post by its title... There are several answers that apply to the situation you describe here, I am sure they will at least give you some pointers... perhaps it requires several google searches, but in a bigger sense "google it" means "try finding it on your own"
  
  – DarkCygnus
  2 mins ago
  
  

  
  
  
  

add a comment | 

We have many cases where colleagues with different experience levels are in a meeting and debating about some software design. And another set of engineers who don't "get it" and would rather simplify everything - by simplification I mean "simplify to their understanding" and not necessarily adopt the suggested principles/practices in our domain.

At times, meetings have been derailed just so that we get provide a knowledge dump, which is exhausting with all cross-questioning/teaching etc., and then are they on board.

We've had discussion where we've explicitly given them some knowledge dump and provided links/books/references to follow up on the others. However, the "follow up" never happens and we're back to square one. It seems there's resistance in putting up the effort to "read up about it" and then come back with questions/clarifications/suggestions vs. argue about it right there and go back not feeling convinced and just leaving it at a stalemate.

What are good ways to "motivate peers" to "study/learn" new things vs. derailing meetings to explain everything to them?

UPDATE: This is not as straightforward to "Google it". It's more difficult than a keyword search but more of understanding underlying concepts and why things are done/preferred in a particular way. At times, books do a much better job than Google. The idea is probably to go a little deeper into the topic and make sense of the disparate sources of information to understand something that may take a few hours worth of mulling/understanding vs. a few minutes of Googling. It's about "lack of domain expertise" and unwillingness to "build it up" vs. "explain it to me right now".

professionalism communication colleagues education mentoring

share|improve this question

edited 1 min ago

PhD

asked 46 mins ago

PhDPhD

1063

New contributor

PhD is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited 1 min ago

PhD

asked 46 mins ago

PhDPhD

1063

New contributor

PhD is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited 1 min ago

PhD

asked 46 mins ago

PhDPhD

1063

New contributor

PhD is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 46 mins ago

PhDPhD

1063

New contributor

PhD is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 46 mins ago

PhDPhD

1063