https://github.com/peterldowns
Always happy to meet a stranger, please reach out any time: hn @ peterdowns.com
[ my public key: https://keybase.io/peterldowns; my proof: https://keybase.io/peterldowns/sigs/9N-85LOZH1eJMXHLR70WroivxJB1is_s3ye5IT5xzxs ]
- Yeah unfortunately I think that it's not really possible to hit the speed of a TEMPLATE copy with MariaDB. @EvanElias (maintainer of https://github.com/skeema/skeema about this) was looking into it at one point, might consider reaching out to him — he's the foremost mysql expert that I know.
- Is this basically using templates as "snapshots", and making it easy to go back and forth between them? Little hard to tell from the README but something like that would be useful to me and my team: right now it's a pain to iterate on sql migrations, and I think this would help.
- Really interesting article, I didn't know that the template cloning strategy was configurable. Huge fan of template cloning in general; I've used Neon to do it for "live" integration environments, and I have a golang project https://github.com/peterldowns/pgtestdb that uses templates to give you ~unit-test-speed integration tests that each get their own fully-schema-migrated Postgres database.
Back in the day (2013?) I worked at a startup where the resident Linux guru had set up "instant" staging environment databases with btrfs. Really cool to see the same idea show up over and over with slightly different implementations. Speed and ease of cloning/testing is a real advantage for Postgres and Sqlite, I wish it were possible to do similar things with Clickhouse, Mysql, etc.
- Great books! Strongly recommend for anyone into fantasy stuff.
- That's a really cool prompt idea, I just tried it with my neighborhood and it nailed it. Very impressive.
- > and seems reasonable considering the benefits I receive.
> I would still make the same decision to purchase or abandon based on its value to me.
- I appreciate being able to pay for a service I rely on. Using self-hosted runners, I previously paid nothing for Github Actions — now I do pay something for it. The price is extremely cheap and seems reasonable considering the benefits I receive. They've shown continued interest in investing in the product, and have a variety of things on their public roadmap that I'm looking forward to (including parallel steps) — https://github.com/orgs/github/projects/4247?pane=issue&item....
Charging "more than nothing" is certainly not what I would call maximizing revenue, and even it they were maximizing revenue I would still make the same decision to purchase or abandon based on its value to me. Have you interacted with the economy before?
- I'm happy to see they're investing in Actions — charging for it should help make sure it continues to work. It's a huge reason Github is so valuable: having the status checks run on every PR, automatically, is great. Even though I'm more of a fan of Buildkite when it comes to configuring the workflows, I still need something to kick them off when PRs change, etc.
Charging a per-workflow-minute platform fee makes a lot of sense and the price is negligible. They're ingesting logs from all the runners, making them available to us, etc. Helps incentivize faster workflows, too, so pretty customer-aligned. We use self-hosted runners (actually WarpBuild) so we don't benefit from the reduced default price of the Github-hosted runners, but that's a nice improvement as well for most customers. And Actions are still free for public repos.
Now if only they'd let us say "this action is required to pass _if it runs_, otherwise it's not required" as part of branch protection rules. Then we'd really be in heaven!
- At CloudX (https://cloudx.io) we’re building a new supply-side advertising platform for mobile publishers. Yes, it's ads, and yes, there's AI involved, so stop reading here if that's not interesting to you.
It's a gnarly infra problem with huge scale, combined with an interesting product space that we think legitimately benefits from tasteful AI automation. We're doing cool things with Nitro Enclaves to prove that our auctions are fair. And our founding team have done this before with great success, first at MoPub (sold to Twitter) and MAX (sold to AppLovin).
We're hiring (all remote) for:
- Senior Fullstack Engineer https://jobs.gem.com/cloudx/am9icG9zdDogum5THF3fORqb1eEupFQx
- Senior Infrastructure Engineer https://jobs.gem.com/cloudx/am9icG9zdDo4vl4A1sEcc7sDQf8ZYiqR
- Senior Android SDK Engineer https://jobs.gem.com/cloudx/am9icG9zdDqPAWu1cxr3PmEuuTIdliI6
- Senior iOS SDK Engineer https://jobs.gem.com/cloudx/am9icG9zdDpOy3Qmt1fLsOu4gKwtwWTz
Our philosophy is to keep the team small, well-paid, and productive. We deploy every day and our monorepo CI suite takes about a minute to pass.
The best way to apply is directly through those jobs pages but if you have other questions you're welcome to email me at peter@cloudx.io. I always post here on HN because it's where I got my career started back in highschool; I will personally make sure you get a response if you apply.
- The beauty of mise is that as long as someone is hosting a precompiled binary for you, it's easy to get it. I just repro'd and yeah, `mise use php` fails for me on my machine because I don't have any dev headers. But looks like there's an easy workaround using the `ubi` downloader:
https://github.com/jdx/mise/discussions/4720#discussioncomme...
or see the first comment on this thread to see a way to explicitly specify where to find the binaries for each platform:
https://github.com/jdx/mise/discussions/4720#discussioncomme...
Having these kind of "eject" options is one of the reasons I really appreciate Mise. Not sure this would work for you but I'd rather be able to do this than have to manage/support everyone on my dev team installing and maintaining Nix.
- Agreed. Recently started a new gig and set up Mise (previously had used nix for this) in our primary repos so that we can all share dependencies, scripts, etc. The new monorepo mode is great. Basically no one has complained and it's made everyone's lives a lot easier. Can't imagine working any other way — having the same tools everywhere is really great.
I'll also say I have absolutely 0 regrets about moving from Nix to Mise. All the common tools we want are available, it's especially easy to install tools from pip or npm and have the environments automanaged. The docs are infinity times better. And the speed of install and shell sourcing is, you guessed it, much better. Initial setup and install is also fantastically easier. I understand the ideology behind Nix, and if I were working on projects where some of our tools weren't pre-packageable or had weird conflicting runtime lib problems I'd get it, but basically everything these days has prebuilt static binaries available.
- same here, hope they fix this soon
- Born ready
- I just ordered two cans of the cougar gold, one of the viking, and one of the mild cheddar. If it's not good I will blame you.
The archaic checkout system and the fact that this is a Washington State school agricultural product make me think that this will be the best cheese I've ever eaten in my life. Quite fond of their apples!
- Wow that is pretty bad. The comments in particular don't really make sense and are also dripping with AI mannerisms. Gross.
- I respect that, makes sense.
- I didn't complain, I'm legitimately asking. I've never seen so many ads in a personal tech blog before, it's an extremely confusing choice to me.
- Why do you have so many ads in this blog post?
- Would be nice to see an example of one of these cue sheets, I'm curious about the layout.
https://github.com/peterldowns/pgmigrate