KingEllis

I had never considered until now that my left thumb never touches the keyboard.

Their website says 2014. Amazon says 2018. But definitely not 2024, unless I am missing something.

I would not use this because of the distracting stuff on the borders. Hardly "minimalist".

Can someone explain this? One three occasions in the essay, including the title. he adds a cryptic "2001 Tor". What does that mean? It does not exist in the many other mentions of the same book title. Also, Amazon believes the publication year is 2002. What is "2001 Tor"?

Well, either no, or I would not know, as the point is C++ programmers are not nearly as self-congratulatory.

100 percent

Can I guess, from one not in the field, and no one bothering to define it? "Large Language Model"? I don't think it is a "a graduate qualification in the field of law". JFCFFS

About a minute in, I could not figure out if satire or self-absorbed. I stopped reading.

The absence of the go binary as a tool (i.e. "go get ...", "go install ..." etc.) is odd, considering that is what has been eating Python's lunch lately.

Another starting point: https://github.com/dagger/dagger/tree/main/ci

> * Don't even think about using ML for this, that doesn't solve biases, it just hides them in a black box.

Can you clarify: what is "ML" here? "Machine learning", ML the language, MatLab, "machine language" (a.k.a. assembly), Matt LeBlanc? I'm out of ideas...

Comparing with a similar recipe I have, those look to be teaspoons.

Speaking as someone ashamed at having never taken Calculus, I didn't know there were 3 of them...

> the faux screen jump when Bowman nearly touched the edge, and instead shattered the glass. It really is brilliant, a movie within a movie.

> that the upright position of the monolith as it is presented is incorrect.

Can you provide references for either of these?

I have feedback on the Ubuntu 18.04 LTS Cloud Image that I am hoping reaches the right ears.

There is something about the way the disk is partitioned that makes the use of virt-resize no longer work (as it does for 16.04).

Specifically, I am referring to: https://cloud-images.ubuntu.com/bionic/20180124/bionic-serve...

The boot partion looks to be sda14 or sda15. But judging from the output of virt-resize, it appears that although these are sda14/15, they appear in front of sda1. (When virt-resize is run on sda1, sda14 becomes sda1, sda15 becomes sda2, and sda1 is now the resized sda3, and grub is confused.

  $ virt-filesystems --long --parts --blkdevs -h -a bionic-server-cloudimg-amd64.img 
  Name        Type       MBR  Size  Parent
  /dev/sda1   partition  -    2.1G  /dev/sda
  /dev/sda14  partition  -    4.0M  /dev/sda
  /dev/sda15  partition  -    106M  /dev/sda
  /dev/sda    device     -    2.2G  -

  $ virt-resize --expand /dev/sda1 bionic-server-cloudimg-amd64.img bionic0.qcow2

  $ virt-filesystems --long --parts --blkdevs -h -a bionic0.qcow2
  Name       Type       MBR  Size  Parent
  /dev/sda1  partition  -    4.0M  /dev/sda
  /dev/sda2  partition  -    106M  /dev/sda
  /dev/sda3  partition  -    25G   /dev/sda
  /dev/sda   device     -    25G   -

I am hoping this can be addressed before April, as I would prefer not to maintain my own LTS image (that doesn't have this issue).

I didn't know this for many years of listening to that album. But I was blown away when I found out that on many tracks, Stevie is basically playing every instrument. It's quite astounding. I found out by being really drawn in by the drum work of "Too High". I looked it up. Well damn, that's Stevie.

Ref: https://en.wikipedia.org/wiki/Innervisions#Track_listing

> PyPy exists and works as both an open source project and as a codebase, which is no easier to achieve than coming up with an idea.

I have no idea what you are getting at here.

Yip yip yip yip yip yip yip. Good.