Not at all. I think the media is overestimating the effects of this virus. The world will realise that soon and everyone will calm down.
I can see this effect right now in Italy.
I in one of the affected regions and while a few people have been queueing to empty shelves at the supermarket, I'll go tomorrow for a normal weekly grocery shopping. Supermarkets are fully stocked again and everyone is doing well.
The main issue is in people's mind, at least right now.
Ok, but then what's the point of splitting it in the first place?
The way I see it is to split your domain so that a team owns not only the code, but also the model, the data, the interface and the future vision of a small enough area.
If a service owns all the data, then someone who needs to make any change is bottlenecked by it and they would need knowledge beyond their domain.
So the key is defining the right domains (or domain boundaries). Unfortunately most people just split before thinking about the details of this process, so the split will sooner or later hit a wall of dependencies.
Unique storage for multiple services sounds like a recipe for disaster.
The purpose of splitting services, at least one of, is to decouple parts of the code at a fundamental level, including storage and overall ownership thereof.
You're probably better served with a modular monolith if you really can't break storage up.
I'd much rather live in a country where disparity is not clear like in Austria than the US. And I'm a software engineer but that doesn't change how I think about social justice.
It brings value in the long run and makes retention easier. If I work for a company who pays differently based on location, I'll soon be searching for a company that pays the same based on level of seniority or other internal criteria.
Tel Aviv has many examples of good 20th century urbanism.
London Barbican is also a great example.
I'm sure there are more but we'll see which ones will be true classics over time.
An MVP should consist of the minimum work required to test an hypothesis.
In this case the hypothesis is: "People would buy a browser if it offers an ad-free experience".
So it's viable according to that idea.
Viable doesn't mean useful though :)
Shantaram is a great novel that is very easy to read regardless of the book length (it's very long). If you are even remotely interested in India and/or travelling it is a must.
OT: out of curiosity, did you get the one with FHD or WQHD screen? Having nightmares trying to set it up with an external monitor and scaling UI properly in Gnome.
Just scrub the footbed with water and marseille soap. It always worked for me with the traditional ones made of leather.
A lighter method is to scrub some bicarbonate of soda gently for a couple of minutes, leave for a day and then clean up.
This sounds really expensive! Are all contracts similar in the US?
In Italy I pay EUR 5.99/mo for 30gb and unlimited calls including to any European country and some international countries too.
Doing TDD in Python every day. Done that with other languages in the past and can't see any difference, so I'm curious to understand why you have this feeling.
If your application mostly reads from the DB then don't use a ORM. I think ORMs shine when you need to save/update a domain model to a relational DB.
In the CQRS world, a fairly typical choice when using a relational DB is to use a ORM for the write side and raw SQL for the read side.
Robert Sedgewick's Algorithms has been one of the best for me, not only as a general refresher on algorithms, but also as a way of better understanding complexity notations.
a relatively newcomer in the space is Nomad by Hashicorp, very promising and with simpler architecture. Of course it makes even more sense if used in conjunction with Consul and Atlas from the same company. It's still young and buggy though.