If your unfinished projects are adding up there are generally two approaches to solving them. One – Close them off so you don’t see them anymore. Two – Stop starting new projects until you finish the old ones. Both options involve some work in look at the old projects. But you haven’t been working on them at all, so that is why they are “old” projects in the first place, going back to them will…
If you have ever written a line of code, you are a developer – it’s that simple. It doesn’t matter if you sold it. It doesn’t matter if you packaged it. It doesn’t matter if you promote it on twitter. It doesn’t matter if showed it. All that matters is that you wrote that line of code, you ran it, and it did something. If it shows “Hello World” on your screen, then congratulations you…
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…
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.