practicalli / practicalli/engineering-playbook
Building trust
Open
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 12
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
What creates trust - honesty
- transparencey /openness
- consistency
- do what you say you are going to do
- not afraid to fail
- feeling safe to share
- support, espe
- empathy
- egoless / no agenda
Nobody is wrong about the way they feel
Being present
Bring a beginners mind
3 levels of listening
- active (self)
- focus (on others)
- global (non verbal)
vulnerability
- uncertainty, risk, exposure
Pillars:
- Psychlogical Safety
- Dependability
- Structure & Clarity
- Meaning
- Impact
biases
- sophistication
- adrenaline
- quantification
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue lists ideas about trust, listening, vulnerability, psychological safety, and biases, but names no file, entry point, or expected document structure. Start by clarifying where this material belongs and what form it should take. Done means the intended content is organized in the agreed location with clear scope and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100