Summary: The Five Dysfunctions of a Team

The Five Dysfunctions of a Team, by Patrick Lencioni, published by Wiley, John & Sons, Incorporated.

 

Book Summary: THE FIVE DYSFUNCTIONS OF A TEAM

Kaleido

The first step towards reducing misunderstandings and confusion within a team is to understand that there are five dysfunctions, and that each one that applies has to be addressed separately.   

1. Absence of Trust

The root cause of absence of trust lies with team members being unable to show their weaknesses; to be vulnerable and open with one another. The absence of trust is a huge waste of time and energy as team members invest their time and energy in defensive behaviors, and are reluctant to ask for help from – or assist – each other. Teams can overcome this dysfunction by sharing experiences, following through in multiple ways, demonstrating credibility, and developing strong insight into the unique characteristics of team members.

The following signatures couldn't be verified because the public key is not available:

GPG error: https://dl.bintray.com/marshallofsound/deb trusty Release:

Ubuntu 18.04

$ sudo apt-get update
W: GPG error: https://dl.bintray.com/marshallofsound/deb trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 379CE192D401AB61
E: The repository 'https://dl.bintray.com/marshallofsound/deb trusty Release' is not signed.

From the "software and updates" application (System/Administration if like me using the Traditional theme) select the "Other Software" tab and UNTICK the entry for marshallofsound as seen below (not the highlighted one, that's mega)

Uncheck

After that, exit and update as prompted. Either then through the command line or graphically from the software updater, update.

Google Accounts and Backup codes

Basics of backup codes

If you lose your phones or otherwise can't receive codes via SMS, voice call, or Google Authenticator, you can use backup codes to sign in. Follow the instructions below to generate backup codes. You can also use these codes to sign in if you don’t have your Security Key.

The codes come in sets of 10, and you can generate a new set at any point, automatically making the old set inactive. In addition, after you’ve used a backup code to sign in, it will become inactive.

We recommend you store your codes wherever you keep your other valuable items. Like the codes on your phone, backup codes are only valuable to someone if they manage to also steal your password.

Creating and viewing a set of backup codes

To create a new set of backup codes:

Getting started using saltstack

On line saltstack manual

https://docs.saltstack.com/en/latest/topics/tutorials/index.html

Example install for Centos 7

# yum install https://repo.saltstack.com/py3/redhat/salt-py3-repo-latest.el7.noarch.rpm
# yum install salt-master
# yum install salt-minion
# yum install salt-ssh salt-syndic salt-cloud salt-api

Edit config files # vim /etc/salt/master

   - #interface: 0.0.0.0
   + interface: 10.0.0.1

# vim /etc/salt/minion

  - #master: salt
  + master: 10.0.0.1

Start processes in the background as demons

# salt-master -d
# salt-minion -d

Useful commands

$ sudo salt \* sys.list_modules

$ sudo salt \* sys.list_functions

$ sudo salt \* sys.doc

Only on Redhat servers list all status

$ sudo salt -G 'os_family:redhat' status.all_status

Change to yaml output only on Redhat servers show all memory info

$ sudo salt --output=yaml -G 'os_family:r*' status.meminfo