-
Notifications
You must be signed in to change notification settings - Fork 361
Feedback "Fiesta"
Davis W. Frank edited this page Oct 17, 2018
·
2 revisions
This is a time, schedule weekly, free to reflect your interaction with fellow team members.
During this time feel free to:
- Write up a story about working with someone recently
- Reflect on interactions with a team member over time
- Think about your own strengths or growth areas; What you would like others to tell you about yourself?
Things to note:
- You should be able to provide feedback to anyone, in any role (e.g, for devs not just someone you've paired with)
- Positive things are just as important as constructive things
- If you are writing up something, send it via email
- If appropriate (e.g., about someone's skills, career growth), please include their manager
If you're not yet comfortable with writing feedback for others, here are some frameworks/techniques to consider.
- Timely - share your feedback very soon after an interaction
- Actionable - share information to help the other person
- Specific - share lots of detail in order to reduce ambiguity
- Kind - share your experience and impact politely
- Giving Feedback from Radical Candor
-
Pipelines
-
Contributing
- Tips and Tricks
- Cloud Controller API v3 Style Guide
- Playbooks
- Development configuration
- Testing
-
Architectural Details
-
CC Resources
- Apps
- Audit Events
- Deployments
- Labels
- Services
- Sidecars
-
Dependencies
-
Troubleshooting
- Ruby Console Script to Find Fields that Cannot Be Decrypted
- Logging database queries in unit tests
- Inspecting blobstore cc resources and cc packages(webdav)
- How to Use USR1 Trap for Diagnostics
- How to Perf: Finding and Fixing Bottlenecks
- How to get access to mysql database
- How To Get a Ruby Heap Dumps & GC Stats from CC
- How to curl v4 internal endpoints with mtls
- How to access Bosh Director console and restore an outdated Cloud Config
- Analyzing Cloud Controller's NGINX logs using the toplogs script
-
k8s
-
Archive