dblock / dblock/code.dblock.org
VPEng/CTO responsibilities in firing
Open
Nobody has claimed this yet.
post topic suggestion
- Dominant language
- JavaScript
- Stars
- 7
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
A long-standing senior engineering IC does something terrible and the right thing to do is to let the person go.
Do we need special treatment for OGs?
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 body raises a policy question about how to handle firing a long-standing senior engineering individual contributor, but names no files, tests, or entry points. Clarify whether a documented policy or an article is wanted, then define the intended audience and acceptance criteria before starting.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100