I keep a WTF notebook (2021)

Engineers describe using a “WTF notebook” or work journal to quietly capture confusing, broken, or impressive aspects of a codebase or process when joining a new team, then revisiting those notes after gaining context. Many see this as a way to avoid being the new hire who complains constantly, to distinguish genuine problems from necessary complexity, and to improve onboarding, documentation, and team culture. Others worry that turning note‑taking into a deliberate reputation‑management strategy feels manipulative or overly political, highlighting a broader tension between authentic collaboration and career-minded social tactics at work.

Purpose and Benefits of a “WTF Notebook”

  • Many see value in logging confusing or frustrating things when joining a new team.
  • Writing first, acting later gives time to learn context; some “WTFs” are genuine mistakes, others are subtle complexity that become reasonable with understanding.
  • Helps separate emotional reaction from considered judgment, and leads to more thoughtful communication.
  • Several commenters extend the idea to general work journals, idea lists, or “how do I do this again?” files.

Onboarding, Fresh Eyes, and Team Learning

  • Strong agreement that you’re “only new once,” and new hires are uniquely good at spotting usability, process, and documentation issues others have gone blind to.
  • Some teams formally ask new hires to fix onboarding docs or present their understanding of the system, which is reported as effective even at larger orgs.
  • Others describe pushback when they tried to fix or document issues early, especially in rigid or political environments.

Timing and Style of Raising Issues

  • One camp supports the “observe for a while” strategy: early, constant criticism alienates teammates and wastes time when you don’t yet grasp constraints.
  • Another argues you shouldn’t need a 2‑week moratorium; you can raise issues immediately if you communicate respectfully and collaboratively.
  • Several note that in security or high‑risk domains, dumping all issues at once overwhelms people; structured, delayed reporting can be more effective.

Concerns About Manipulation and Office Politics

  • Some find the deliberate reputation‑building language off‑putting or “political,” focused on optics and performance reviews rather than shared goals.
  • Others counter that being intentional about relationships and influence is a legitimate professional skill, not inherently manipulative.

Risk of Becoming “The Fixer”

  • Mixed views on cultivating a reputation as the person who solves everyone’s problems.
  • Positives: broad network, organizational leverage, potential for higher‑level roles.
  • Negatives: risk of being flooded with requests, pigeonholed, or under‑promoted despite high impact.

Related Themes: Note‑Taking and Usability

  • Multiple commenters endorse aggressive note‑taking as a predictor of success for new hires.
  • Others draw parallels to watching real users interact with software: direct observation and “fresh eyes” reveal issues telemetry or veterans miss.