anon3949494

I agree with the gist what you're saying, like ditching the ego, the status chasing, etc. But dragging stuff like staying connected, being knowledgable, enjoying good food, and travel is where this goes a bit too far. A rock has zero dependencies, but nobody wants to be a rock.

I had a similar experience. It's a strange and surreal form of gaslighting when family members make you angry and then subsequently make you to feel ashamed for becoming angry.

Anger, just like any other human emotion is neither good nor bad. Prescribing a human emotion as good and another human emotion as bad takes a certain degree of self righteousness. After some growing up, I've since learned to try and let my emotions guide me rather than run away from them and that's made all of the difference.

I can definitely see how this is appealing for small technically oriented teams that want to move fast. It is likely however that your team will reach an inflection point and at some point having a *good* PM would be a net positive to the company.

Just signed up but didn't receive a confirmation email. Are you currently accepting new sign-ups for the managed service?

Education rather than policy might be the key ingredient

We should seek sustainable human population on this planet, rather than pursuing the conventional approach of relentless growth.

> It typically manifests itself as not being able to read your own writes

Multi-region databases with read replicas face the same issue

It's also trivial to serve read requests from a caching layer or via a CDN. At any sufficient scale, you're probably going to need a CDN anyway, whether your database is replicated or not. You don't want every read to hit your database.

Yep, for anyone confused on how this works:

You'd still be sending writes to a single region (leader). If the leader is located across the world from the request's origin, there will be a significant latency. Not to mention you need to wait for that write to replicate across the world before it becomes generally available.

After all the chatter this week, I've come to the conclusion that Heroku froze at the perfect time for my 4 person company. All of these so called "features" are exactly what we don't want or need.

1. Multi-region deployment only work if your database is globally distributed too. However, making your database globally distributed creates a set of new problems, most of which take time away from your core business.

2. File persistence is fine but not typically necessary. S3 works just fine.

It's easy to forget that most companies are a handful of people or just solo devs. At the same time, most money comes from the enterprise, so products that reach sufficient traction tend to shift their focus to serving the needs of these larger clients.

I'm really glad Heroku froze when it did. Markets always demand growth at all costs, and I find it incredibly refreshing that Heroku ended up staying in its lane. IMO it was and remains the best PaaS for indie devs and small teams.

We're on the Team plan

We're a small org with a github connected to heroku. All of our repos were cloned between April 8 and April 15 with the majority of them having no activity for several years. The audit logs don't show this, you can only see this information in the traffic graphs (/graphs/traffic). If you're seeing cloning of repos that you haven't touched in a while, you've likely been compromised.

We're a small org with a github connected to heroku. All of our repos were cloned between April 8 and April 15 with the majority of them having no activity for several years. The audit logs don't show this, you can only see this information in the traffic graphs (/graphs/traffic). If you're seeing cloning of repos that you haven't touched in a while, you've likely been compromised.