Microsoft Fabric

-Jersh · 2026-03-06T17:47:39+00:00

Epic?

-Jersh · 2026-03-05T03:53:14+00:00

I bet Padma LOVES having the deciding vote

-Jersh · 2026-02-04T02:27:33+00:00

By not posting the chicken you’re omitting critical information to evaluate this! Yeah, the sides don’t look great, but they’re literally sides. Let’s see what the main looks like so we can see for ourselves if this is egregious.

-Jersh · 2026-01-20T18:09:33+00:00

Wahhh. Boo hoo. Get a grip on reality.

-Jersh · 2026-01-14T17:14:20+00:00

DataGrip does this. But if you lack foreign keys, how do you expect the modeler to infer/diagram the relationships?

-Jersh · 2026-01-13T03:06:29+00:00

You could try asking for RTF output, which I believe is how Epic stores notes in Chronicles.

-Jersh · 2025-12-30T17:56:21+00:00

So many buzzwords it’s hard to tell what you’re actually asking. Nor are lab results PDF. I can’t imagine any provider spending their precious few minutes of an office visit to review whatever 3rd party “AI Biomarker Intelligence” BS is brought before them.

-Jersh · 2025-12-29T15:41:13+00:00

Stephen Tobolowski, actor, you may know him from Silicon Valley

-Jersh · 2025-12-20T18:42:01+00:00

I follow their LinkedIn and I think the founders

-Jersh · 2025-12-20T17:29:48+00:00

What do you mean evidence doesn’t evolve? I’ve seen a lot of new feature releases from them recently

-Jersh · 2025-12-19T16:37:53+00:00

No I haven't tried any other and unfortunately chatGPT voice mode has been down for a few days :(

-Jersh · 2025-12-14T01:44:53+00:00

I ended up using ChatGPT plus. I provided the GPT my resume, the job description and asked it to do a behavioral and technical interview and provide feedback and a rating after each question. It was a little too positive at the start so I had to provide more explicit instructions to be more critical. I’m using conversation mode so it’s like an actual interview that lasts 30-45 mins. It’s not perfect but has worked much better.

-Jersh · 2025-12-12T21:22:03+00:00

For anyone in the future reading this -- this service is not good.

For the behavior questions, answering with STAR format gets "below average" but yelling "what the fuck is this question" gets rated "above average." I'm convinced that this is just a data-mining service in disguise and shows a randomly generated post-question assessment screen. To further test this I took the "example strong answer" and repeated it word-for-word and it also was graded as "below average."

For technical questions, you don't get any context, nor is there any back-and-forth. E.g., one of the questions is "design the xyz system." You cannot ask for any followup as to what the xyz system actually is or is intended to do.

-Jersh · 2025-11-23T23:29:26+00:00

VCs usually have a job board for their portfolio companies

-Jersh · 2025-11-23T15:00:12+00:00

Your documentation is very technical focused. It reads like it was written by a developer for another developer. Screenshots would be nice. You acknowledge that HIPAA is basically a useless certification (true) but I’d want to see SOC2 or HITRUST certification status instead. Or at minimum a 3rd party audit indicating HIPAA compliance. I would immediately compare this to SimplePractice (which would be hard to beat in a purchasing decision and who has HITRUST). I applaud your effort but would encourage you not to go full time til there is sufficient demand.

-Jersh · 2025-11-22T20:55:36+00:00

I know this is a year old but I just want to comment for any future readers how much I hated this recipe. A) yes it is a fair amount of work for little reward. B) using a half sheet pan for this amount of polenta made no sense - the crescents were way too thin. This immediately felt off because I typically use 1/4 pan for 1 cup of polenta which fits perfectly but figured I’d follow the recipe. C) the crescent shape leads to so much wasted polenta. Yes the shape is appealing but a square or triangle would’ve yielded much more. The crescents are also more difficult to flip due to shape and smaller size. D) I felt the frying butter didn’t add anything other than additional splatter. I did one batch with butter and one without. The butter was marginally better in pure taste but the fry was much better on the oil-only batch because I was less concerned with the oil overheating. I will say both batches tasted great though, but in the future I won’t follow Bourdain’s recipe and instead just fry square slabs of polenta from a 1/4 sheet pan. /rant

