I can strongly recommend the SponsorBlock extention (also available in revanched).
jochem
joined 3 years ago
I always write it as a select, before turning it into a delete or update. I have burned myself too often already.
There are huge differences. One country came into existence due to a federation disintegrating, because its members called for independence. The other country came in existence because an occupier forced it upon the people living there.
There wasn't also a huge amount of migration involved with Ukraine. People mostly continued their lives when Ukraine became independent. The founding of Israel involved many Jews for all over the world migrating to that area. You can imagine that affects the people already living there.
It's also hard to imagine people will live in harmony when one side literally enforces an apartheid regime on the other side.
With Influx 3 the preferred language is gonna be their SQL dialect. Flux is on its way out and I suspect it will get deprecated in the near future. Flux saw very slow adoption and SQL can do everything as well.
The one that blew my mind is that plate tectonics is only a widely accepted theory since the 70s.
They're nice if they also migrate your db schema. That way you define your schema once and use it both to setup your db and interact with it via code. I do write raw sql for more complex queries, e.g. when there's recursion.
I was big into downloading before streaming services were a thing. Music streaming is one of the few services that's totally worth my money: no hassle and I rarely have to resort to other platforms to find what I want (very different from video streaming, which totally sucks when it comes to that).
Every country that joined the EU after the 1992 Maastricht treaty has to adopt the euro. Denmark signed that treaty, UK as well, but if they rejoin, they'd more than likely be treated as a new member.
Netherlands too. Amsterdam is even planning to change major inner city roads to 30km/h (minor roads already are).
Pretty standard sink in my neck of the woods. The part on the right has ridges and drains to the sink, so you can use it to put e.g. washed veggies or let dishes dry.
The name of the function, what goes in and what goes out in most cases should be enough to get a good idea on what the function does.
It also helps to make a diagram of how everything ties together. Just boxes and arrows is enough.
When writing your own code, it takes a bit of experience to know when to put something in its own function. It's very obvious when you're replicating code. It's also very common to cut things up when a function gets too big. Look for bits of functionality that you can give a good name.