4 ms·
When the company is five people, doing the deployment yourself is a necessity. When you have a dozen developers working on the same project, doing the deployme
by dsr_ 8y ago
When the company is five people, doing the deployment yourself is a necessity.
When you have a dozen developers working on the same project, doing the deployment yourself is a danger to the company.
- loriverkutya 8y agoThen we are a company living very dangerously, cause any of our developers can deploy :)
- dsr_ 8y agoWhat's the maximum cost to your company if one of your developers has a really bad day and deploys a release that accidentally allows all customers to see each others' data? For my company, that would probably be a death blow.
- lmm 8y ago> When you have a dozen developers working on the same project, doing the deployment yourself is a danger to the company. How and why? There may come a point where it's worth segregating deployment from development, but I'm certain it's a long way north of a dozen.
- workinfunk 8y agoReally? You put a dozen people on the same _project_? I find it hard to believe that your project is so unique that A) requires 12 devs and B) is also deployable by all 12 of them (without relying on automation) in a way that doesn't throw off any of the other 12.
- lmm 8y agoI don't know what you mean by "relying on automation" or "throwing off the other 12". Deployment is mostly-automated - put a note in our chat channel topic that you're deploying (or queue if someone else is already deploying), push a button to do a release and deploy as staging (and a small smoke test), do any manual testing (or investigation of logs etc. if something goes wrong), push another button to flip that deploy to be prod. Any of the 12 devs can do this (and does, we each deploy our own features/stories), any of the 12 devs can make changes to the deployment scripting just like with any other code area (some will be more or less familiar with them, but that's true of any area of the codebase). Nothing unique about it, quite the opposite.
- workinfunk 8y agoIf your deployment is automated, your developers aren't doing the deployment, the machine is, and the argument is moot.
- lmm 8y agoDevelopers automate things, that's their whole job. The point is that we don't have people in dedicated ops/sysadmin roles, and are better for it.
- workinfunk 8y agoI believe we are violently agreeing at this point.
- rootlocus 8y agoIdeally, you should trigger a deploy by tagging a commit in the VCS.