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…
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…
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…
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…
Your code. Your team. How you lead. What project you are working on. What you are learning. Everything, it all breaks at some point. Good. That’s the point, if it doesn’t break, you’re not learning, you’re going through tutorials and motions where everything is isolated and perfect. It’s messy, all of it, it’s supposed to be messy, that’s the point. Break it, make a mess, fix it and grow.