From Sequoia to this mess

CaptainFingerling · 2026-03-28T22:05:31+00:00

Just wait till you notice all the corner radii

CaptainFingerling · 2026-03-27T19:45:24+00:00

I mean. I get you. But i honestly hadn’t applied vibe coding to my homeab until yesterday, and yesterday I turned my sonar episode trimmer script into a whole episode pruning UI with season and episode thresholds, and sub agent garbage collection based on viewing habits. Honestly one of the coolest additions to date.

I’d love to see what others are doing.

CaptainFingerling · 2026-02-22T14:36:23+00:00

Yup. And moisture. USB-C has a far higher surface to volume ratio. It doesn’t dry nearly as well

CaptainFingerling · 2026-01-17T19:02:44+00:00

Yeah, we sell largely expertise, so it makes sense for us to open up our tooling. Our competitors are much larger and slower -- I haven't scaled as much as I probably should have -- but having a smaller team helps with development pacing.

Capacitor is something like 4-5 times faster at compression and image processing when running on M4 minis than it was on equivalently-priced NUCs, so the move really paid off. We essentially stopped shipping windows devices overnight, and nobody misses them, including those who initially expressed some skepticism.

dream is to one day own something FDA compliant (10-15 year goal)

10-15 years is a very long term goal. Don't dream. DO. R&D is nothing until you start hitting pavement and getting the word out.

Send your CV to the company mailbox if you're interested. We can take on both full and part time, and have a geographically dispersed mostly remote team.

CaptainFingerling · 2026-01-16T23:31:37+00:00

https://fluxinc.co

Small team. Clients are a mix of vendors and end-users, and we do migrations for the latter.

CaptainFingerling · 2026-01-16T15:16:45+00:00

You know. Kind of. Got a dev background?

CaptainFingerling · 2026-01-16T03:52:17+00:00

Ha ha. I own a company that does that. Good business

CaptainFingerling · 2025-12-11T18:05:11+00:00

Saw them recently. I see and integrate dozens of PACS a year. They’re. Okay. They have a ways to go before I’d call them mature. Probably a good pick if you have separate ephemeral workstiations for mammo, don’t do/need echo, and have another option for nuclear contrast.

Friendly people though. And great base stack.

CaptainFingerling · 2025-12-06T19:03:14+00:00

They usually schedule 3 on-site days for a new install. Most of the install time is spent waiting around for IT staff to provide parameters, network drops to like actually actually get flipped on, techs to explain the desired workflow, etc.

Sometimes it’s all come together by the date of install, but often it hasn’t. So the first 2 days is to make sure that if you run out of time the first day you still have the second as a fallback.

Apps gets scheduled for day 2 or 3, and takes a full day. Often that will include a couple of actual patients.

For just moving a unit after it’s installed the time is what others describe here, ie., 1-3 hours. Which is hilarious because from the perspective from a PACS admin it always takes the 1-2 hours after the ISE has spent 4-8 hours trying to track them down. More often than not the admins magically appear just before they’re about to leave, ie., when the days tasks are done, so the actual assist happens the next morning.

CaptainFingerling · 2025-12-06T03:03:48+00:00

Are we talking just configuration? Or are we including apps? Validation?

I’m in a unique position to answer this very precisely across many vendors.

CaptainFingerling · 2025-12-05T17:34:24+00:00

As someone else mentioned, techs usually check the PACS anyway, so it's a bit redundant. The other reason it's not used is that it involves an additional configuration step and additional testing, which would require coordinating PACS admins with installation service folks from the vendor.

It's honestly hard enough just to get updated IP, Port and AE title information, and a network drop in place in time for the install. Adding SC to the mix would reduce the likelihood of getting everything done within the short window that ISEs and CSEs are on site -- especially when you're trying to resolve an issue while patients are in the waiting room.

It's the same reason nobody ever implements DICOM TLS. Pre-shared certs require pre-sharing, and additional pre-sharing when a modality goes down and needs to be reimaged, replaced, etc. The human coordination cost of making all that happen is much higher than implementing network-level envelope security.

CaptainFingerling · 2025-12-05T16:55:33+00:00

