They can also shoot you if you’re near the person who didn’t pay the $2.90 fare.

Click bait. From an article last year:

These effects may be troublesome, but they are short-lived; re-ionization occurs as soon as the sun comes up again.

https://earthsky.org/todays-image/spacex-launch-punches-a-hole-in-the-ionosphere-red-blob/

I don’t understand how their decision 3 years ago “worked” and that’s why they’re changing the license again.

I remember reading that the banks who loaned him the money haven’t been able to sell off the debt.

* { display: flex; }

Which starship is this on?

But how’s the java support? If it’s better than vs code then it might be worth something.

I think basic or even complex stuff is fine in vanilla js.

The problems show up as you scale the team and code base. You can do a large project in vanilla js but you’re going to have to solve a lot of the same problems frameworks/libraries have already solved. Maybe it’s worth it, maybe it’s not.

But what is the game? I’m feeling pretty happy about it so far.

After that fiasco I can’t believe anyone still uses Wells Fargo.

Because it’s not about getting work done, it’s about having power over your employees.

If you message me your Google password then I’ll check for you. That way you won’t be at risk for catching a virus. You can never be too careful these days.

I wonder what it will be like on a long flight with this feature: there is an army of unknown Bluetooth items moving with you.

Lesson learned: always use your girlfriend’s browser to look up how to do crime.

Not saying anything about good or bad, but trunk-based development doesn’t work when the business requires you to have multiple releases under development concurrently.

I would recommend checking out Rollup (https://rollupjs.org/introduction/).

Rollup is one option that will fit a lot of situations, but there are other ways to bundle a library/module that focus more on how you want to use it. Is it used by other libs, by a UI application, etc.

I know of 2 projects that wanted to migrate from Oracle to Postgres, one of which was successful. Both migrations were driven by cost savings–Oracle can get exceedingly expensive.

In both cases there was up front analysis of Oracle specific features being used. A lot of that could be rewritten into standard SQL but some required code logic changes to compensate. Vendor lock-in is insidious and will show up in native queries, triggers, functions that use Oracle packages, etc.

Changing a project’s underlying database is rare, but not as rare as it used to be.

Take your example of adding a field to an entity. Just because you’ve made that code change doesn’t mean other code should be using it. Who should be using it and how is determined by the business rules.

Also your interest in ensuring it is “properly” used is impossible to enforce. What’s considered proper even for existing code can change over time.

Hmm I think you’re looking for a technical solution to a non-technical problem.

If you update your tests to reflect proper usage of the new field then you can catch potential errors.