799 karma · joined March 11, 2014
Personal email: my username at gmail.com
Andrew Kelley - An Open Letter to Everyone I've Butted Heads With (2025 Aug 29) https://andrewkelley.me/post/open-letter-everyone-butted-hea...
My guess is that, like OP, we're both getting interference in the our DP connections, and that that interference is in our cases causing the GPUs to crash.
Haven't had a chance to try ferrite cores yet but that was going to be my first test.
Curious what system specs you have in case we have overlap in anything that could isolate the issue. Mine: https://pcpartpicker.com/list/Xpdb8Z
For example, if I wanted an AI to help me highlight to the user where in a body of text I mentioned AI, I might have it return something like:
<text>Great writeup. To add an example, I personally use JSON for most of my work, but have found myself using XML for certain <ai-mention>AI</ai-mention> use cases that require annotating an original text with segments.</text>
SelectIQ works with clinical trial sites and their referring physicians to automate the patient referral process, massively speeding up enrollment.
Bringing new drugs to market is primarily rate limited on the speed of clinical trials, which are themselves bottlenecked by patient recruitment. 80% of clinical trials don’t meet their recruitment timeline, and being behind on recruitment can cost pharma companies millions of dollars per day.
We're looking to bring on our first engineering hire to help us build out the platform and build an amazing culture. More details and application can be found here: https://www.ycombinator.com/companies/selectiq/jobs/4aRBMcX-...
Feel free to email me directly - jason@selectiq.ai
The shared feature between Temporal and those three is the workflow orchestration piece. All 3 can manage a dependency graph of jobs, handle retries, start from checkpoints, etc.
At a high level the big reason they’re different is Temporal is entirely focused on the orchestration piece, and the others are much more focused on the data piece, which comes out in a lot of the different features. Temporal has SDKs in most languages, and has a queuing system that allows you to run different workflows or even activities (tasks within a workflow) in different workers, manage concurrency, etc. You can write a parent workflow that orchestrates sub-workflows that could live in 5 other services. It’s just really composable and fits much more nicely into the critical path of your app.
Prefect is probably the closest of your list to temporal, in that it’s less opinionated than others about the workflows being “data oriented”, but it’s still only in python, and it deosn't have queueing. In short this means that your workflows are kinda supposed to run in one box running python somewhere. Temporal will let you define a 10 part workflow where two parts run on a python service running with a GPU, and the remaining parts are running in the same node.js process as your main server.
Dagster’s feature set is even more focused on data-workflows, as your workflows are meant to produce data “assets” which can be materialized/cached, etc.
They’re pretty much all designed for a data engineering team to manage many individual pipelines that are external from your application code, whereas temporal is designed to be a system that manages workflow complexity for code that (more often) runs in your application.
EDIT: I doubt OP is reading this but I would highly recommend they get insurance before giving birth...sure, they won't cover your at home birth, but they will cover your hospital stay if you end up having potentially fatal complications
Out of curiosity - the demo on the site suggests the local first latency is like 10-40 ms. I would think reading/writing to SQLite locally would be on the order of 1ms or less. Why is that?
Congrats on the launch!
"It has nothing to do with gender" is with regard to the ratio of BE to FE people in engineering leadership. I'm not making the argument that gender bias plays no role in promotion anywhere. It is possible for some things in the world to not be explained by gender bias.
I like CSS more than Tailwind -> Why don't people like CSS more? -> Maybe because 'CSS, which makes things look ‘pretty’, is considered feminine'
You're entitled to like CSS more, and I could even agree making things look pretty is feminine coded, but it obviously doesn't explain people's preference for Tailwind because Tailwind also exists to make things look pretty.
---
I've worked with plenty of female engineering leaders, and most of them have a backend background.
The reason for this imbalance has nothing to do with gender, but entirely to do with criticality. Given that frontends tend to read/write from the backend, the domain model is usually owned by the backend in most apps, meaning that capability design and expansion is gated by the backend.
Not to mention that screwing up your backend architecture is in 95% of cases a much much deeper problem than screwing up your frontend. A data migration is basically always harder than redesigning the UI for some app.
2. Their presentation showed someone using it with airpods on a plane
https://community.fly.io/t/preview-managed-upstash-redis-wit...
They don't have a managed postgres offering yet ("this is not a managed postgres" - https://fly.io/docs/postgres/getting-started/what-you-should...)
EDIT: recognize that these may be poorly timed but unrelated incidents, but it has been frustrating to be trapped on a broken box for 12 hours and have the status page telling me it's just new deploys that are borked :)
edit: One suggestion - maybe have a discord server that people provide support through, that way there's already an (IM-based) comm channel setup. Would def reduce the friction for me (and increase the chances I become a repeat customer)