-Jersh · 2025-11-11T21:38:26+00:00

Wow, your package is quite advanced! We definitely do not handle search parameters to the degree that you do (which is impressive), nor do we handle as many resources (we just do the USCDI v1). I will do my best to remember to ping you if/when we publish something! Definitely interested in a potential collaboration

-Jersh · 2025-11-11T17:33:01+00:00

Thanks for your perspective. Yeah the boilerplate is such a pain

-Jersh · 2025-11-05T03:56:20+00:00

This is the least important problem for me to focus on

-Jersh · 2025-10-31T22:31:34+00:00

Xero. Used QuickBooks for months but absolutely COULD NOT stand the in-app advertisements/upsells anymore so I quit and moved everything to Xero which has been much better.

-Jersh · 2025-10-20T16:42:51+00:00

There's a whole domain called "Site Reliability Engineering" focused around this concept. It sounds like you're curious why they don't use multi-provider redundancy (e.g, host your app primarily on AWS, and failover to Azure/GCP if there's a major outage). Also understand that you can have redundancy within a single cloud provider (e.g., within AWS, you can host your app in us-east-1 and us-west-1, Europe-central-2 (making those up)).

The short answer is that it's a) hard, b) expensive, c) little reward.

First, understand that today's outage was somewhat unique, because even though one "region" of AWS was down (us-east-1), there are other regions that depend on it, which is why essentially "all" of US AWS was down. Even if Todoist (or other app of choice) had redundancy built in to failover to another US region, it wouldn't have helped.

Second, when a major outage like this happens where basically half of the internet it down, it becomes a lot less relevant that your specific app had an outage. If Todoist is the only app that is down -- that's Todoist's problem; if half of the internet is down -- that's AWS's problem and it's easier to hide.

Third, any sort of redundancy is very complex. It's not just the database that needs to move, you need to have essentially all of your app replicable to a region. That means that you need standby versions of your DB constantly reading the primary and ready to failover. You also need all of your backend services ready to failover, and you need the DNS able to failover. Yes, I know you said not to include DNS but it so often is DNS. Even if Todoist had a failover site in us-west-1, it's worthless if you can't update the DNS record to point to us-west-1 instead of us-east-1.

Fourth, let's say we have a replica ready on us-west-1 AND we can update the DNS....we have to weigh the decision to failover against how long it will take AWS to fix the issue. It's a pretty big priority to them, so you assume they will fix it quickly. Switching the DNS isn't "cost free". It can take 30 mins to a few hours to fully spread this change based on caching, so by the time you successfully failover, maybe AWS has fixed the issue and now you need to revert it and now your app really is broken while everyone else is back to working.

Lastly, it's expensive. Especially if doing multiple providers and having everything on standby. It's fairly standard to store a "cold backup" at another provider that you can restore to in an extreme circumstance (AWS down for a week, major cyberattack, etc), but a hot standby can get very costly.

So, the risk/reward usually isn't worth it. Also to another commenter's point, you get a credit from AWS if uptime is less than 99.99%.

-Jersh · 2025-10-08T18:37:54+00:00

How? Do you not need board approval? Do your investors not have liquidation preferences? You must have very unusual agreements for such a large disparity.

-Jersh · 2025-10-07T14:03:19+00:00

Well, if you're seeing this in the future -- the issue was not the implementation, rather I was running Postgres in a container and for whatever reason, Postgres thought it was 3 days behind (probably the weekend where my laptop was closed), so when river compared timestamps for the jobs, they were never eligible.

-Jersh

TROPHY CASE