We’ve all heard it before: breaking up is hard to do. Whether it’s a personal or professional relationship, pulling the plug on an arrangement that’s no longer working for you can be pretty tough, especially when there’s something important hanging on the line. In the case of web projects, you can feel intimidated to end a relationship with your developer for various reasons. But there may come a point when you have to fire your developer and go in a different direction. How do you know when that time has come? Keep reading.
Failure to plan is planning to fail.
We've all heard the old adage, but with software, failure should be part of any plan. This isn't because we want or even know that failure will occur. We certainly don't want the application to fail, but disaster happens. It could be a fire at the data center where the application is housed, infiltration by a malicious hacker, or any number of things that cause an application to fail. What's important, though, is that you have a plan in place to get back up.