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.

Wait what’s the missing number??

I think the problem is that it should be standard, but the LinkedIn poster is talking about it like her company is SO generous.

Owning an animal is a commitment which often requires money: food, toys, vet bills, etc. If you’re worried about yourself surviving, getting a cat will only make things worse. Which is bad for you, but equally bad for the cat.

All is not lost however. You should volunteer at your local shelter. They literally need people to just sit and pet cats. It would also give you an opportunity to learn their body language so you understand them better.

Yeah it ended before it even got started

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.

WebMD: it’s cancer

Hmmm

I experienced the reverse. Someone asked me “what’s a singlet?”, and I had no idea.

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.

You can do it!

I totally agree, but I don’t hear any discussion about how to incentivize developers to do it.

If AI makes creating new code disproportionately easy, then I think DRY and refactoring will fall by the wayside.

Would you, could you with your throat?

Nice pic! Looks like a Myna, but more grey. Maybe it’s the lighting?

OCI allows you to package arbitrary content in a docker image. In this case it would be a collection of k8s yaml files. Two main benefits of this approach are:

• Your gitops tool only needs image registry access, not git access
• The OCI image contains the final yaml. Your CI pipeline is responsible for generating the image.

Flux already supports this and I other tools to follow.

I think it would be helpful if you outlined where helm is falling short for you.

Personal opinion: I think packaging k8s manifests in OCI image format is probably the future. Helm, Kustomize, etc may still be useful in generating the yaml, but the “package management” part will be OCI image registries.

China wants to remove the adverse affects of gambling/addiction from it’s populace, not the world. This is just another facet like their social media restrictions.

Turn the wifi off, or take it somewhere where there’s no wifi, and start it up.