For me it's similar'ish. My approach is this: I'm a developer but I want to be involved in all deployment related steps and ideally deploy the app from day 1 my

For me it's similar'ish. My approach is this: I'm a developer but I want to be involved in all deployment related steps and ideally deploy the app from day 1 myself. The latter step is usually underestimated and helps to keep the timeline. On the other hand I learn early on how the app behaves during runtime on a real environment and can take precautions that maintenance on application level is almost only needed when deploying. A dedicated Ops team is nice when it's limited on the application level to very basic tasks like just restarting the service. If the services are not under-provisioned and have a properly set up process/app orchestration in place this is actually a non-task... Under these conditions I don't mind being on-call every now and then or even all the time if done right.