The Neuronen Schmiede concerns itself with topics related to software development. One focus are robust web applications.

Don't Forget That Dependencies Have a Cost


Google is changing their services around Google Maps. In a month they will insist on filled out billing information and massively decrease free quotas of their platform. Initial reactions show that this is a fatal problem to some projects forcing them to shutdown.

A situation like this reveals how fragile ones software development process is. Is there a checklist in place for adding dependencies to a project?

The checklist creates awareness for these situations long before they occur. It makes sure there is an alternative plan in place and at least shows the boundaries of operation.

What does your checklist look like?