Having learned in the last year that I'm autistic, and having learned a lot just about what that means, I cannot help but wonder to what degree Reagan and Trump may be dyslexia and not even know it.
It's very easy to realize you're "different" from other people, but can't place your finger on it, yet manage to make up for the differences in odd and creative ways!
I'm not entirely sure if smugness is the entire reason for doing it -- I suspect that for many of us (particularly autistics like me) there's a certain amount "But someone's wrong on the internet!" syndrome going on.
Some of us just can't work up the energy to answer a question, but if we see something wrong, it doesn't sit well with us, and we have to correct it.
And yes, sometimes when I see a question I can answer, it gives me the energy to answer it ... but not always ...
When working on a test that has several asserts, I have adopted the process of adding one final assert, "assert 'TEST DEBUGGED' is False", so that even when I succeed, the test fails -- and I could review to consider if any other tests should be added or adjusted.
Once I'm satisfied with the test, I remove the line.
I liked the part where they were looking for someone to manufacture the handles, and the Japanese machinist said "If he could make it, I can make it!".
Indeed, having gone down the rabbit hole of machining (both to see if it would be a viable hobby and if it could even be a career), this was the attitude of the shop teacher: "if you can think it, you can probably make it". I am far more surprised that neither the American nor the Taiwanese manufacturers said this. Then again, perhaps it was because management didn't talk to the guys who made things!
(Now that I think of it, had they done that, perhaps they would have gotten the answer "We can do it, but the fins will wear down the tool too fast, at least until we can figure out a better material for the tools!" instead of "Nope, we can't do that!")
I have concluded, as a general rule of thumb, that if something costs more to recycle than to produce naturally, it is probably more harmful to the environment to recycle it than to create it fresh and dispose of it properly.
There are certain exceptions to this -- nickel cadmium batteries come to mind -- but for things like this, the question isn't "is it more economic to produce it new than to recycle it?" so much as it's "is it more economic to recycle it than to dispose of it properly?"
I think 'dispose of it properly' is doing a lot work there. I understand that for something like plastic, properly disposing it would be to chemically render it down to it's constituents rather than just landfilling it. If the thought was to burn it, well then how are you properly disposing the released greenhouse gases?
On the other hand if a pound of plastic being burned offsets a pound of coal then that is probably better for the environment. We are nowhere near not burning anything so I'm largely OK with incinerators.
That might be true. I guess the point I was thinking of was more related to the cost of producing new vs recycling or disposing of. I think that in a lot of cases,the cost of producing new does not take into account the lifecycle of the product - it does not factor in the cost to retrieve it to be burnt, it does not factor in the cost to develop and implement technology like carbon capture. It seems that the industry that creates plastic does not pay for its proper disposal, which is why it is so cheap to make new plastic.
That probably means that recycling is not worth it, so the only responsible way is to reduce its usage as much as possible (reusing or replacing with better solutions)
It is a horrible waste to produce any strawberries from an environmental perspective compared to the least sensitive feed crops so feeding them to animals is more of a better than nothing while getting someone out of the market for the grades of strawberries that drive production is not. But any mediocre quality strawberry jam probably does that.
Despite the quotes, the person you’re replying to didn’t use the word “waste” nor have they claimed using that fruit to feed animals would be bad. In short, they didn’t make the argument you’re against.
However, in the interest of good faith discussion, I’ll offer a rebuttal to the argument you are making. The logic applies when (and this is very important) that food goes to farm animals which will be slaughtered of humans to eat.
“Waste” isn’t really the right word, more like “inefficient”, in the sense that the amount of food which takes for an animal to mature is orders of magnitude greater than what you take from it. In other words, you could feed significantly more people if they ate what you’re feeding the animal.
When you couple that with the environmental impact of raising animals as food, including deforestation and land use, which in turn affects us as well, it becomes a major issue.
Potato potáto, that’s not what matters. The whole point of the post was to engage in good faith and see past the exact wording to focus on the argument. Obsessing about the definition is counter productive and an exercise in bad faith and derailing the conversation. That is a waste.
As someone who doesn't like to see history lost via "rebase" and "squashing" branches, I have had to think through some of these things, since my personal preferences are often trampled on by company policy.
I have only been in one place where "rebase" is used regularly, and now that I'm a little more familiar with it, I don't mind using it to bring in changes from a parent branch into a working branch, if the working branch hasn't been pushed to origin. It still weirds me out somewhat, and I don't see why a simple merge can't just be the preferred way.-
I have, however, seen "squashing" regularly (and my current position uses it as well as rebasing) -- and I don't particularly like it, because sometimes I put in notes and trials that get "lost" as the task progresses, but nonetheless might be helpful for future work. While it's often standard to delete "squashed" branches, I cannot help but think that, for history-minded folks like me, a good compromise would be to "squash and keep" -- so that the individual commits don't pollute the parent branch, while the details are kept around for anyone needing to review them.
Having said that, I've never been in a position where I felt like I need to "forcibly" push for my preferences. I just figure I might as well just "go with the flow", even if a tiny bit of me dies every time I squash or rebase something, or delete a branch upon merging!
> I cannot help but think that, for history-minded folks like me, a good compromise would be to "squash and keep" -- so that the individual commits don't pollute the parent branch, while the details are kept around for anyone needing to review them.
But not linked together and those "closed" branches are mixed in with the current ones.
Instead, try out "git merge --no-ff" to merge back into master (forcing a merge commit to exist even if a fast-forward was possible) and "git log --first-parent" to only look at those merge commits. Kinda squash-like, but with all the commits still there.
I use git-format-patch to create a list of diffs for the individual commits before the branch gets squashed, and tuck them away in a private directory. Several times have I gone back to peek at those lists to understand my own thoughts later.
XKCD has a fun comic about a guy who recalculates the world records of pole vaulters based on the gravity of the locations of various events. Earth's surface gravity is by no means constant -- it varies, presumably due to the density and altitude of any particular location.
Indeed, "sea level" is defined as the level that the sea would be at, if the area of question didn't have the land mass, but still had the same gravity. Of the various possibilities, this particular definition is useful, in that it you can expect the air pressure at a particular altitude to be the same, regardless of where you are, after factoring in things like temperature and humidity -- which is kindof important if you're a pilot of some sort!
With the lack of precision for clocks the way they are, and worries about variance in travel time due to traffic, distractions, potty emergencies, and so forth, the more natural way to handle precision is to give yourself a 5-to-15-minute-to-an-hour buffer to ensure that you're in your seat when the clock ticks from 11:59 to 12:00.
And yes, 5-to-15-to-an-hour is something that varies, depending on the length of your trip. 5 is appropriate when you're in your office and you need to get to the conference room, 15 if you're driving from your nearby home, an hour if you're flying in, or if you have to drive 200 miles or so -- particularly if it's a trip you don't regularly take!
For meetings, I actually give myself 16 "precise" minutes -- one minute less than 15, with 4-minute-30-second snoozes, so I can have both adequate warning, and regular pokes, to make sure I can do something on time.
There have been times when my wife and I resorted to including send times, because the latency between our phones was ridiculously high. I really wish SMS and email would include both sent and received times, so that latency issues can be accounted for.
It's very easy to realize you're "different" from other people, but can't place your finger on it, yet manage to make up for the differences in odd and creative ways!