HackerTrans
トップ新着トレンドコメント過去質問紹介求人

mteigers

no profile record

コメント

mteigers
·3 年前·議論
I've been a personal paying customer going on 2 years now. The biggest benefit I get from fig is their "build a script / cli" functionality. With it you can define UI elements like "list all branches" and you have a nice UI sector and then you can string together code snippets using the outputs of the UI elements. So I have some fig scripts that prompt me for half a dozen inputs and then execute bash and python based on the outputs.

Fig has been a godsend for acting as glue for one-off bash scripts that are added to repos.
mteigers
·3 年前·議論
Anyone have any thoughts as to ballpark costs to run this? My napkin math on the cosmo-db requirements is failing me (largely because I do not know Azure at all).

I'm wondering as a hobbyist / tinkerer if a solution like this is "affordable" (I know it's all relative)
mteigers
·3 年前·議論
I have no direct affiliation with this service (nor am I a user of it) but I recently learned about "Pool Together" which is a "lossless" lottery system. It's a daily lottery that happens automatically, you do not need to collect as it happens automatically, and you can withdraw all of your capital at any time.

I thought that was a decently novel use case.
mteigers
·3 年前·議論
I'm curious if you have any pointers for whole Mac config with nix-darwin. This is something I've just started looking at and at the moment don't have much more than a nix-shell with some nice-to-haves. Any tips / tricks / guides are greatly appreciated.
mteigers
·3 年前·議論
I do something similar but with HAProxy and a micro GCE VM which acts as my edge which hits a Tailscale subnet router and routes to my MetalLB install. Works _really_ well.
mteigers
·3 年前·議論
Ditto, my managed service at Google threw close to 3k 500s / second when I was still there. Anything from cosmic rays, faulty hardware bit flipping, hard drive failures.

We did, however, aggregate and group similar 500s and those did get looked at, but no way could we have looked at all errors.

The other thing, is that with resilient infrastructure, who cares about an occasional 500. Back off and retry. No harm done.