As someone with Crohn's disease (thankfully now in remission) I can fully relate. Nausea is the worst symptom because it is so debilitating. You don't want to do anything when you are nauseated and when it goes on for months that affects every part of your life.
That's so interesting. I have crohns' (definitely not remission but not flare either), and nausea has never been a thing for me. It's just pain and the usual incomplete digestion if i stray at all out of my heavily restricted diet. How did you get remission? I'm about to have to up my remicade dose
Mine is primarily in my large intestine, so it's like a weird combination of Crohn's and UC, which could be why it causes so much nausea. Remission for me was just sort of luck and time. I was first diagnosed at 28, was on a ton of steroids followed by about 20 years of Imuran. After a colonoscopy my GI doctor said that my colon shows no sign of damage anymore and that since Imuran increases risk for cancer that I should consider trying to reduce my dosage. After about a year of reducing I was totally off with no return of symptoms. Now I'm just on mesalamine. So, TL;DR, I got lucky. Good luck with your treatment.
Knock on wood, mesalamine has been good to me too. (Not quite remission atm but promising improvements.) IIRC most of its effect is in the large intestine, so it generally works better for people with UC, but I'm the same in that my Crohn's is mostly colorectal.
Unlike you I haven't had nausea as a primary symptom though, knock on wood. It's weird/interesting how much variance there is between Crohn's patients... fast food destroys me, but then you hear about people whose safe food is McDonald's :P
Yep. I've seen it used in place of 'CQ' when testing propagation conditions to avoid other stations coming back and attempting a contact. It always reminds me of the Doctor Who theme: ...- ...- ...-
Turbo Pascal 6 was the first high-level language I learned after BASIC and my first job out of college was doing Delphi development. I loved programming in Pascal, not so much because of the syntax (it gets a bit clunky at times) but because of the speed and ease-of-use of the development environments. Similar to having a REPL in a language, fast compilation is amazingly helpful for development iteration. If you can test ideas quickly, you can reason about things more quickly (at least in my experience).
For a very engaging documentary about the remaining team of Voyager 1 scientists, watch "It's Quieter in the Twilight". The ending kind of tails off, mostly due to the Covid pandemic, but it's a great look into how a group of aging scientists and engineers (the last to really understand how Voyager 1 works) are keeping it alive.
> ...but it's a great look into how a group of aging scientists and engineers (the last to really understand how Voyager 1 works) are keeping it alive.
That kind of brings up some interesting questions of team composition. When you're building something complicated that will last 50 years, you probably want a few people on the team who are: 1) talented, 2) very young (like fresh out of college), and 3) have the mindset of a lifer. You deliberately get them involved in all the stuff and put them in the room when all the decisions are made, then they serve to preserve the institutional knowledge of the project for the latter half of its lifetime.
I’m sorry but this comment just highlights how mind bogglingly bad we in tech are at documentation and knowledge transfer. The very idea that a single project can only survive as long as the same individuals are working on it is insane. For hundreds of years architectural projects have outlasted the original architect. Or just look at civil engineering: transportation networks, utility infrastructure, etc. The idea that every project must bring on a high schooler to maximise the longevity of a project before we have to start over is ludicrous. Our tech stack needs to prioritise stability, we need to learn how to document from our friends in other disciplines, our funding models need to expect smaller returns over much longer timescales, and we need a culture of celebrating those who do the tireless job of maintenance.
NASA, probably more than any private organization has reams of documentation. Every bolt is documented. Maybe, just maybe, electronic systems are more complicated than bridges and buildings that literally just sit there.
I do agree that we need to do a better job of celebrating the people that do maintenance which is what the vast majority of our field is based on.
This is interesting. When we talk about interstellar travel in the far future, this may be another issue to consider. The handover of knowledge will have to happen over at least a few generations.
It will end up being a software application whose development and upkeep sprints/projects will be measured in multiple years instead of weeks.
"NextNav’s Petition for Rulemaking. NextNav asks that the Commission reconfigure the Lower 900 MHz Band by creating a 5-megahertz uplink in the 902-907 MHz band paired with a 10-megahertz downlink in the 918-928 MHz band, shifting all the remaining non-M-LMS licensees to the 907-918 MHz portion of the band. Petition at 28–30."
