F21A6194C9DB9899CD09E24E434B2C14B8C33422
[ my public key: https://keybase.io/n8henrie; my proof: https://keybase.io/n8henrie/sigs/WoQvsZKguJVoMfO7Fxk2mnWhN1Xh0cLZuDGQnxpwhWY ]
- n8henrie parentYes, I have several esphome devices. Very easy to use. Unfortunately the project is not written in a language that I know, and I strongly prefer projects in languages that are familiar to me.
- I never learned any C based languages, so it's been a challenge, but I've enjoyed learning the basics of bare-metal no_std rust on the esp32c3, with esp-rs and its support for embassy to help me get started!
My learning project -- using mqtt for HomeAssistant integration: <https://github.com/n8henrie/esp32c3-rust-mqtt>
- Tried to migrate to Hugo from Jekyll multiple times and have bounced off every time. Don't really know Go very well, but better than Ruby, and used this as justification -- since dealing with Jekyll updates was sometimes a headache (I use GitHub Pages for free hosting and let them build things for me when I push updates).
Instead I eventually just created an environment in nix that had compatible dependency versions to what GitHub uses and have been pleased since.
- After a decade of homebrew, a few years ago I got tired of their very grumpy maintainers and switched to nix-darwin + home-manager. I've been overall fairly happy, and for tinkerers would recommend giving it a shot. Admittedly I bounced off my first try a year before that.
A few of my favorite parts, which I see less represented in this thread so far:
- I simultaneously jumped into nixos on several Linux machines (starting with a few Pis for experimentation), and maintaining all of my systems with a single flake and mostly shared code is a dream come true. - no more convoluted dotfile syncing, most of my scripts and aliases and bash config and binaries all sync together - cross-building linux from Darwin -- including integration tests in a vm -- works surprisingly well, this is mostly just nix but nix-darwin has helpers that make this easier - writing system services (launchd) on my Mac then converting them to a headless Linux machine (systemd) is generally very straightforward - prefixing my path with GNU coreutils works well and saves me from many e.g. `sed` quirks, I get expected behavior across OSes - this was always a sore spot in homebrew, either dealing with the `g` prefix on everything (eg `gsed`) or dealing with intermittent breakages when stuff depends on the BSD behavior - I was also able to put nix-darwin on my wife's MacBook and greatly simplify admin / maintenance tasks I do for her - finally, the nix crew is just thirsty for help and contributions, particularly the darwin crowd; I feel like my (minor, occasional) contributions are celebrated, differences of opinion are met with an open mind, it is in general a far departure from the relative hostility of homebrew - on the down side, I have spent far more of my limited time helping contribute to nixpkgs / nix-darwin / home-manager
- Love that you had a good experience. I perform these procedures semi-regularly, and in some cases they can be painful (even with lidocaine). Most people tolerate them very well though, I usually compare it to the pain of an IV stick, which most people have already tolerated, but which can also cause some people a surprising amount of distress.
- For the last several years I've very happily used it over SMB to ZFS (with autosnaps) for this very reason, and wrote an AppleScript to automatically "verify" it every week or so.
Once or twice a year it gives a verify error (i imagine this is because a plug gets pulled halfway through a backup on one side or the other), and I just have to go find the last verified date, zfs rollback, and then re-verify. Afterwards it picks up where I left off, and the historical backups are preserved.
Wish it didn't require this extra effort in the first place, but much better than having to nuke and pave every time.
Even better, it's working great over Tailscale so I can even use it remotely. Only big hiccup I ran into was figuring out some ZFS setting about quota vs refquota (something like that) to have the Time Machine's (artificial) space limit match the ZFS quota so that Time Machine would prune the oldest backups appropriately (otherwise the ZFS snapshots took up an unpredictable amount of space and Time Machine would unexpectedly get out of space errors before hitting its space limit).
- I do a ton of work on low-power devices over SSH. Helix launches almost instantly; neovim with a similar level of functionality (via plugins) has considerably more startup lag and considerably more maintenance cost (config / plugin updates). I also know enough rust to try to help fix bugs but don't know any C family languages; I have a strong preference to use open-source projects written in languages I know.
EDIT: for context I'm a hobbyist who use n/vim for 12 years or so before switching to helix for the last couple of years. There are several things about nvim behavior that I still miss quite a bit and still feel more natural, but the instant startup of helix vs a second or two for nvim configured to a similar level of functional makes it totally worthwhile for me.
- My most recent septic patient had literally zero SIRS criteria, and I strongly did not suspect a bacterial source of infection. Isolated hypotension, nothing else. Said she felt great and asked to go home To date she's grown out GPCs on 8/10 blood cultures. Sepsis actually is hard. Also, it sounds like a bacterial source was not suspected in this case (and was validated by the cultures being negative and the autopsy), so AFAICT this was not sepsis.
- As an ER doc I look at a lot of my own studies, because I'm often using my interpretation to guide real-time management (making decisions that can't wait for a radiologist). I've gotten much better over time, and I would speculate that I'm one of the better doctors in my small hospital at reading my own X-rays, CTs, and ultrasounds.
I am nowhere near as good as our worst radiologist (who is, frankly... not great). It's not even close.
- Can you clarify -- if you're comfortable sharing additional details -- did you have an "occlusion MI" heart attack, involving balloons / stents in the cath lab?
Most people assume that "heart attack" is a distinct clinical entity, but the majority (~80%) of elevated troponin levels are not exactly what comes to mind when people say "heart attack," but will often be described to patients as a heart attack (sometimes out of ignorance and others out of convenience, as the actual explanation for what is going on takes a lot more time and effort).
- Nix is the escape hatch!
More packages than any other package manager you're likely to encounter.
If something isn't packaged for nix, it's often simple to package yourself. Even when this isn't simple, it's often simple to use nix to bring the build dependencies into your environment and then follow the usual (non-nix) build instructions.
I'm a lowly self-taught hobbyist who works in an entirely unrelated industry. If I can do it, you can.
- Learning to do something like this (reverse engineer electronics and flash them with custom firmware) from scratch is one of my life dreams!
Having read https://github.com/openmiko/openmiko/blob/master/doc/develop... -- is there anywhere that you document how you learned to do this / how you got started with this project?
I would love to find a "zero to hello world, from scratch" type tutorial for putting custom firmware on a camera not supported by one of the existing projects (or a similar writeup detailing how one of these projects got started in the first place).
- What? 25%? Isn't rabies in dogs lethal in fairly short order (like in humans)?
I'm pretty sure the rural county in which I work hasn't seen rabies in a dog since like 1986.
I work in an emergency room (frequently caring for dog bites) in an area with numerous packs of strays. Dog rabies is always a concern, but I've never seen a confirmed case.
- Can you elaborate on how things are counted?
Is it "counted" if FSD was engaged within a certain time frame prior to a crash? If so, do you know what time frame?
Or only if it was disabled automatically due to detecting a potential crash?
The latter would still be problematic, as a human driver noticing a problem just prior to the FSD disabling itself would potentially be missed (right?).
Do you know who does the counting and who makes the rules in this regard?
Asking as you seem to have more knowledge here than me.
- I love espanso! The cross-platform support is huge (I use it on macOS, windows, and X11 and Wayland-based Linux systems).
Moreover, the original creator (Federico) and the current head maintainer to whom he has handed most of the day-to-day (AucaCoyan) are two of the kindest people I have ever come across in open source. All issues and contributors are treated with respect, it really is refreshing to feel so welcome when trying to contribute.
- I don't think "easier" and "cheaper" are valid barriers to research regarding the most prevalent maladies affecting most people of the species. If there is a low morbidity gold standard for in-vivo diagnosis, it seems like a valid inclusion criteria. If there is no such gold standard available, it's kind of hard to validate a claim of someone having deep expertise.
The endpoints for such research don't have to be problematic; regarding musculoskeletal complaints it's fairly straightforward to measure self-reported pain, self-reported level of function, or more objective measures like working days lost, strength, stamina, range of motion. The more difficult issue is determining an appropriate control group / placebo intervention.
(Also, I'll point out that my initial comment also included nutrition, dentistry, and several other fields under the same umbrella of "not enough good research" -- or to further specify, my complaint is that the burden of disease is disproportionate to the availability of rigorous literature.)
> Some specialist physicians have a deep knowledge of exercise for injury prevention and rehab.
By what measure? As in "they have a lot of clinical experience" -- (the "plural of anecdote")? Or as in they have read a lot of books on the subject? In which case, you seem to be agreeing that the evidence base is weak, so I'm not sure how authoritative this body of literature could be.
> As a patient it can be tough to discriminate the good ones from the quacks.
I imagine they would be virtually indistinguishable as a patient. Based on the context of this conversation, how would you recommend that I, as a physician, tell them apart? (It's hard enough to do with other physicians.)
- Do you therefore agree that most physicians do not "deep fund of literature-backed knowledge to draw from regarding exercise"?
> Because there is so much variability in individual injuries and physiology it's extremely difficult to do rigorous studies comparing different treatments.
This is generally true of research in all areas of medicine; I don't see it as a fundamental reason why we wouldn't hope for equally powered and rigorous studies focusing on the issues that affect most of the population, even if there are not pharmaceutical or device companies that will profit from the recommended interventions.
I'm only a decade in, but my clinical experiences in my area of expertise vary widely from those of my colleagues, which vary from those of other colleagues, in spite of years of shared experience in a fairly homogenous demographic. Expert opinion is not a level of evidence that carries much weight in my mind.
It may be the best we have in many cases, I just wish we had something better.