Felix Dietze

Please elaborate more, why it's bad.

I thought that the general idea was, that many different metrics are combined, because every metric in itself is not sufficient.

Great idea! How could such a work estimation system be implemented on github? I especially like, that the work estimation benefits developers of higher skill who could finish a task...

> P.P.S If we have to pick a metric, I think the highest reward should go for lines deleted I had exactly this idea before! :rofl: Less code is always...

> It would actually be a good metric, but it could result in code that is no longer readable and does not contain comments. Such PRs should simply not be...

Here's how I'm currently working around the problem in ScalaJS / AWS lambda: I only use skunk for typescafe query construction, but submit them using [pg-node](https://www.npmjs.com/package/pg)/[pg-connection-string](https://www.npmjs.com/package/pg-connection-string) (with scalablytyped). It also...

That sounds sufficient, thank you! How do we proceed? Is it something you can do quickly, or should I get my hands dirty?

I think I'll approach this soon. What would be the rough steps to implement it?

How about ditching the session pool of skunk entirely and refer to dedicated solutions like https://www.pgbouncer.org/ instead?

I finally managed to skip the type checking. This is working for me now.