Wow, I thought the online papers etc trying to charge had dispeared ?! There were worries that newpapers were going to lose too many readers in print and started charging online.. assumed this had died. Never will pay for news, it's freely available and actually most are behind the social networks at getting anything up to date.
Ok, many people have already picked this one up. But how many full time developers do you need? Your ERP should be upgraded/customised/developed on a project, maybe 3-6 months cycle per year. Unless there is an urgent bug or other issue that stops the business. It seems to us like every little ask by the business is just put into place, instead of driving the business to using the software correctly or at least 4 full developers seems like that's the case. I'd look at create a correct roadmap for the ERP or even look at if it's the correct product. That much development for any company seems excessive unless you were like someone who are totally unique ala NASA. But, assuming all is good with the number of developers, I'd be pushing to look at how the efficiencies would benefit the company in terms of profit? So a business case with the team and your manager, then this needs to be presented to your CEO etc.
So what OS did they infect?
Back hander from the power contractors. Germany aren't doing that bad..
Your car was built by robots, yeah some parts are still done by hand. But a huge part of the manufacture process is done by robots. People are happy to assume the car is not going to break and risk their life every day. So why not a needle?
Sounds like to me there is no UAT going on. Old method but, Development->UAT->Product, should be the most basic method. Sounds like you are handing over the software without any sign off from the customer. If they are signing it off, are you getting them to test it first? As part of your contract with the developer, you should be making sure the developer is aware of this process. That "within reason", the customer should be testing the software according to your specification. Any bugs can be returned to the developer. Once it meets the specification, then the customer signs it off. The customer is then aware, any issues after that period they pay and the developer knows after that period they get payed. Having an employed developer, means you have an overhead if you have no business coming in.