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,…
We all know where we excel and the value we provide. The hard part is showing it to others when it’s not clear what the path is. And who wants to talk about what they are good at? Not easy, but maybe it’s a question to ask of yourself to know where you are going next.
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)?
In every problem you are working on, there are always a number of What Ifs to figure out – after all, it’s a problem – that you don’t know how to solve. But if you give into each and every what if that comes up, you’ll never get to solve the problem and will be left drowning in an innumerable setup of What Ifs for life. Isolate the problem, focus on the immediate, save the…