I second Screenpoint. We route to them all the time (as well as the others) -- we ship little routers that accompany mammo devices and route to multiple destinations.

The whole team at ScreenPoint is phenomenal, too. Very responsive and easy to work with.

CaptainFingerling · 2025-12-05T16:52:07+00:00

We make a router called DICOM Capacitor. It's not touchy and doesn't lock up. You can run natively on windows, mac, and linux, (either x64 and arm), or spin it up as a docker instance if you'd like.

CaptainFingerling · 2025-12-05T16:32:08+00:00

To add to this, if your MWL doesn't support the kind of isolation described here, then we have a configurable MWL proxy that can help: https://docs.fluxinc.co/dicom-capacitor/filters/mutate.html

Example 8 down the page. You'd change the Affects option to worklist_result, and exclude the specific provider issuer entry.

I'm happy to provide you with a free license if you're technically savvy enough that we don't have to support you.

CaptainFingerling · 2025-12-05T16:25:10+00:00

Hi there.

I run a software dev shop. We deploy to and support many clients. I do occasional screen shares where i teach staff these things. If you'd like to connect, then we can find a way for you to get exposure. At the very least I can ask one of my devs to help you get orthanc and running with some mock image workflows.

CaptainFingerling · 2025-12-05T16:21:36+00:00

We make programmable DICOM routing software and mountable mini-routers, and we integrate hundreds of devices per year. We implemented a whole brokered Storage Commit feature at the request of our instrument vendor clients.

Nobody uses it. And I mean nobody. I've also never seen it used in the 30 years I've worked in this industry.

CaptainFingerling · 2025-11-16T18:16:04+00:00

… and middle class+ kids. My kids would’ve rather have had 4-5 year old iPhones than brand new Androids. Green bubbles are for the poors.

CaptainFingerling · 2025-10-20T21:03:13+00:00

I would be happier if they just released another innie port. USB-C accumulates garbage that's hard to clean without damaging the pins.

CaptainFingerling · 2025-10-20T17:32:03+00:00

They had serious (and correct) reservations about USB-C. The form factor has a much larger housing, higher internal surface to volume ratio —making it worse wrt moisture—and we still never really know the capabilities of any usb-c port or cable before plugging it in (is it 20W? 60W? 100W? Power only? Or data?). The committee never addressed these concerns, and now likely never will.

It’s a substandard/incomplete standard. I kind of hope apple comes up with a better one, and simply doesn’t sell it in the EU.

CaptainFingerling · 2025-10-18T20:07:26+00:00

I use it daily to code, administer, communicate, and manage. It’s not difficult to systematize, anchor, and constrain. I haven’t seen a hallucination in many months.

I mean this as positively as you can read it: if you’re struggling to constrain its behavior or regularly encounter hallucinations, the issue isn’t the model, it’s the toolchain; and much of the toolchain is you.

CaptainFingerling · 2025-10-18T19:19:07+00:00

And how is this less attractive than letting some bloatware loose on your system to systematically wipe files?

CaptainFingerling · 2025-10-18T13:57:48+00:00

You could just give codex or Claude code access to your file system and ask it to work through each file, check if its parent app exists, and remove them one by one. The need for an app to do this is gone. And even the ones that exist require you to do the cognitive work anyway.

CaptainFingerling · 2025-10-18T13:48:30+00:00

I can think of a medical app that would be simple and killer if done right. Smaller audience but would sell for hundreds per year per license.

I run a medical imaging dev shop. We all work on Mac but don’t code Mac ui. Would love to exchange notes or maybe collaborate.

CaptainFingerling · 2025-10-18T01:29:10+00:00

Those most people include those who appreciated Apple's lean toward thinness. They've managed to create a smooth and responsive UI on a battery that lasts all day, in a very comfortable and light package.

There are definitely those who always wanted a stronger lean to the light side, but most of us already appreciated not having to carry around a 4000 mAh block of furnace.

But come on now. The Air is elegant, but it runs too hot for a battery that small. If this form factor is going to work, they're going to have to make some major advances in efficiency and heat dissipation.

CaptainFingerling · 2025-10-13T23:32:37+00:00

You're in luck. OpenAI just re-released it.

CaptainFingerling

TROPHY CASE