4 ms·

I think the concept of a 'WTF notebook' is great, and I think writing down one's thoughts in general is a good idea. I also think that it helps formulate though

I think the concept of a 'WTF notebook' is great, and I think writing down one's thoughts in general is a good idea. I also think that it helps formulate thoughts and communicate them in a more thoughtful not-in-the-heat-of-the-moment way. However, > For two weeks, that's all I do. I just write it down. I don't tell the team everything that I think they're doing wrong. I don't show up at retro with all the stuff I think they need to change. I just watch, and listen, and I write down everything that seems deeply weird. > [...] > Before I started keeping this kind of list, I brought up problem I saw immediately, as soon as I noticed it. The reputation I got was, "Nat's always complaining about things. Nat thinks we're never doing things right." People stopped listening to me. I was personally frustrated, and professionally ineffective. Not bringing up things that you think could be improved in a retro.. that's pretty silly. If you are getting a reputation of 'always complaining', and coming across as 'telling people they are doing things wrong', etc. then you are just bad/unprofessional at communication. Communicate things as 'I was thinking maybe we could do <X> better if <Y>, what do you think?' and make it a genuine discussion with people, rather than 'WTF <x>?' - especially when it is someone else's work and you want to remain on good terms with them. You don't have to wait 2 weeks, compile a secret list and then bring it to your manager - though. You can communicate things that you think can be improved in a polite/respectful manner as they occur. Being on a team is about working together. If you cannot safely do that when communicating effectively, then you are with a terrible team/company.

lrvick 2y ago
If the author is anything like me, I get it. I have 20 years of software engineering and infosec experience can fill a few hours talking about all the crazy risks I find in a day of looking around most any company I interact with. The status quo for security in our industry is abysmally bad. Not washing hands while working in a hospital WTF bad, everywhere. Bringing it all up as I go can burn everyone out on interacting with me or trusting me at all if I am not careful, because survivors bias is a hell of a drug. Two weeks to collect information and context is about right. I just usually do it as a contract security auditor now and provide a detailed report at the end.
al_borland 2y ago
I think you missed the point. This is about someone entering into a new team. Walking into a team day 1, knowing nothing, and telling everyone they’re doing it wrong, is a horrible way to start things off. By watching and waiting a bit, it gives time to learn why the stupid things are stupid, what is actually being worked on, etc. This helps build trust in the team, because it shows the new person respects the team enough to take some time to learn how things are before trying to change it. I don’t trust anyone in a leadership role that starts changing things before taking the time to learn how and why things are currently done the way they are. A guy on my team now takes your approach. He derails every meeting with the way things “should” be, and he is just saying what everyone already knows, he just lacks the understanding on why the problem is more difficult to fix than he realizes. If he would talk less and listen more, he might understand those things better and stop wasting everyone’s time.
- blaise-pabon 2y ago
  Yes, I think I have been "that guy" when I walk into a situation I have been hired to fix, I want to get started right away. If I see a common problem, I want to fix it immediately and say something like "I see big batch sizes all the time and they have a simple, counter intuitive fix. In fact, of you had read more than 30 minutes, you would see it addressed."
yjftsjthsd-h 2y ago
Waiting a couple weeks makes sure you have enough context to usefully contribute with less stepping on toes.

lrvick 2y ago

If the author is anything like me, I get it. I have 20 years of software engineering and infosec experience can fill a few hours talking about all the crazy risks I find in a day of looking around most any company I interact with. The status quo for security in our industry is abysmally bad. Not washing hands while working in a hospital WTF bad, everywhere. Bringing it all up as I go can burn everyone out on interacting with me or trusting me at all if I am not careful, because survivors bias is a hell of a drug. Two weeks to collect information and context is about right. I just usually do it as a contract security auditor now and provide a detailed report at the end.

al_borland 2y ago

I think you missed the point. This is about someone entering into a new team. Walking into a team day 1, knowing nothing, and telling everyone they’re doing it wrong, is a horrible way to start things off. By watching and waiting a bit, it gives time to learn why the stupid things are stupid, what is actually being worked on, etc. This helps build trust in the team, because it shows the new person respects the team enough to take some time to learn how things are before trying to change it. I don’t trust anyone in a leadership role that starts changing things before taking the time to learn how and why things are currently done the way they are. A guy on my team now takes your approach. He derails every meeting with the way things “should” be, and he is just saying what everyone already knows, he just lacks the understanding on why the problem is more difficult to fix than he realizes. If he would talk less and listen more, he might understand those things better and stop wasting everyone’s time.

blaise-pabon 2y ago
Yes, I think I have been "that guy" when I walk into a situation I have been hired to fix, I want to get started right away. If I see a common problem, I want to fix it immediately and say something like "I see big batch sizes all the time and they have a simple, counter intuitive fix. In fact, of you had read more than 30 minutes, you would see it addressed."

yjftsjthsd-h 2y ago

Waiting a couple weeks makes sure you have enough context to usefully contribute with less stepping on toes.