Every project has a set of pain points that aren’t a direct output of the project but are indirectly related to it. “We can’t find reference documents anywhere.” “People are always late for meetings.” “Meetings go on too long.” “Our architecture is a mess.” The list goes on and on and on. These are pain points to the delivery of the project. These are pain points that are not only slowing your team down, but…
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…
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…
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…
Will it be on LinkedIn? Twitter or Facebook? The algorithms have changed and the content that is sent to you has as well. This isn’t a conspiracy, this is a fact, things change, code gets optimized, what you think is the right way to do something, might not be what the actual owner of the company thinks is the best way to do it. You might both be wrong. If it’s getting harder and harder…