Super annoying as I use this for my job (devrel). Maybe we can complain loudly enough about it? You know they are tracking the data, so I wonder what the big gain is in retiring the public view.
Haha, for what it's worth, I'm the lead for their marketing, and also an eng who took the job because I loved using Render and wanted a change from working in DevOps.
You don't have to believe me...would expect nothing less : D the product and the way we ship what our users want speaks for itself.
I'm about to move our tiny startup off AWS, onto NextPAASPlatform and had both fly and render shortlisted. The latter just bumped a few notches higher.
FWIW: I'm moving off AWS because it is expensive in many ways: it's costing me dear time which I should spend on my product. And it's costing serious baseline costs: Just a CI pipeline, building a static site, a react app, and deploying a Ruby (not rails) backend to Beanstalk Staging and Production costs over $100/month. Before any traffic and scaling. And building and maintaining it costs me upwards of 90 hours now. I consider this wasted investments.
+1 to keeping PRs small. This makes it much more logical to me. But I have worked at organizations where this is frowned upon...teams liked the PRs to be one logical unit/fix/improvement and component parts became frustrating or got merged at different times, creating the need for rework.
From reading a lot of feedback on this post one thing that stands out is, the best way to use git just depends on the context. But it doesn't hurt to have commands like this in your toolbox and know how to use the tool well. Plus we all have our private, icky antipatterns that we know we should improve, right?
> An addiction has for sure its chemical reasons, but limiting to only that when dealing with it, it's reductive
Right, the point I got from this, particularly from all the examples pulled from pop science, is that folks are focusing on a reduced/mischaracterized biological mechanism instead of on the associated social behaviors. The social behaviors are the things we can (theoretically at least) actually change. Perhaps the author means to express that we should focus on whatever human behavior we think it problematic instead of "blaming" a component of the mechanism.
I think you two agree (as do I). So much of this thread is focused on stuff like interest, but spending less than you earn and knowing how to calculate risk over time are massively more general and useful skills to learn.
Unclear whether we're in violent agreement. Parenting is all about evoking interests whilst suppressing urges. Since money is a means of both its importance comes out in the wash, so to speak.
I remember discovering Heroku while I was in grad school in 2014. I was learning how to use AWS...which in a way was a lot simpler back then. But I was working on different kinds of workloads and more focused on learning Hadoop so it didn't seem that useful to me and I kind of, disdained things that were "too simple." Seeing it again several years later it seemed a lot more useful to deploy webapps for dev projects but there didn't seem to be a way for us to leverage in in prod. Needed much more control and capability to run complex apps. Like, I was setting up ELK stack and I couldn't see how to integrate so I just...stopped thinking about Heroku, lol.
I don't know how I feel about the whole, locality pay thing. I still feel it is not ethical to pay developers in Eastern Europe what we typically pay them. However, I myself strive to achieve a Bay Area salary (and expect that when I'm working at a Bay Area company) despite living in a bit of a less expensive part of the Pacific coast. I don't see easy solutions to this problem when I look at it from both hiring and hiree perspectives. Capitalism...........
