That career switch? That change in direction on the project? That person on your team that wasn’t happy anymore? That code that failed in the next upgrade? Most times we can see it coming, we have an inkling of what is going to happen, we know something is afoot. And even more, most times (of those most times) we choose to ignore it, hope it doesn’t happen, hope nothing changes, hope we can keep on,…
Or CTRL + N. Or whatever keyboard, file combination works for you that signifies the blank slate with something to be created. You can’t go wrong with it. It’s the best feeling.
The first cut. The first deployment. The first delivery. Getting to that point of – “here it is, here is what I am offering” – is the hardest step you’ll take to getting whatever that thing is out the door. What comes next will be the feedback and the critiques you need to make it better but no matter how red or how many bugs get reported. It will never be as hard as getting…
Here’s someone you’ll come to meet once or twice in your career – the Project Hoard. The Project Hoard implies exactly what it is – someone who hoards all the projects for themselves. All the development, architecture, design, deployment tasks that are critical to the project being a success, they take it all on, they own it all, they can’t let any of it go, they can’t trust anyone to do it as well as…
If you are looking to implement a colossal change in your life and/or career. I.e., Run a Marathon or build an iPhone App as examples… And you’re getting nowhere because the goal of what it is you are trying to achieve is simply too big start with getting comfortable with the smallest part of the project. Master the Mini. If it’s an app you are building, focus on the database and how you are going…