kroolik

(...) that I might get a couple of times

email alerts when GitHub, (...), go down

bold statements when the Missing Github Status Page shows 87% availability.

I didnt mean Google, but there are those we pages that, for example, scraped Stackoverflow.com just to provide the very same content

It first gives you a page of ads, then a scraped version of the solution that steals content for ads, and then the amp version of the solution that doesnt work because js or what not.

Build with what pieces you can find, rather than plan the perfect structure ahead. Improvising keeps the creativity going! Wheres fun if sorting legos sucks all the Joy from it

Horridly inefficient. Just unfold the loop.

Those FAANG devs have milions of (social) lives on the line, though. Every day.

You can apply dynamic env to other jobs by exporting an env file as a dotenv artifact. So first job creates a dotenv file and export it as artifact. Second depends on the first so it can consume the artifact. https://docs.gitlab.com/ci/yaml/artifacts_reports/#artifacts...

Why do you need the vector if you have already compared the query with the result candidate?

Its not difficult to imagine a person saying 'i have nothing i want to share here' be stigmatised in future. As a person who doesnt want to work together and be part of the company culture.

1) IMHO, people use quantifiers like majority, mostly, rarely, etc not because its the absolute truth, but because its their subjective PoV

2) Dont trust everything you read on the internet. A lot of it is skewed by personal biases.

So they have the monopoly on repairs

That's some National Geographic clip. Now, show us the demo!

High level devs still do low expertise things every now and then. Or rather, designs need to be implemented, eventually.

Re whys: this can be even simpler. I sometimes catch myself rapidly click the mouse button a second time with my finger, right after the initial click. This is not intended and may be related to low resistance on the button itself.

Link requires premium account to read the actual data

You can peer-connect vpcs cross-account

Are page misses still a thing in the age of SSDs?

Yes, although timestamps may have collisions depending on resolution and traffic, no? Bigserials (at least in PG), are strictly monotonic (with holes).

Yes, but updates are covered by updated app code

PG bigserial is already strictly monotonic

When running a batched migration it is important to batch using a strictly monotonic field so that new rows wont get inserted in already processed range

Having an index over the uuid is equivalent to it being a PK, so why would you bother having both?

The locking part is often forgotten when discussing zero downtime migrations in postgres. As more and more operations become fast, more engineers will get bitten by this.

Ive telling this to engineers in my org for such a long time, now I also have a nice article to share :)

BTW, you don't need the pg_sleep and hurry with the execution. Simple BEGIN and COMMIT/ROLLBACK will give you infinite wait time :)

I believe the fact that V8 vulnerabilities are not "classic" memory corruption can be attributed to their developers' experience and review processes.

This doesn't imply, though, that another project in C++ will share these traits.

Its more like "Im interested in subscribing and paying more"

As I started to think for some time now: you can have a challenge or a solution.

As engineers, we are often tempted to challenge ourselves, straying away from the latter. There is less perceived pride from following simple solutions.

We use IF NOT EXISTS to bring non prod environments in sync with prod. The size of prod requires some migrations to be done separately over course of days, in separate transactions. The IF NOT EXISTS clause then brings dev and non prod envs in sync.

Fail and learn from your mistakes. Or hire developers and fail and learn together.

Make sure to create indices AFTER the data is in. Its way faster to create indices from data than create them empty and insert data.

Also make sure to set maintenance_work_mem high as it helps with index creation

If im not mistake, you can do this with no downtime by creating a regular index CONCURRENTLY and creating a not checked unique constraint. The constraint applies to new insert/updates only. After that, you run VALIDATE on the constraint and it will be a fully fledged unique constraint.