If you want to be seen as the developer that “knows it all” you better work hard to make sure you do (an impossible task). Or, if it’s something much smaller as – “yes I’m really busy and do have not to time for other tasks” – then you better be really busy. The statements we make are descriptions of what we are going through and what we are doing but the actions we take,…
Even when you screw up. Even when you have to read the documentation again. Even when it doesn’t make sense. Even when you are sore and beat down. Even when you aren’t sure where to start next. Keep. Showing. Up.
I’ve held off on adding new categories to my posts for a while now as I generally think what you do comes down to behaviors of work that you do, but I know I’ve been writing about different areas of work that I’d like to bring more to the forefront and I’m also looking to change some of the content that I’ll be writing about. You’ll start seeing new categories such as Team (for remote,…
There is always that point in any project where it fell over. The hard part is realizing where you were when it fell over and what you could have done differently. The even harder part is wanting to find this point so you can make a difference on your next project (because who wants to revisit old pains)?
When someone leaves your team, there is a window from the point when they announce when they are leaving to when they actually leave. That window is the amount of time you have to get all of the training this person has learned in their time with you and download it to another person. These are the interactions you don’t want to push off and you want to kick off as soon as possible to…