Is there a github repo for her time series forecasting experiments? I'd like to see her code and be able to run it against my own data sets.

Thanks for the detailed reply. I'll definitely check this out. What type(s) of projects have you created that use this?

100x.bot is completely powered by daptin, canaster.in (work in progress, i am redoing the frontend in webgl) is also running on daptin. there are various internal company services which are running on daptin which i cannot name here.

almost any project which matures to requiring a user authn/authz (and there are always assets owned by users) i default to using daptin

I have hardened it a lot over the last 10 years, especially in terms of transaction/concurrency/security. happy to help you setting it up in your project. you can dm me ( x.com/phparth ) or leave an issue on the github repo

Thank you!

https://datetimemate.com/ - An old-school terminal-styled date/time calculator

Compute differences between dates, times, durations and timezones

Underlying CLI and Go library: https://github.com/jftuga/DateTimeMate

I like running Linux on older Dell Optiplex systems that you can buy off of Ebay. They usually come with 8GB ram, 256 or 512 SSD and usually 4 to 6 cores (maybe 8). All of the ones I bought use Intel CPUs.

They run Debian or Ubuntu great although I usually run them headless and just SSH into them. One experiment I did was with Talos / K8s with about 3 of these and it worked great.

What do you think of this: https://github.com/synadia-ai/synadia-agents

That sounds interesting too, very cool!

I think this is a good idea as it happens anyways even in GitHub.

I like to rebase/squash before pushing because it keeps the commit history cleaner. However, I do like your idea so I guess I could also do a squash/merge after approval (which I already do, anyway).

Some interesting tid bits:

* we had to resolve a variety of bottlenecks that appeared faster than expected from moving webhooks to a different backend (out of MySQL)

* * redesigning user session cache to redoing authentication and authorization flows to substantially reduce database load.

* we accelerated parts of migrating performance or scale sensitive code out of Ruby monolith into Go.

I'd like to know what database backend they migrated to. I was also surprised to read that the migration from Ruby to a more performant language had not already been completed. I assume this is because it a large code base with many moving parts, etc.

Another interesting bit: they are hitting performance issues due to the rise of monorepos. GitHub and frankly Git were not designed for monorepos

Yet the Linux kernel is a monorepo

The Linux kernel is pretty small

Try google3

Wow, this is super useful. Thanks for making this!

Nice layout - I really like this.

Thanks!