3 ms·

> Should I write down the steps to every process? For the love of God, yes. Do you just intend to memorize everything? Are you assuming that you'll never get

> Should I write down the steps to every process? For the love of God, yes. Do you just intend to memorize everything? Are you assuming that you'll never get interrupted or pulled away from a task? Are you going to memorize the task backwards in case you need to revert? Ok, I think you get my point by now, please create a playbook (checklist) for every critical process that you're responsible for. This will make life so much simpler for you. Basically you should create a system or process that turns your most consequential tasks into the most boring part of your day.

jupp0r 5y ago
Every process should be written down somewhere (a wiki, a markdown file in some repo, …) anyways. It’s not OPs fault if this isn’t the case on his team, but it’s definitely an opportunity to contribute and create documentation. Everybody writing it down for themselves is not a good solution.
dgb23 5y ago
I think most answers here are addressing the cultural problems well, as well as the expectations one should have in regards to junior positions or even just new hires. And these things are important and have to be said. However this is the most important one. Yes one should be able to lean on others as a junior, ask questions and so on. But in order to have _any_ progress and confidence at all one has to do _this_. Writing things down, even drawing, helps to think clearly and to remember important details. Even just questions, assumptions and so on. It helps to focus and to organize. Checklists/steps are great too, because one can see very quickly how they initially lack very important steps. Our brains are very selective when it comes to details that are not grounded in experience, or have not been used multiple times already. The third benefit is hard problems (that may or may not have simple causes). The back of our brain will pattern match and process the notes during sleep or other activities - and suddenly solutions appear.

jupp0r 5y ago

Every process should be written down somewhere (a wiki, a markdown file in some repo, …) anyways. It’s not OPs fault if this isn’t the case on his team, but it’s definitely an opportunity to contribute and create documentation. Everybody writing it down for themselves is not a good solution.

dgb23 5y ago

I think most answers here are addressing the cultural problems well, as well as the expectations one should have in regards to junior positions or even just new hires. And these things are important and have to be said. However this is the most important one. Yes one should be able to lean on others as a junior, ask questions and so on. But in order to have _any_ progress and confidence at all one has to do _this_. Writing things down, even drawing, helps to think clearly and to remember important details. Even just questions, assumptions and so on. It helps to focus and to organize. Checklists/steps are great too, because one can see very quickly how they initially lack very important steps. Our brains are very selective when it comes to details that are not grounded in experience, or have not been used multiple times already. The third benefit is hard problems (that may or may not have simple causes). The back of our brain will pattern match and process the notes during sleep or other activities - and suddenly solutions appear.