Skip to main content

最有效的解决问题的方式

领导者通过问题看到机遇

 领导者看问题不是作为干扰， 而是不断改进和看到原来没有意思到的机会
A leader must never view a problem as a distraction, but rather as a strategic enabler for continuous improvement and opportunities previously unseen.

 responding promptly and efficiently  with a comprehensive step-by-step incident report that included our change management efforts.
Effective leaders connect the dots and map-out a realistic plan of action in advance. They have a strategy that serves as the foundation for how the problem will be approached and managed. They anticipate the unexpected and utilize the strengths of their people to assure the strategy leads to a sustainable solution.
Never shoot from the hip when problem solving. Avoid guessing. Take enough time to step back and assess the situation and the opportunities that each problem represents. Make the problem solving process more efficient by recognizing that each problem has its own nuances that may require a distinct strategy towards a viable resolution.


 They never realize that, in the end, all problems are the same – just packaged differently.
A silo mentality is a reluctance to share information with employees of different divisions in the same company. This attitude is seen as reducing the organization's efficiency and, at worst, contributing to a damaged corporate culture.Jun 25, 2019
https://www.forbes.com/sites/glennllopis/2013/11/04/the-4-most-effective-ways-leaders-solve-problems/#348d59cd4f97

  • Generous favors blossom into friendships.
  • Odd jobs blossom into annual contracts.
  • Coworkers blossom into supporters.
  • Bosses blossom into advocates.
  • Friends blossom into partners.
  • Ideas blossom into enterprises.
Labels:

Comments

Post a Comment

Popular posts from this blog

for loop in javascript - promise - .eslintrc for "for of"

the vast majority of cases  map ,  forEach ,  find  etc. can be used.  async function printFiles () { const files = await getFilePaths(); await Promise.all(files. map (async (file) => { const contents = await fs.readFile(file, 'utf8') console.log(contents) })); } const inventory = [ { name : 'apples' , quantity : 2 } , { name : 'bananas' , quantity : 0 } , { name : 'cherries' , quantity : 5 } ] ; const result = inventory . find ( ( { name } ) => name === 'cherries' ) ;   function getFirstMatching(array) { for (let item of array) { const result = heavyTransform(item); if (result) { return result; } } } Specifically this shuts down the whole no-restricted-syntax. If you want to cherry-pick, here is the current definition: 'no-restricted-syntax' : [ 'error' , { selector : 'ForInStatement' , message...
Post a Comment
Read more

setup git account on mac with ssh - push to remote denied with other login

http://burnedpixel.com/blog/setting-up-git-and-github-on-your-mac/#generatenewkey “ SSH  uses public-key cryptography to authenticate the remote computer and allow it to authenticate the user, if necessary. There are several ways to use SSH; one is to use automatically generated public-private key pairs to simply encrypt a network connection, and then use password authentication to log on.” An SSH key basically lets your computer uniquely identify itself when it connects to servers. If Github is aware of the key your computer is using, you won’t have to enter your Github username/password every time you connect. Check for pre-existing SSH keys on your computer Let’s see if your computer has one or more keys already installed: 1 2 # Point the terminal to the directory that would contain SSH keys for your user account. $ cd ~/.ssh If you get the response “No such file or directory”, skip to  Generate a new SSH Key . Otherwise, you’ll need to backup...
Post a Comment
Read more

fs.writeFile - permission issue on GCP (Google Cloud Run)

error on this: fs . writeFile ( fileName , pdfBytes , err => { if ( err ) { console . log ( err . message ) reject ( err . message ) } else resolve ( fileName ) }) #1 It looks like when deployed into Cloud Run it also requires the extra permission "Service Account Token Creator" to run  getSignedUrl . Locally for some reason this role is not required. #2 Only the directory  /tmp  is writable in Cloud Run. So, change the default write location to write into this directory. However, you have to be aware of 2 things: Cloud Run is stateless, that means when a new instance is created, the container start from scratch, with an empty  /tmp  directory /tmp  directory is an in-memory file system. The maximum allowed memory on Cloud Run is 2Gb, your app memory footprint included. In addition of your file and Airflow, not sure that you will have a lot of space. A final remark. Cloud Run is active only when it...
Post a Comment
Read more