VPEng/CTO responsibilities in firing

Open
#59 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

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.

Description

post topic suggestion

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?

Dominant language
JavaScript
Stars
7
Forks
30
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dblock/code.dblock.org

All issues in dblock/code.dblock.org

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.