Taking Responsibility for the Things You Build and Run Bookmark

It’s easy to blame third-parties and not taking responsibility for incidents of any kinds. The underlying problem is that it’s possible that it’s you yourself who allowed things to happen by design.

It’s you who designs your service. If you’re an engineer, it’s you who builds the API and the permission model which third-party gets access to which data. If you’re a designer, it’s you who designs the interface to ensure people understand what they’re doing when granting access. If you’re part of the company, it’s you who decides whether the service will work when users block Google Analytics or Crashlytics. It’s you who decides which data the service really needs. If we start with that in mind, it doesn’t matter if I’m working for someone else or myself. I know that I am responsible for what I work on.

Read the complete article by Anselm here.