I actually haven't been able to get the ED notes from that first ER visit yet. They are in a different system than Brigham and Women's, which made it super easy to read notes in their app.
15,550 karma · joined August 18, 2012
https://burntsushi.net
[ my public key: https://keybase.io/burntsushi; my proof: https://keybase.io/burntsushi/sigs/F85E7EUozUtRvdv1a8NpNW8HBSSJ4cK9bhTgqDAslZA ]
I actually haven't been able to get the ED notes from that first ER visit yet. They are in a different system than Brigham and Women's, which made it super easy to read notes in their app.
I was put on a low dose of an anti-psychotic. I am in fact still on it. We just haven't gotten to tapering off of it yet. (Other medications have taken higher priority.) Tapering off all of my medications, which is the goal, will take quite some time.
In the moment, I very much welcomed the anti-psychotic. I would do anything to fix what was wrong with me. The problem is that the front-line treatment for anti-NMDA receptor encephalitis (IVIG and steroids) takes a minute to kick in. Moreover, you don't have the diagnosis until later. There was a point in time, before the positive CSF antibody test but after the abnormal MRIs, where multiple sclerosis was a possible diagnosis.
In any case, once I got out of the psychiatric hospital and into Brigham and Women's, an MRI is indeed what I had right away. And that's when the brain lesion was found. But! Not all cases of anti-NMDA receptor encephalitis have an abnormal MRI. Susannah Cahalan, for example, had two normal MRIs. Brain inflammation was only detected indirectly at first because of the "clock test"[1]. And they later did a biopsy on her brain to confirm.
In retrospect, yes. I think I could have done a better job of advocating for myself on my first ER visit and demanded to see a neurologist. But I didn't know what I didn't know, unfortunately.
[1]: https://www.encephalitis.info/news/brain-on-fire-susannahs-r...
In my case, the misdiagnosis up front was entirely reasonable. (EDIT: Well, maybe not. See below.) The generalized anxiety disorder diagnosis from my PCP made a lot of sense given what was happening. I hadn't had delusions yet at that point. It was... a mixture of panic attacks, night sweats, jaw pain and a greatly increased level of anxiety compared to my baseline.
My PCP did run a bevy of tests (chest x-ray, and took tons of blood) to try and rule out anything biological.
Given what was known at the time, I think my PCP did the right thing. And when my symptoms really escalated (delusions, suicidal ideation, falling and hitting my head), my PCP suggested going to an ER. And that's what we did.
I think it was the ER that really dropped the ball. Given the sudden onset of everything, the fact that they didn't get me in front of a neurologist is, in retrospect, really quite baffling. That's when I went to a psychiatric hospital, where I spent 3 nights.
I only got out of that hospital due to total luck. My neighbor was old college buddies with a neurosurgeon. (We had no idea about it. It just came up randomly when my neighbor was dropping my son off at home for us.) That was the critical connection because he ended up talking to the neurology department at Brigham and Women's, then talked to the psychiatric hospital and was the one who facilitated my transfer.
My wife tried to do it on her own but they wouldn't allow it because I had been medically cleared. She had to give 3 days notice to pull me out. Or otherwise, by default, I would see a neurologist after 2 weeks. According to the psychiatric facility.
I really don't know if I would have made it that long. The encephalitis wouldn't have killed me in that span of time, but I was in an extremely dark place.
I'm also really lucky that this is an autoimmune disorder that has a pretty objective diagnostic criteria: a positive antibody test in your cerebral spinal fluid. You "just: need to have your spine tapped to get that though. Fun times.
(My handle comes from graffiti I found on the booth of a hot dog stand in Worcester MA called Coney Island[1]. I thought it was a cute oxymoron and adopted it on a silly whim. I only later learned that some sushi is indeed cooked.)
There were lots of reasons that went into me posting this.
First and foremost is that this is a disease of chaos that is prone to misdiagnosis. I want to shout this from the roof tops to spread awareness. I don't have a ton of reach, but I have some, and I want to use it to amplify things like this.
Second is that I'm somewhat naturally open about these sorts of things.
Third is I feel a responsibility to my projects and users.
Fourthly is that it's just practically useful to have a link to send to someone when I reference this time period in my life. :-)
> very new diagnosis
Yes! Discovered in 2007. Wild.
> so if you are reading this burntsushi, thanks for being open about something deeply personal, I hope I would have had the courage to do so myself.
<3 <3 <3
It's been a trip. The worst thing that has happened, but also the best. It has definitely given me a new perspective on life, that's for sure.
My favorite side effect is that I now love all foods. Prior to this, I was a rather picky eater. Now I love everything!
If AI becomes the interface, then we will a layer of abstraction above programming languages themselves. Which is kind of wild.
(I don't pretend this is a novel idea. I'm just not that plugged into AI discourse.)
Using +4 or +5 explicitly instead of a time zone when DST is relevant is bad juju. Then your arithmetic can become silently wrong in subtle ways when it cross a DST boundary.
> Why replace the already existing std::range in-place with the new version
We didn't. `std::range` is new. The existing range types have always been in `std::ops`. They have to stay there because we don't have a way of resolving paths in an edition dependent way.
See: https://rust-lang.github.io/rfcs/3550-new-range.html#new-pat...
> The other day there was some talking about Go's stdlib around here, and I truly believe they got it much better thought out.
I used Go for over a decade and loved every minute of it.
As someone with significant API design experience in both Go and Rust, Go has it way easier. I don't want to go into a big long diatribe about it, but the space in which Rust operates means that getting APIs correct in a way that lasts forever is harder. To a first approximation, this is a result of project goals (hand wavy: being able to write code while thinking about "what I want the CPU to do") and expressive power provided by the language.
Go added generics after I mostly stopped using it, but even with that, there are considerable differences in expressive power that translate directly into more complex APIs.
Plus, Rust started with Cargo. Go didn't get "proper" package management until much later. The promise (and one that it has fulfilled ten-fold) was precisely that Rust's standard library could be "small" and gaps could be filled by ecosystem crates that can use semver incompatible changes to evolve when necessary.
(My intent is for the above to be mostly descriptive. I'm not trying to cast shade on Go here. The Rust and Go projects have different goals that they optimize for. To be prescriptive: Go does an excellent job of optimizing for their goals IMO. And also, IMO, to be frank, I would consider this a feature of Go that it has over Rust. Having batteries in std is great. I'd love to have more. It's just fucking hard in the Rust world. That's not to minimize and say Go has it easy... But, well, okay. I'll stop hedging here. Lol.)
Fun fact: ripgrep started as something to dog-food the regex crate (with a focus on performance). I didn't originally build it to release to end users funnily enough. To be clear, I'm not implying bttf will follow the same path. I honestly probably agree with you at this point. I wouldn't have 1 year ago though.
And yeah perf probably doesn't matter much. But, like, running my approach on the Rust compile repo takes at least minute on my beefly (if a little dated) machine. But lukasgelbmann's approach only takes about 11 seconds. That's a big improvement.
Yeah though, perf here may not matter much. It's just an example use of bttf that is less than instant. (And it's not really bttf. It's my examples access pattern of git.)
I'll have to noodle on this one. `bttf tag exec` works with arbitrary commands that can print any kind of date. But your approach require a different access pattern. I can either specialize the use case in bttf (blech) or I can figure out how to generalize your approach.
I think the key issue here is probably that it isn't line oriented. bttf composes well, but only when you have a one-to-one relationship between date and data. (Or a many-to-one is also supported, but it's many dates to one datum, not one date to many datums.) So maybe that relational model is worth figuring out how to streamline. Then I think this use case would work better.
Also, thank you! This is exactly the kind of reply I was hoping for! :D
To be clear, I don't mean publishing a crate to read an environment variable. Of course. I mean a crate that converts a POSIX locale into a Unicode locale.
I guess there's probably a 20% solution that gets 80% of the way there. e.g.,
$ BTTF_LOCALE="$(echo $LANG | sed 's/_/-/' | sed 's/\..*//')" bttf
Thu, May 28, 2026, 11:46:21 AM EDT
If Biff just did that as a stop-gap until the full solution lands, I bet it would work in lots of cases.I still want one of those hover boards!
In any case, I've renamed the project to bttf: https://github.com/BurntSushi/bttf/pull/14
$ bttf time seq monthly -w 2-tue -u 1y | bttf time fmt -f '%c'
Tue, Jun 9, 2026, 11:15:11 AM EDT
Tue, Jul 14, 2026, 11:15:11 AM EDT
Tue, Aug 11, 2026, 11:15:11 AM EDT
Tue, Sep 8, 2026, 11:15:11 AM EDT
Tue, Oct 13, 2026, 11:15:11 AM EDT
Tue, Nov 10, 2026, 11:15:11 AM EST
Tue, Dec 8, 2026, 11:15:11 AM EST
Tue, Jan 12, 2027, 11:15:11 AM EST
Tue, Feb 9, 2027, 11:15:11 AM EST
Tue, Mar 9, 2027, 11:15:11 AM EST
Tue, Apr 13, 2027, 11:15:11 AM EDT
Tue, May 11, 2027, 11:15:11 AM EDT
More examples here: https://github.com/BurntSushi/biff/blob/master/GUIDE.md#date...Implementing the RFC 5545 recurrence rules was quite a lot of fun: https://github.com/BurntSushi/biff/blob/4c75d5cf6e09310e74ca...
I'm quite proud of it, because if you look at the implementation, it's almost entirely about dealing with the specification rules. All of the datetime bullshit (including handling time zones) is all deferred to Jiff.
Plus, the tests are nearly 4,000 lines. While the implementation is 2,000 lines.
The comparison with GNU date is also likely informative.