Can't you simply make a PR against the other PR's branch?

Yes, but the UI isn’t great for it. When you make a change in a base branch and push all the branches ahead of it, GitHub litters the UI with “force push” activity, even when no one has even started reviewing the PRs yet. This creates tons of visual noise in the PRs to sift through.

> It’s an itch – a feeling that something is really important, and you need to do something about it, and nobody else can possibly do it except you.

Might be difficult to believe, but I strongly believe there are things that no one else on this planet would do except one of us.

To add to what others have said, I would ask every person in my team what's the most important think I need to know.

Also ask the name of someone I need to meet. This helps find the load-bearing people who are sometimes invisible on the org chart.

I'm running my website with Jekyll for around a decade. Interestingly I use sqlite for comments submitted to the server (cgi-bin, mind you) and populate the pages during build. Your plugin is a perfect match for my usecase. Will definitely consider it. Nice work!

Filter this page [1] for newly created profiles and see how it grows in realtime.

https://firesky.tv/

What the hell am I looking at here!? This surely can't be ALL the messages right!? That would be amazing.

Someone want to do the math on bitrates?

Seems reasonable to me. If only 10% of the user base posts just twice a day, we are talking about 4.2 million posts in a single day or about 48 posts/second.

Well, I recently used it in a small PostgREST-subset query builder I wrote in case the query builder received an input more complicated that what it could handle. I found 418 a natural response in this case. In retrospect a 5xx (edit: or better 422) error is more appropriate, however.

FWIW, one python project I'm working on uses an obscure Framework, and ORM. I was contemplating to convert it to FastAPI+Pydantic, however the amount of effort needed was no different than rewriting the whole project.

This was literally among the best comments I've read today and I couldn't stop laughing out loud.

Can only second you. His style is by far my most favorite among all other technical authors. And thanks for the reminder, time to get another one of his books.

> His style is by far my most favorite among all other technical authors.

All authors should learn from Kernighan's books (co-authored with Plaugher/Ritchie/Pike) on how to write technical books. 90% of all the computer programming books published nowadays are too verbose (why the hell are they so huge?), meandering over inessentials, lack of clarity in language, a paucity of clear and precise examples and overall just a waste of paper. Reading them is more of a chore then enlightening whereas all of Kernighan's books are only a little over 200 pages, dense with knowledge and a pleasure to read.

In discussions with colleagues they blamed the absurd demands of the publishers in terms of hitting specific volumes (in pages), which oddly reminds some past relationships I had with management and sales departments as a developer.

I wish we had all these goodies in default linux console (I know about and try to use kmscon sometimes...)