February 12, 2021
Take a look at the work you are doing, what you are building, what you are creating. Are you a part of the team? Does what you do contribute to what the team is trying to deliver? It’s not just code, it’s leadership, it’s teamwork, it’s accountability and owning up to when things go wrong, it’s putting in the cycles when the team needs them. Are you a part of all that? Are you on the team?
February 7, 2021
But in the remote world, we are trying to solve every problem with technology. You don’t need to wellness emails that tell you how long you have been in front of a screen, you know. You don’t need an app to break out what you should be doing next. You don’t need an app that pulls you out of meetings because you have one scheduled right behind it. Sometimes a problem is just a problem that needs to be solved on your own… without technology.
February 1, 2021
If you can do either, you’re a developer ahead of the game of many others. These are two of the most important skills when becoming a developer because at their core they speak to creating and fixing code. Debugging – Walking through your own code to see if there are errors and/or running your own code to replicate errors. Troubleshooting – Getting an error sent to you that requires you to dig through the code you built and the tools you have given yourself to identify the source of the problem. One supports the other. Over time, I have become
January 28, 2021
If you want to be the most for your team and help them get the succeed. The best way to do that is to learn their habits. How do they learn best? What tools help them work? What distractions are in their way? What do their schedules look like? Who do they work best? All of these questions (and more) help you put that picture together on how you can help your team and what they need from you. When you figure all that out, you have a picture, a view and a direction in what you should be doing
January 16, 2021
There is a very common myth that attending a meeting is work. It’s not, it’s clicking an invite, listening to people talk and interjecting when you might have an opinion. Now, if you were to run the meeting, well this is different – because then you are having to think about who needs to be there, who will contribute, what do you need to prepare, what should the focus be, where do you want people to think about when they leave, what messages matter and on and on. Attending – you don’t need to do much. Running – you are
