3 ms·
I don't think "developers should operate the software they write" means "developers should be sysadmins", more that developers need to be tightly coupled to the
by taneq 7y ago
I don't think "developers should operate the software they write" means "developers should be sysadmins", more that developers need to be tightly coupled to the actual uses of the software they're developing. You can't write good software in a vacuum, no matter how carefully you analyze requirements and specify functionality. You just can't. You need to be close to the users. Even if you can't eat the dog food yourself, you need to watch the users eating it.
- majewsky 7y agoExactly. The org (and all constituent team members) needs to think about problems end-to-end. When you notice a problem, setup monitoring to collect metrics about the problem and alert on it before it becomes a downtime. Have ops write down their experience with that problem into a playbook, then have dev figure out which parts of the playbook can be automated, or if the system design can be iterated to remove the problem class altogether. If you're a dev and you don't listen to ops, you're just as doomed as an ops guy who doesn't read the dev's manuals.