Contract software developers have to deal with a lot of issues, especially if they are honest. There are loads of scam artists out there who can’t code particularly well, but will throw an application together for a client quickly, often disappearing shortly afterward. I’ve cleaned up lots of code from that sort and it’s a headache. This article wasn’t really written for that sort of developer, however, as I believe it’s very easy to accidentally screw a client over, even when one is otherwise trustworthy and honest, simply because you don’t think through all the implications of what you are doing. Here are ten ways I’ve seen developers screw their clients, without intending to do so. This is aimed more at solo developers, although a number of these points could apply to larger companies as well.

This is my first ever hardware review, but while I was going through the process of the move, I bought a new router because I needed better signal coverage, VPN capabilities, and other features. After a lengthy exercise in price and feature comparison, I settled on the Netgear Nighthawk AC1900 R8000 router. This router runs right around $300, whether you get it at NewEgg or at Best Buy (I’m assuming that means that they have a suggested retail price and everyone is sticking to it for now).

I normally try to get a blog post out every Tuesday, and sometimes on Thursday, based on my workload. This past week though, I totally dropped the ball. On Thursday of last week, we were supposed to sign the paperwork to sell our house at 9:30 in the morning, and sign paperwork to buy a new house at 12:30 in the afternoon. We then would have until Saturday night to get everything moved, and I would (of course), have working internet within a day or so of the move-in.