Everyone and anyone can show up to a meeting. But only some can contribute. Only some can ask the hard questions. Only some can move the ball forward. Only some come with information and content relevant to what is being discussed. If you are attending a meeting with the thought that you need to be “entertained” or “wowed” – save everyone some time and watch the recording later.
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.
Your bug might have been reported on X, but when you dug into it, it was really an issue with component Y. Component Y didn’t handle the error correctly and hid it instead but eventually it bubbled up stopping your code in the progress. Upon further inspection, it looked like it’s not a problem at all but a feature of Platform A that can be implemented via toggling Option B. All this to say, to…
Tasks are the livlihood of developer work. If you have an overload of tasks in your queue, you are in demand, you are getting work done and you are needed by your team. If you don’t have any tasks in your queue, you should be a bit worried, a little concerned that your queue is growing empty. Whenever my queue starts to shrink, I reach out to those for what is next, if it fills…
I’ve written about this before, but it bears mentioning, for so many reason. If you are going to start something new, don’t fall into the trap of dipping your toe in to see if the temperature is right for you. In short – the temperature will never be right, it will always be a bit too cold or a bit too warm. Eventually you need to jump in, fully submerge yourself to make the impact…