* { display: flex; }

Which starship is this on?

What’s their ticker? I looked up BSOD but that’s not it…

YOUR ACCOUNT HAS BEEN SUSPENDED BECAUSE YOU DARED TO COMMENT WITHOUT PROVIDING THE EXACT SOLUTION FOR OP’s PROBLEM (shame on you)

Wait what was the solution?

Found a solution, thanks everyone!

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.

I do microclouds in the service.

Yeah but it’s just going to get better at magicking. Soon all us wizards will be out of a job…

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.

Good one, I hope others can learn from my mistakes

SQL-99 called and wants it’s joke back

I think of XHR as more of a low-level API. Most of the time though you don’t need access to those low-level details.

The fetch API is bit higher level and nicer to work with.

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.

These days this reads as some kind of managerial feel-good comic.

60 Doodles in a Dandy

The article is pay walled, but there’s no way they’re not selling that data. They’ll just sell it to a different middleman that isn’t technically a “data broker”.

I feel for this guy. It’s not just frontend though, I’ve seen it with backend, DBAs, etc. It really is just a reflection of what the business considers valuable.

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.