jschwartzi

This kind of thing is what eventually kills off Brewer's Yeast. The individual yeast cells keep making sugar into alcohol until the alcohol concentration is so great that they kill each other off.

I actually think there are tons and tons of "homeless" people who are completely invisible because they're otherwise normal people who just happen to be living in their car or a tent for an extended period. The people I've met who have been in that situation were not dealing with addiction or psychological problems. They were simply victims of circumstance. In at least one case I'm aware of the person was kicked out by her husband with no job and no address and was totally unable to access any social services. Her getting housing enabled her to get a job and access services she didn't have access to when she was homeless.

I think giving people housing is a huge part of getting them off the streets, and I think you underestimate the number of people who are homeless because you're not seeing the countless homeless people who are keeping their lives together in spite of not having a permanent address.

Simply giving someone a permanent address allows them to access tons of social services that are completely locked away when you're homeless. Food stamps, unemployment, disability, child care assistance, are some of the very important social programs which require a permanent, non-PO Box, non-General Delivery mailing address before you can access them.

Unless I'm writing a blog or something, in which case I'm not looking for customers and I really don't care if anyone reads it or not.

Yeah definitely. And also be sure to switch all your keys on your keyboard to a hardwood. I prefer mahogany for its bright clicks and depth of response versus the equivalent plastic keycaps.

I can type about 70-80 WPM on my qwerty in typing tests. The limiting factor in my work isn't typing speed, it's my ability to form thoughts and to express them to the computer. So switching to a faster keyboard does absolutely nothing for me.

Some of the lower-level questions map more to design review rather than code review. For example if you're asking "Do the domain models cleanly map the real world to reduce cognitive load?" after the code is already written, it's probably too late to make any changes. However you should have some kind of plan and communicate it to your teammates prior to embarking on the kind of code change that creates new "domain models." During their review of your plan they should be making sure the domain model makes sense.

The point of it isn't to know what everyone is doing, it's to know when someone is hung up on something that you can help them with.

Yeah my brother's wife will completely shut down and start screaming if a dog comes within 5 feet of her. Where she grew up in China dogs were wild animals that would viciously attack you if you got near them, so it's a pretty understandable reaction. So I'm not sure why you're getting downvoted here.

Also having personally seen how poorly trained most peoples' dogs are I would be very uncomfortable having a random stranger's dog near me. A lot of the dogs I encounter on the street are neurotic wrecks incapable of passing without barking, leash pulling, or lunging.

This is pretty much how systemd works. You can specify secrets that are retrieved from somewhere else and provided to the process in the environment it is started with. So you could do exactly this with the right unit configurations.

There's actually a long list of variables that are unset when invoking sudo to prevent these kinds of attacks. Systemd will also start programs with a very minimal environment that isn't inherited from any shells. You then have to specify environment variables explicitly as part of the unit file. You can also specify environment variables in environment files.

In the article it says that these doses were produced in a facility that wasn't approved by the FDA yet, so this has no impact on the availability of doses now. It might have an impact on the availability of doses in the future though.

True, but think of all the complications a regular person could perform that the watch can't.

I think you could probably pay someone $40,000 a year to follow you around and tell you what time it is whenever you ask.

I think that Hermes watch that the article thinks so highly of has an awful typeface. It's cool that they went to the trouble of designing something to work within their design language, but it's totally unreadable. It would have worked better to simply leave the hour marks totally unadorned.

Also yelling at someone who is the only person who can solve your problem is not a good negotiating strategy, especially when it reminds them of why they left.

Walking away from a toxic situation is not "psychopathic." It's common sense and if we all did it more then the psychopaths who expect us to stick around through it all would finally learn how to treat other people with respect. It's a job, not a marriage.

Or the pale imitation of recourse that is a boycott. Try boycotting the company that sells your water.

We had to write our own Scanner class in our Java classes because the version of Java we were using didn't have that functionality yet. It came out in the middle of the course.

Well, sure. if you have a pile of totally unrelated things that never need to change in lock-step, then you don't need a "monorepo." But on the other hand if you're building an entire software system such as a collection of API services, a database schema, embedded device firmware, and a website, and all of these things are interdependent and incompatible across versions then please for the love of god use a monorepo.

