It's a good way to get started, and then incrementally type as much as you can, preferably everything.

Later on, or if you start a new project with TypeScript, it's a good idea to turn on noImplicitAny and only allow explicit any in very specific framework level code, unit tests or if you interface with an untyped framework.

The hassle really pays off later.

It's also ok to support neither or to say it's too complicated to pick a side.

Depends on what you already know.

Functional languages like Haskell, Clojure or Erlang have a reputation of being hard to grasp.

Rust's borrow mechanics are hard for some people at first, especially because it's very unique to the language.

Javascript can be frustrating because it also has some rare features among popular languages, and uses the same keywords for different concepts. It's not bad at all once you let go of your assumptions and dedicate the time to understand how it works under the hood.

C++ is also notorious for being hard but I haven't used it for a very long time so I can't say anything about it.

Before buying your fitst home:

• bring someone with more experience than you to have a look at it, maybe even a professional
• scout out the area (on foot) during the day, evening and night
• visit local businesses like cafés, restaurants, bakeries etc.
• look at statistics like crime and air quality
• have a talk with the neighbors, get a sense of the community if you can, otherwise just observe while taking walks
• if applicable, call the home owner's representative (or whatever the equivalent is where you live), ask them about the home, neighborhood, community, expenses, plans for the future etc.
• have a set budget of how much you want to spend on it before you move in, don't overstep that amount

That's why in Star Trek the holographic NPCs were programmed to not find this odd. Same when the program took place on Earth in the 20th century, they saw alien species like Klingons as humans.

The title makes it seem like it's a wide spread thing in the industry but according to the video it's 3 frameworks.

Yeah, it's additional work but I've found that really convoluted or complex type definitions usually mean you should consider refactoring. Of course this is a bit different when it comes to developing frameworks where you might want to support a bunch of different use cases.

Maybe I'm biased because I've been using TS ever since it first came out.

Credit scores are a scam to sell credit cards.

You take small loans each month via a credit card that you have to pay back. This increases an imaginary number that lets you take out bigger loans in the furure.

This is all tracked by private companies that you trust with your personal data. That, or you'll not be able to take out a loan if you want to buy a house or start a business.

If you have a good credit score it means that you don't overspend or forget to pay, which you can also achieve with a regular debit card by default. This doesn't serve people, only the banks who expect that a number of people will overspend or not be able to pay their loans back.

Credit cards alone aren't the problem. Forcing them on people with the credit score system is.

I drink carbonated water almost exclusively, it's the same water, just with some carbon dioxide to make it sparkle.

It has no downsides afaik, it's a bit more acidy but not as much as sodas, and it might make you burp, but that's it.

Could be someone who's genuinely trying to understand someone's viewpoint, but it reveals inconsistencies in the other person's logic, so they get irritated.

Where's "here"?

In some countries they'll fail you if you don't bribe, even if your driving was perfect, in others they'll just overlook small errors that aren't too dangerous.

There are places where if you bribe they'll let you pass even if you can barely drive, in others they'll call the police on you if you bring it up.

Ask around locally, you should definitely not bribe if you'd be a danger to yourself and others.

You misspelled pacman

I was working on an enterprise web application, there was a legacy system that everyone hated and we replaced it with a more modern one.

We got a ticket from our PO to introduce a 30 sec delay to one of our buttons. It sounded insane, but he explained that L1 support got too many calls and emails where users thought said button was broken.

It wasn't, they were just used to having to wait up to 5 minutes for it to finish doing its thing, so they didn't notice when it did it instantly.

We gradually removed that delay, 10 seconds each month, and our users were very happy.