As a Developer, I have always hated saying these words, it always feels a bit like a copout – like I didn’t do my job, left something out, forgot a scenario, ignored something, etc, etc. I don’t mind the jokes that come with it (and they do come, in waves and torrents). When this happens my first thoughts are; Don’t say it.Ask for logs.Get a screenshot.Work the problem. It’s that last one that is so…
If they mean something, use them. If they are saying the same thing, over and over again and never getting anywhere and have become utterly meaningless. Let them go and find something new.
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.
Without getting into a whole “thing” on experts, there is a common fallacy that when your team isn’t performing, you need more of them to get back on track. On a sorely undermanned project, of course, you might need more senior resources to jump in and get the ball rolling again. But in most cases, your projects are not at this point and what need isn’t an Expert, what you need is for your existing…
No matter what it is. Being a YouTuber. Coding. Writing. Kicking a ball. Scoring a goal. Drawing. Building a House. Building a Fence. Knitting. Writing proposals. Whatever it is, remember, it’s all learning, all the time. You are never done, you’re always growing, always learning more. It doesn’t happen overnight, it happens over life.