vazamb

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.

Which also might solve the mystery of why it's only available in the Netherlands? No need to built a different keyboard.

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.

Why this being downvoted:

You need to use a process pool in Python, thread pools are for I/O bound tasks and cannot use more than 1 core.

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.

PGMs also provide the intuition behind GANs and variational autoencoders.

I think the better scalability does not come from lambda itself but because you have to design for share-nothing concurrent executions from the start.

I think it is already through libraries. At least for lambda in python you have libraries (Zappa for example) that allow you to write basic flask and Django apps and then deploy them to lambda. These apps can still be deployed the "old" way with no or minor modifications

Hey, I just finished your book. Loved it! I am out of uni already and uses it to brush up.

I find it interesting that one of their major pain points was data schema. After having worked at places that use plain json and places that used protobuf I can highly recommend anyone starting an even mildly complex data engineering project (complexity in data or number of stakeholders) to use something like protobuf, apache arrow or a columnar format if you need it.

Having a clearly defined schema that can be shared between teams (we had a specific repo for all protobuf definitions with enforced pull requests) significantly reduces the amount of headaches down the road.

Taxpayers already pay quite a bit to keep the cash system running. I think it would make sense for the state to provide baseline infrastructure for electronic payments.

It is ridiculous how hard it is to get ANSI keyboards here (Germany). Laptops are ok (Macs, Lenovo and Dell) but external keyboards (especially mechanical ) and any other laptop brand are a huge hassle.

I am glad other people get that feeling too. A lot of pop-sci books are not terribly bad but could be cut down to 1/4 of their length. Another example for this is "Deep work" by Cal Newport. Great idea, something to actively think about. But not necessary to be spread out across 300 pages...