antoineleclair

It's more than a 404... going to the root of the domain welcomes you to the screen to install Wordpress.

Reloading the page a few times shows different sets of keys and also a 404, randomly.

It's breaking "login with Apple".

Hi! HN is such a small world.

I stopped reading at "load-bearing" and em dash.

Great to see Disco is listed there. Thanks!

Kudos for the new landing page.

I see in their FAQ:

> Will PeppyOS be open source?

> Yes! PeppyOS will be fully open source under a BSL license before the end of this year. Once the software is mature, everyone will be able to contribute and participate in its development.

Librato was a simple Heroku add-on to view charts of metrics provided in the logs of Heroku.

It's not super simple, but here's how we did it for a long time:

All of your income that's not invested for retirement goes to a joint account, every 1st of the month. From that joint account, you then move the money to many different accounts and/or prepaid credit cards: - Day to day expenses, like groceries. - "Irregularities": municipal taxes, school taxes, things that don't happen every month, like car inspection, veterinary, vacation expenses. You add everything in a spreadsheet that you keep, and divide by 12. Add some padding. - Home improvements, aka "IKEA" account. Fixed amount every month. If it's a good that you buy to add you our home (coffee machine, chair, curtain, etc.), that's the account. If it's a consumable (gas for the car), use "day to day expenses". - Individual accounts: each one of you have an account that you decide what to do with. Buying clothes, hobby, etc. aka "I'm an adult, I do what I want". - Kids: There's always something to buy. Clothes, etc. - Automatic payments are taken from the main joint account, but you could also have another account if it makes it easier.

This method can get confusing and you may need to move money from one account to another one when the wrong card was used. But the main advantage is that it automatically budgets for you. You see the amount remaining for the month for everything. Otherwise, you may think that you still have plenty of money to spend on the grocery, so you buy a nice coffee machine, and then the mortgage and car payments happen and you're left with nothing for the rest of the month to do the grocery.

The main goals we had when using this method were to never use a credit card (and lose track of how much money we have), and also accommodate for the discrepancy in our revenues at the time.

Transactions can fail because they conflict with other transactions happening at the same time. It's not an application bug. It's real life transactions happening on a production system. It's normal for that to happen all the time. The app can retry, etc., but it should be expected to happen. Having to deal with distributed transactions is not something easy. Especially when they're part of many different systems. For example, you'd have to wait until the transaction commits successfully before setting the value in the cache, which makes it hard to read. Also, life in general happens. Compute a value, cache it, save things to the database, make API calls, and then a network error happens cancelling everything that you've just done. Having code that handles this kind of possibility is relatively hard to write/read.