Readit NewsAlso taxes in Japan seem to be quite high, on par with the Netherlands.
Baltic states look interesting! According to google Estonia has a fixed 20% income tax.
Although I'm not sure how to pick between them, all three look kind of similar. I've also surprisingly never heard about someone migrating there for financial purposes. I've always thought of the US as the only place to make a lot of money.
You are right about the taxes in the Baltic countries - in all three you can get ~20% effective tax (minor differences between the countries). And they are really similar otherwise.
Most people in a similar situation to yours pick Estonia. It is the most focused one on tech, supporting startups, and overall the most developed one (relatively speaking). Also seems to be the most expensive of the three.
Lithuania has the most business-oriented culture in my experience. Otherwise a nice and chill place.
Latvia is maybe not the best in the above regards (though, not too far off either), but I would say it has the most stuff going on and things to do overall.
What I love:
* Total mental clarity during the first half of the day, can focus fully on work or life responsibilities without a single thought about food.
* Freedom to not have to organize the day around food (making choices, planning logistics, "wasting" time). Pays off big time when traveling.
* Never inconvenienced or slip into grumpy mode when for whatever reason I don't get food.
* Eating a lot of high-quality home-cooked food - as I love cooking (when I have time) and I don't depend on eating out / ordering food / quick-prep meals as much.
* Bonus: great ROI of the occasional first alcoholic drink of the day (on a more or less empty stomach). Not a health advice!
Other touch screens (or similar things) I dislike:
- the controls on my stove top
- the controls on my monitor
- the controls on my tv
- the controls on my thermostat
- probably more
All of these should have physical buttons for the limited number of functions required. Or, at a minimum, for navigation and confirmation. Touch screens there suck.
My wife's car has a touch screen on the control/infotainment center whatever it's called (where the radio is), and a few physical buttons on the steering wheel. There are two clocks: one on the control center, and one in the main dashboard display.
The dashboard clock is controlled by the buttons (just one for menu nav and one for confirm selection) is super simple and frustration-free to change. The touch-screen controlled one is a shitty pain the ass.
By far the worst though is my touch-controlled stove top. Just give me some damned knobs.
Guess what happens during the cold season when you you've got your gloves on? Yep, absolutely nothing! (bonus f.u. points if you are carrying stuff and cannot easily take the gloves off)
Luckily have a fully analogue car so I'm maintaining my sanity somewhat.
- Configure Vacuum and maintenance_work_mem regularly if your DB size increases, if you allocate too much or too often it can clog up your memory.
- If you plan on deleting more than a 10000 rows regularly, maybe you should look at partition, it's surprisingly very slow to delete that "much" data. And even more with foreign key.
- Index on Boolean is useless, it's an easy mistake that will take memory and space disk for nothing.
- Broad indices are easier to maintain but if you can have multiple smaller indices with WHERE condition it will be much faster
- You can speed up, by a huge margin, big string indices with md5/hash index (only relevant for exact match)
- Postgres as a queue is definitely working and scales pretty far
- Related: be sure to understand the difference between transaction vs explicit locking, a lot of people assume too much from transaction and it will eventually breaks in prod.
I recently went from:
* somewhat understanding the concept of transactions and combining that with a bunch of manual locking to ensure data integrity in our web-app;
* realizing how powerful modern Postgres actually is and delegating integrity concerns to it via the right configs (e.g., applying "serializable" isolation level), and removing the manual locks.
Any time I asked this question it produces some joyful brainstorming. It doesn't matter if it is a room full of highly technical people(engineers, mathematicians) or a family dinner.
I've already heard most of the arguments from the topological definition of a hole to difference between a hole, a cavity and a hallow but it is still very fun for me to watch people getting excited over such a boring looking question. (:
If you walked down the street and chose the first 20 people you met and threw them on an engineering team, you'd expect the engineering product to suffer. The same applies here. We threw a whole bunch of people into working from home with no skills or experience related to WFH and, as you would reasonably expect, they are floundering.
This isn't the fault of any particular tool, rather inexperienced people not understanding how to properly use the tools they have available and conduct themselves generally. I anticipate that things will improve as experience grows, but it is still early days. A few years is still quite junior. We don't expect great software from someone who has only been programming for a few years, so we shouldn't expect great WFH ability from someone who has only been working from home for a few years.
As a long-time remote worker I also noticed (especially in early 2020) that a significant portion of people were struggling simply because they assumed they can continue doing things _exactly_ like at the office, only at home.
No, it's a considerably different setup, and you (and your team) have to adjust your processes accordingly:
• Slack is not a (chit)chat. Be precise about what you want and provide enough context to the reader. Small niceties are important, but reduce the overall fluff.
• Pay attention to how you structure your messages / exchanges. Take advantage of the formatting features. Make your messages easily digestible. Small things add up over time.
• Take notes / write documentation more than before.
• Embrace tools that you didn't need previously (for communication, brainstorming, whiteboarding).
I believe work in a remote setting is generally more productive if done well.
P.S. Not trying to dismiss the highly extroverted folk who _need_ human contact to feel normal day-to-day. I believe that's a separate topic entirely.
We need to stop doing them.
What we need to stop is put unreasonable emphasis on association studies (i.e., interpret the results incorrectly).
The only notifications I'm using are for phone calls from selected contacts, mainly my family.
I've gone the extra mile and set my phone to be entirely in grayscale, and have never been happier.
(Doable on Android at least, look under "Developer Settings")
I want it to be true, but I am wary of the fact that people say that not because it is true, but because they also want it to be true.
My own anecdotal experience suggests that, yes, people do slack off more if they are remote.