eezing

You buy Salesforce because your boss told you to. If you believe differently, you’re the boss.

“Amazon Aurora Serverless is an on-demand, autoscaling configuration for Amazon Aurora. It automatically starts up, shuts down, and scales capacity up or down based on your application's needs.”

It pays to be a hard worker… thanks for the tip.

Aren’t there enough frameworks available to avoid Webpack? Seems pretty low level for app developers these days.

I’ve done Webpack configurations and Browserify before that. I’ll be glad if I never go there again.

Google Docs is pretty efficient. It loads incredibly fast and you never have to manually update it. But, it clear has limits… 30MB Word files.

Slightly slower is an understatement. Absolutely useless on touch. No fault of Atlassian, but why use the HTML 5 API knowing it’s trash on mobile?

Infrastructure as code can be useful for complex systems.

These days, the cloud providers have pretty good abstractions that IMO diminish the need for IaC for many use cases.

Being multi-paradigm with a Java like syntax doesn’t hurt.

You’ll convert, it’s only a matter of time.

Can do this for free via GCP BigQuery console.

I believe AlloyDB is GCP’s flavor of AWS Aurora.

We shouldn’t assume that this schema was designed all at once, but rather is the product of evolution. For example, maybe the external_id was added after the initial release in order to support the creation of unique ids in the application layer.

AlloyDB on GCP could be a good fit here.

I’ve been using a Makefile in front end projects for years- use it for all dev, build, test, and deploy scripts. Local users and GH Actions use the same Make targets. Our GH Actions are very lean.

If reusable frontend code for your within a single organization or business unit is important, then having separate repos is crazy.

A monorepo with separate build pipelines is better, but still unnecessarily complex.

A framework like Next.js can do the heavy lifting for you. One build pipeline where components are shareable, and pages/routes ans entry are isolated during development and can be deployed independently if required.

Computers weren’t on my radar until my grandmother surprised me with one. I came home from school and there lay 2 huge boxes. I was on my own from there.

I was given the opportunity.

“The bill was passed by the Senate Judiciary Committee on July 11, in a 10-1 vote”.

Do they use the metric system in San Francisco?

“…can be selected for copy-pasting by double-clicking”

Details matter.

The auto select ruins the game

No vendor lock-in here. Been running NextJS on GCP Cloud Run for years and each major release has become more Docker friendly. Just my experience.

Less sleep is correlated with more device, tobacco, and drug usage. Weird.

But yes, school shouldn’t start before 9AM.

Was the article created by a bot?

Correct. While data-loader facilitates data loading, type resolvers in GraphQL is where the solution starts.

Just run “npm ci” next time.

In the hospital after my son was born, my wife and I were coached on breast feeding by the staff. The coaching was overall helpful; however, one of the recommendations was to avoid pacifiers. We endured two nights of crying in the hospital and a few more at home before giving in to the pacifier. It was a game changer, we slept well after that.

Advice will come from people with beliefs that may differ from your own. Additionally, what works for some may not work for others.

Here’s my advice. If your baby is crying and you’re not sleeping, make a change.

P.S. Before trying the pacifier, we ruled out hunger as the cause for crying by supplementing with formula.

I’ve hidden all content from Fox News and CNN in Google News. It’s great.

Not using a framework will harm the maintenance of your software.

I’m in favor of Array.smoosh

Quest hardware is fantastic, but content is king.

The top selling titles on Quest have been at the top for years. The Apple App Store model alone will not catapult the platform.

Meta should deprioritize Horizon (a Mii lookalike ain’t it) and spend the next 10 years developing 1st party titles. Set the benchmark. Learn best practices. Let the technology evolve.

We’re not ready for Ready Player One.