idealmedtech

Welcome to cyber security in medicine! Stay a while!

There's lots of mentions of Maps.ME, which is no longer open source. The spiritual successor is called Organic Maps

Code execution of code written by your own engineers!

That's the one!

My old workhorse T530 is now a home media center, and it's snappier than ever, even with KDE and all the window effects!

On a similar note for Windows: Everything Search. Blazing fast, super easy syntax, powerful search tools. Almost don't remember where most things are stored on my hard drive these days, since they're all just a shortcut and a few characters away

How do you manage the keys? Rotation every now and then? New keys with each deployment?

Axiom of choice isn't really relevant to Godel's work, except for the fact that it's part of axiomatic systems. But in response to your comment, I was pointing out that there's lots of interesting math that comes from the results of his work; namely under different axiomatic systems you can find different and interesting results.

There's whole _fields_ of inquiry that either take or leave the axiom of choice; so yes, absolutely.

No, he proved that under existing axiomatic systems, there are some statements which cannot be proven to be true axiomatically, even though they are true; such axiomatic systems are, in his terminology, incomplete. A subtle but important difference.

Millionaires and billionaires are typically NIMBYs, not YIMBYs (although in SF being a millionaire is common enough that this probably isn't totally true)

> it simply issues (with a refund of the permit processing fees) if the deadline passes.

We're a medical device company with Breakthrough Device status, and it works largely like this. Whenever we submit, FDA has 30 days to reach a decision from time of receipt, and if they don't decide, we automatically get approval. Really helps with keeping up momentum!

Never since have I found such unique and interesting web apps/essays/videos. Was very cool how it took you to the actual site, but somehow felt a lot more curated than the link aggregators of the time. Every single click was so fun! One of my favorites was a sort of proto- /r/place, where you could place pixels as many times as you wanted on an infinite canvas. Sometimes you could return days or weeks later and still find your art.

Ah, my apologies! This is the one I thought you were associated with; one letter makes a big difference: https://www.volusion.com/

I figured it was one of those "founder-has-a-blog-with-very-similar-name-to-capture-new-users" situations. Nothing wrong with it, just something I feel it's important to be aware of. Sorry for the mixup!

Quick but important note: for those who don't know already, Volution sells a square space-esque managed site builder with hosting, which means this post does have a minor conflict of interest (although these days I guess it's called content marketing). Haven't seen it mentioned yet in the comments.

I haven't read the code, but I'm guessing the API they're using would allow them to track _all_ changes. The only reason Reddit works that way is because they choose to only keep one version of the comment internally (or at least they did back when most reddit deleters were in use, in 2017 or so). It's architecture, not some fundamental limitation, that causes that to work, although it may not actually work anymore. Only reddit knows that.

> First and foremost, for reasons that are unclear to me, ObfDereferenceObject is exposed to driver developers through a macro3 called ObDereferenceObject. I don’t understand what the point of this even is, but in any case, we can find the documentation for the macro here.

Emphasis mine. The reason why this is done in big projects is adding just one more level of abstraction to be able to preserve how userland interacts with your library, but still allowing you to make underlying structural changes to the code.

You mean VGA? Most every monitor these days still has VESA mounting holes.

Anecdotally, I've found that coil whine is much less of an issue in their chunkier models, eg P53 (not P53s)

I'd love to see that distribution at the end with a log-axis for the file size! Or maybe even log-log, depending. Gives a much better sense of "shape" when working with these sorts of exponential distributions

I originally just stumbled upon it myself (when I first started I was reading a lot of topology books), but that video was great for showing the load strand effect! Felt great to have stumbled into the "right" way by accident

If you clean a figure 8 really well, it's just as easy to untie after a whip as a bowline (okay, maybe not just as easy, but very close), and much much more universal for your partner to inspect.

The process I follow to ensure a clean knot every time:

1. Tie your figure 8, with the tail the same size every time (use your body as a ruler, testing a few lengths to get the perfect size)

2. Pass the tail up through your hard points so the knot is only a few inches from the bottom hard point.

3. Orient your knot so the tail is coming out of the bottom right side

4. This is the most important step! Instead of passing the tail through the inside of the knot when starting the followthrough, pass it in between the tail strand and the bottom right of the knot.

5. Follow through as normal. It should come out almost clean (eg no need to flip strands over each other)

6. For all 4 combos of top and bottom strand, yank them to make the knot very tight. The tighter and cleaner it is, the easier to untie after a whip.

7. If you do this all, the load strand will be on top, so no difficult flipped strands after a whip!

This is just my process, what's most important is doing something that works for you and that you can get right every time.

Back in college, the engineering school had a farm of Linux servers from which you could access all your documents, as well as log in to your account from any number of computer labs around campus. Back when I was first learning Linux (not that long ago, 2008), I fell in love with how many things you could customize, and really create your own experience. When I got to college, I wanted to replicate this ability (install ANY program! use ANY desktop environment!), but predictably, their machines were pretty locked down.

I went snooping around the internet, and found that there was this magical software called Nix, which would let you have a package manager without root! The Linux computers in the lab didn't have root, but they did have GCC. I started learning all about build systems (mainly that you could specify a custom --prefix and essentially create your own filesystem within your filesystem), and got to work compiling Nix (or, i think, GUIX) from source. It's actually a fantastic amount of work to go from GCC all the way to a functional GUIX, even with access to every source tarball on the Internet

Eventually some admin emailed me about this project and I stopped working on making it happen shortly after, but it was such a formative experience in my tech life that I always think back fondly on it when Nix pops up.

Pluton is also a geological term, referring to magma domes that have solidified and since eroded to yield granite structures like Half Dome.

There are many many very difficult parts to novel drug developments, and I'm not saying they will have success finding something that doesn't infringe and also scales. What I'm saying is that the strategy of doing everything yourself with startup level funding and experience is not optimal, and you can save money and time by outsourcing at the beginning.

Most older expired IP insulin just isn't very convenient to use for most people; it requires more intense participation from the people using it, so you tend to get worse results (imagine if you had to actively think about breathing in enough oxygen every single waking hour of your life -- it's exhausting). The longer acting, more specialized insulins are still heavily patented. When insulin takes longer to work, the person using it has to think less about the insulin and actually gets to live their life rather than think about blood sugar all day.

Now, if you closed the loop and used older insulins, you'd have good control and less issues since a computer would bear the cognitive load, but glucose control, especially in the outpatient setting, is ridiculously hard. If you think you can solve it though, give it a shot. It's a multi billion dollar market and a lot of lives you can improve.

No one in their right mind would build manufacturing from scratch. Contract manufacturers exist to do relatively cheap design work in exchange for access to their expensive-to-build (but cheap to use by comparison) manufacturing facilities.

I can't speak to drug manufacturing, but I know from experience that when it comes to medical devices, you save almost 10x in up front fixed cost by outsourcing, like California is doing. You spend more per unit, but still profit, so you can build a healthy warchest while you accumulate experienced personnel to build out a more vertically integrated manufacturing process.

The biggest issue with DRY is commitment to a bad abstraction just for the sake of not copy-pasting some code. Abstractions should be liquid while you're figuring out the best way to model your problem, and DRY can often be a culprit in having a model that's a bit too rigid.

Obviously YMMV.

I've found my general file organization suffered with this but my naming of files improved dramatically! Great tool.

If anyone is looking for a text only free version of this, check out 68k.news, found it here a few months ago.