At my job our cloud team uses multiple separate repositories which makes sense, but it also moves the burden of versioning to run-time. This is because they have to interface with multiple different versions of the device firmware. So they deploy different run-time versions of the APIs to support legacy and current production firmware versions. But our firmware repository is a monorepo in that the sources and build system builds the artifacts for multiple devices from the same source tree.

So it's not so cut and dried as "never use a monorepo" or "always use a monorepo." It involves engineering tradeoffs and decisions that are made in a context, and you can't extract your advice from the context in which it exists. What works for our cloud team would be a terrible mess on the embedded side simply because of how the software is deployed and managed.

I use the alpine butterfly to make a trucker's hitch, and I'll often use a friction knot at the end when I've tensioned the line. With those few knots I can use a single 100ft rope in place of a bunch of ratcheting hitches for securing loads in the bed of my truck. And when I want to release the load I can just untie a couple of corners and the whole rope comes out.

We're using two different definitions of "hoarding" wealth here.

The people you're disagreeing with consider buying up real-estate and company stock to be "hoarding" wealth because those assets could otherwise be put to productive use by someone else. People could otherwise live in those houses and become home-owners. Or the companies in question could get re-structured into smaller more efficient organizations during bankruptcy. It's hard for me to see the value of a real-estate investor buying his millionth acre of land when in earlier times multiple families could live on that land and call it home.

In contrast, you're assuming that any money being loaned to anyone is put to "productive use." And the flip-side of that is that the loan will come due some day. So accumulated wealth is used to accumulate more wealth from people who don't have any to begin with. In other words, the hoard of money is being used to extract rent and to hoard even more money. It's hard for me to see the value of that kind of system. It seems to lead to a continual serfdom as most people become renters of everything in their life.

Yeah in the case of water on burning kitchen oil it just makes a big fuel-air bomb if the oil is atomized enough. Kinda like one of these:

https://www.youtube.com/watch?v=i20zvZ-3MMw

Note the initial dispersion of some atomized material followed by a triggered explosion some time later.

By arguing from the standpoint of raising or lowering prices you're being very reductive. Doctors form trade associations too, and yes the prices for a certified doctor are much higher, but the quality of care is also standardized and usually higher to match. OP wasn't making the point that industry associations don't raise prices. OP was pointing out that most industry associations are formed to try to make things better. And that might result in increased prices, but that's a side-effect and not the goal.

You're actually looking for a mol of electrons and a mol of protons.

I'm not really a physicist, but I can suggest better terms than "analog" vs "digital." The words you're actually looking for are "continuous" vs "quantized."

> Bottom line is: we need a system to teach people more things that will probably end up useful and less obscure crap, but it isn't just "teach people whatever their job is and whatever they need to know as an adult, and ignore the social sciences and history because those will never be useful".

I agree with you here, and mostly because we all exist and make decisions in a historical, experiential, and psychological context, and you have to have some knowledge of contexts that are different from yours if you are to have any hope of being an effective leader.

My wife's car just has "Parking Assistant" which beeps if you're within 2 feet of an obstacle in any quadrant of the vehicle. Basically it scares the shit out of us when we're trying to park. So I can understand the harrowingness of that system.

I think a better design than an audible alarm is to show the driver using quadrants or a diagram when an object is within the "close," "very close," or "near-collision" zone around a vehicle and beep once but only when the object passes into another zone to alert the driver to a change in state. The tones should change for each transition so you can learn the tone for "object moved from close to very close in right driver's-side zone" and distinguish that from "object moved from very close to close in right driver's-side zone."

Having to constantly pay attention to an alarm tone is extremely nerve-wracking. In medical devices this will often result in "alarm fatigue" where you spend so much time dealing with false alarms that you miss a real alarm.

I have actually had a recruiter negotiate a salary bump on my behalf though.

And that's probably how I got an interview with AWS once upon a time.

Post your resume on one of the really big job boards like Dice or Indeed and you'll see what we're talking about. Last time I did that I was getting 4 or 5 calls a day. Most of those recruiters were from the same three companies and you could safely rule them out because they would ask for your SSN. But anyone who calls you and tries to establish a personal relationship might be worth working with.