This is really exciting! Discussions of our resource impact have come up a lot in my org's informal spaces, it's really exciting to see someone making a concerted effort to raise visibility into how much we spend in money or energy in what seem like benign actions.
I really like the emphasis you place that reducing environmental impact is reducing cost as well. Tying civic mindedness to pragmatism is essential in dollar-hungry spaces.
I appreciate the love. Yea, that was the cool thing during the research - if we reduce from a large to a medium, it both saves money and reduces carbon. Win - Win! Company can save money at the same time as reducing the environmental impact.
> Now the ones to avoid move around and it's all too likely that a newcomer is such a person.
This seems a wild generalization to make, though I guess "be suspicious of newcomers" is a little biologically hardwired. What's your epistemology for believing "newcomers" are "the ones to avoid"?
It's not just juniors. One of my partners carries a PhD in epidemiology and bimolecular science; they've been job searching for eight months with no bites, just silence. A friend of mine is a chemical engineering PhD, she's been searching for a year and just had her first interview.
I have eight years of software engineering experience but am only one rung up from the bottom of our SWE ladder, and we don't even hire the bottom rung anymore at my org. Seems like there's crushing pressure from above to limit hiring at every stage.
> the notion that it lacks nuance to describe the intricacies of text rendering
I took this to mean that any non-domain-specific language may be bad at describing that domain, e.g. why physicists, mathematicians, chemists, etc. have a common symbology for the discipline, or why programming languages exist. i.e., not so much that English is uniquely bad among written human language for conveying these topics, but just that any non-specialized language may be.
Though, I think the author did a fair job, but I lack the domain experience to guess at where the misconceptions might lie.
They linked a whole article detailing the complexities of specifically NAT traversal.
I should think it obvious that by removing an entire leaky layer of abstraction the process would be much simpler. Yes, you still need a coordination server, but instead of having to deduce the incoming/outgoing port mappings you can just share the "external IP" of each client--which in the IPV6 case isn't "external," it's just "the IP".
>Also NAT is a pretty simple abstraction, it's literally a single table.
...And now, let's try punching a hole through this "simple" table. Oops, someone is using a port-restricted or symmetric NAT and hole punching has gotten just a tad more complicated.
Running a firewall with upnp enabled has always amused me. Might as well just turn the firewall off if you let any machine shoot any hole it wants in it.
Anyone know if it's possible to bandwidth-limit the sync operations? I'd love to set up garage instances across my families' houses to act as a distributed backup, but I don't want to hose their (or my) down/uplink during awake hours. Having redundant selfhosted S3like storage would solve many problems for me, but I really need that capability.
I really like the emphasis you place that reducing environmental impact is reducing cost as well. Tying civic mindedness to pragmatism is essential in dollar-hungry spaces.
reply