We are in a similar situation, both working from home. It very much depends on how lazy we are during the day. If musli bowls and lunch plates haven't been handwashed when we start cooking dinner it's a "dishwasher day". We have a half size one, which means one day's worth of dishes fills it up at least 3/4.
I suspect it might be more water efficient and energy efficient to do this instead of repeatedly heating up water, which takes 30s or so and wastes a lot of cold water / hot water that gets left to cool down in the pipes.
I am not a designer/UX person but still thought I would give it a go. I couldn't get through more than 30% of it because of how boring and repetitive it was.
Petrol stations in Germany make almost no money on petrol. I think it was something along the lines of 2-3 cents/liter. I am quite sure that they will be happy to have customers stay in their shop for longer.
I would love to know what the problem is. We do dozen of deployments every week with a ALB + ECS + Fargate setup.
We upload a new container image, create a new task and launch as many tasks as desired (so if we want 2 containers running we launch 2, for a total of 4). ALB calls the /health endpoints on the new containers and if they pass the healthchecks it drains connections to the old containers and stops the tasks. This has worked seamlessly for a long time now without any downtime during deployments.
EDIT: I should mentioned that we are using AWS CDK for all of this. All it does is register a new task as the default task for a service and ECS/ALB does the rest.
I suspect it might be more water efficient and energy efficient to do this instead of repeatedly heating up water, which takes 30s or so and wastes a lot of cold water / hot water that gets left to cool down in the pipes.