> These tests blew me away. At the very least, I expected that presoaking the beans and pitching the water would reduce fartiness. After all, the sugars are water soluble, so they should leach into the soaking water and get discarded. As it turns out, not so much. I still don’t understand this result.
I don’t buy it. He’s says it doesn’t work but can’t explain why it didn’t work. Could be his method was faulty, the type of bean, the age of the bean, etc.
I rather take the experience of an entire country.
Not to dismiss the experience of Brazil, but Korea believed you would die if you had an electric fan on with no windows open. Safe to say entire countries are not infallible either.
Brazilian here. It's not a superstition, I can see my wife's belly literally inflate if the process is not done correctly. I cook beans at least once a week, I've made mistakes and there's no way to hide it. We don't get them cooked from delivery as we don't know how they were prepared, lesson also learned the hard way.
That said, the process is soaking the beans in water for, at least, 10 hours. You have to change the water four or five times during this period and toss the water at the end.
On the other hand, adding bay leaves are totally a superstition. Saw my mother-in-law trying to hide she forgot to soak the beans overnight by adding bay leaves and my wife had a bad aftermath.
Yeah, boiling water with lemon helps, but without it my wife has a lot more gases. One article that they tested, can't explain it properly and we have seen over and over working, I very much don't believe they did it right
There are multiple watches, cameras, etc., with a lot of physical buttons even, all with replaceable batteries and weather-resistant (or even better, water proof). This is a bad excuse.
One is supposed to grow out of caring about the result. A master at their craft creates masterpieces because day in, day out they sit at their desk and create. When they're sad, they sit down and create. If you love the process, you keep at doing something; doing something repeatedly is how you become a master.
If you want to go spiritual, there's karma yoga from the Bhagavad Gita: "You have a right to perform your prescribed duties, but you are not entitled to the fruits of your actions. Never consider yourself to be the cause of the results of your activities, nor be attached to inaction."
Did Leonardo work for fame and monies, or simply because he found massive enjoyment in it? What about Hemingway, or Einstein?
This might all sound like new age bullshit, but it's taken me literally 15 years of my life to understand this and grow out of chronic procrastination and dissatisfaction.
most of today's problem's in this field is because upper management got swindled into thinking that the process doesn't matter, as long as something comes out the other end. Doesn't need to work properly.
But this shitty state of software nowadays is mostly due to only caring about the result and not the process.
To be clear: this existed even before AI, and also led to the proliferation of electron and its ilk.
Not really. The opposite is far, far more desirable in my eyes.
Example:
* Do I care if an LLM was used to determine the volume of my doorbell? Not particularly.
* Do I care if an LLM was used to generate code to unlock my front door remotely? Absolutely!
I need a warning label cautioning me of the risks associated with generative materials. I don't care in the slightest when it isn't present, because the inherent risks associated are inherently lesser.
My mistrust of digital locks isn’t based on negligence from the reputable(?) manufacturers (Abloy? Reputation is in the eye of the beholder).
It’s who else has access: property and facility management, maintenance, etc. In the age of physical keys, I trusted these SMBs to be relatively capable, let’s say 7/10, in protecting those keys from most local would-be criminals and opportunists. That goes down to 2/10 for protecting digital assets, like remote unlock capabilities, from cybercrime.
As soon as there is a viable market connecting cybercriminals with local criminals, whether it’s vertically integrated organised crime or something like carding forums, physical access exploitation is bound to become a problem.
These might be theoretical issues that people without experience worry about, but let me share what I've witnessed in practice working almost a decade with Clojure at Nu.
We mostly hired people with no previous Clojure experience. Majority of hires could pick up and get productive quickly. People fresh out of college picked it up faster. I even had a case of employee transitioning careers to S.E., with no previous programming experience, and the language was a non issue.
I can't remember an instance where the language was a barrier to ship something. Due to reduced syntax surface and lack of exotic features, the very large codebase followed the same basic idioms. It was often easy to dive into any part of the codebase and contribute. Due to the focus on data structures and REPL, understanding the codebase was simply a process of running parts of a program, inspecting its state, making a change, and repeat. Following this process naturally lead to having a good test suite, and we would rely on that.
Running on the JVM is the opposite of a problem. Being able to leverage the extensive JVM ecosystem is an enormous advantage for any real business, and the runtime performance itself is top tier and always improving.
The only hurdle I could say I observed in practice was not having a lot of compile time guarantees, but since it was a large codebase anyway, static guarantees would only matter in a local context, and we had our own solution to check types against service boundaries, so in the end it would've been a small gain regardless.
I understand the need of terminal emulator for certain interactive programs, but inside Emacs I just use 'shell-command and output buffers. What's the benefit of having a terminal emulator inside the Emacs process? If the program is interactive (TUI) it won't integrate well with Emacs buffers/keybindings anyway right?
I haven't tried this project, but did switch to vterm from shell-mode a while back because it managed to fix most of the paper cuts when using shell-mode. I also used to create a lot of custom compilation buffers for things b/c it would create links to files that were helpful, but that has been less helpful to me. At the end of the day, there were papercuts that made shell-mode and compilation buffers less ideal and most folks were focusing on traditional terminal support.
My main use case is emacsclient and vterm as a terminal multiplexer, in place of something like tmux or screen.
But even locally I use vterm. A terminal is just text, why wouldn't I manipulate it with emacs? At any time you can switch to `copy-mode` and it behaves like a read-only text buffer that you can manipulate as you please.
The Gulf countries are dumping their gold reserves and buying dollars, that put a momentary halt on what was a steady declining trajectory for the USD. But since this blip isn't caused by structural reasons (nothing changed in the US economy), it will only last as long as these countries have gold to sell.
I don’t buy it. He’s says it doesn’t work but can’t explain why it didn’t work. Could be his method was faulty, the type of bean, the age of the bean, etc.
I rather take the experience of an entire country.
reply