sqlcommando

second link should be https://radiolab.org/podcast/good-samaritan

Good teachers are worth six figures easily.

pgbouncer supports session and transaction pooling. With session pooling a connection will be associated with the same session throughout its use. With transaction pooling each transaction on the connection could potentially get a different session.

I think "web app" is too broad a category to have this kind of discussion over.. for a lot of web apps 1.5 updates per second could be considered a reasonable limit. Many people work on web apps that do 100x that and don't consider themselves to be working at any particular level of scale. 1.5K updates/sec is not uncommon either, in different settings -- high-traffic internal web apps can hit that in a single company, and the people working in those contexts don't consider that too special either, not to mention public facing websites like GH where many people start their careers without having seen anything different.

"Sleeping pills" is classic celebrity cover for harder stuff.

It is true that good money can be made in tech, and that some companies pay > 100K/year out of college, but it's worth pointing out that even in the US this isn't true in general or in the majority of cases. There are a lot of people in tech making less than that even years out of college - it's largely a function of where you live and whether you land your first job at a handful of particular companies.

You can refer to https://www.bls.gov/ooh/computer-and-information-technology/..., or https://www.bls.gov/ooh/computer-and-information-technology/... - those people are all in tech, and most aren't new grads. Median salaries for "computer programmers" and "software developers" are 91K and 107K respectively.

"Everything app" seems like a great vision. Let's not get hung up on the details of, you know... everything.

I don't understand what you mean by this.

  [~] $ cat main.go 
  package main

  import "fmt"

  func main() {
   x := []int{1, 2}
   append(x, 3)
   fmt.Println(x)
  }
  [~] $ go run main.go 
  # command-line-arguments
  ./main.go:7:2: append(x, 3) (value of type []int) is not used

and if you assign the result of the append to something else, x is unchanged.

I dunno about the m1 aspect of this but postgres and redis for typical dev work shouldn't require more than a gigabyte or two of RAM when running together. 32-64GB is more like heavy traffic enterprise DB territory...

I was curious about your claim about the lottery...

This article has a quote from a California Lottery spokesman saying 138 people won a million+ in 2021: https://patch.com/california/orange-county/californias-top-1....

This article also from 2021 estimates 7000+ millionaires from 35 bay area IPOs that year: https://www.nytimes.com/2021/03/08/technology/silicon-valley...

When you factor in the number of lottery tickets sold each year vs the number of people working for startups, and the fact that at a startup you do have at least some degree of control over the outcome (that's part of the reason you would take the job), it seems like the lottery comparison is pretty far from correct in reality.

https://learn.microsoft.com/en-us/azure/data-explorer/kusto/... gets linked here from time to time, along with this similar one https://github.com/prql/prql. I'm not sure either one claims SQL parity at this point but one thing they each have going for them is queries start with the entities, rather than the columns, which makes type-ahead completion more natural.

I think if you were going to do SQL over you would probably do it that way. SQL is definitely not perfect or optimal, just ubiquitous.