the difference between 38℃ and 94℃ is 100.8Δ℉ rather than the 100Δ℉ that was probably there in the original markings. It's the closest you can come to the correct values though, 93℃ is off by 1Δ℉
They then assumed 100Δ℉ = 56Δ℃, and applied that to the rest of the dial.
That means the values on the dial are off a bit, and should be: 38, 93, 149, 204, 260, 316, 371, 427
It makes sense to me that the weekend comes at the end of the week, but then again, I don't know what came first, the term "weekend" or the convention of Sunday being the start of the week in some countries
I think it's just one of those things that doesn't really make sense to anyone, but one way makes slightly more sense to some than others.
In reality there is no week end. The only periods that exist are days and years (and lunar cycles). Weeks are artificially constructed and it can begin and end whenever we want. I can see the sense in saying the week ends at the end of Sunday so the weekend is the bit before that. I can also see the sense in saying the week ends at the end of Saturday and the weekend is around that.
I also used to have this impression, I think I got this from Rails and Django docs, maybe you read something similar?
> Rails comes with built-in support for SQLite, which is a lightweight serverless database application. While a busy production environment may overload SQLite, it works well for development and testing. Rails defaults to using a SQLite database when creating a new project, but you can always change it later.
> By default, the configuration uses SQLite. If you’re new to databases, or you’re just interested in trying Django, this is the easiest choice. SQLite is included in Python, so you won’t need to install anything else to support your database. When starting your first real project, however, you may want to use a more scalable database like PostgreSQL, to avoid database-switching headaches down the road.
The Django docs word it better - the chief problem with SQLite is that it's a _local_ database. If you outgrow a single server, you will now need to also migrate your database to something that can handle multiple external clients, or else figure out another way of making writes on one server be available to read on the other servers.
just set the timezone of your devices to UTC, and you're done! Actually getting other people to schedule meetings with you in UTC is going to be a bit trickier though.
for the Netherlands, check out tweakers.net[1] for your computer parts (they have an extensive price guide that will show you which webshop has the best prices and delivery speed). If you need them in a pinch, MediaMarkt/Saturn usually has what you need at a premium.
for living room furniture... Most of it is from IKEA
Thank you. I've been building a startup in California and have been dreaming of moving it to Amsterdam. Been learning Dutch over the last year and been trying to find the best information on the most effective way to migrate over. :)
The highest tax rate in the Netherlands is 51,95% (Note that this only covers anything you make over ~70k+ a year, 0-20k is taxed ~35%, and 20-70 is taxed 40%). Then you pay 6-21% VAT over anything you buy, so yeah, in some scenarios you definitely lose >50% of your gross income to taxes.
You don't just count VAT, let's count everything: 150%-250% taxes on energy, ridiculous amount of fees and duties. As a Dane, we're probably the most taxed in the world and for a high earning software engineer it's approaching 75%.
The state enables a lot of stuff for you in return though, which we'd also have to count as a benefit if we "count everything". It's just infeasible to come up with a concrete number of how much they "take away" from your earned money.
I have the same benefits in the US as in Denmark (more or less). In the US the government take 25% of my income in Denmark it was around 75%. Personally I don't think the extra 50% is worth it. The only ones better off in Denmark is the minimum wage earners.
Looking at the reports, the UUID's are xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx, so V4 UUID's, which should be pretty hard to guess (barring bad PRNG, but that's a whole different problem)
Yeah, that gets you 122 bits of entropy (with a good RNG) so that should be fine. I mainly pointed that out just in case anyone assumes "UUID" automatically means "random UUID" and fails to check whether their particular UUID generator uses v4 or something else.
the difference between 38℃ and 94℃ is 100.8Δ℉ rather than the 100Δ℉ that was probably there in the original markings. It's the closest you can come to the correct values though, 93℃ is off by 1Δ℉
They then assumed 100Δ℉ = 56Δ℃, and applied that to the rest of the dial.
That means the values on the dial are off a bit, and should be: 38, 93, 149, 204, 260, 316, 371, 427