> I'm hustling. I'm playing the game. I'm doing what it takes to make this thing mainstream and a viable, practical choice for individuals and companies. If you talk shit about Zig in public, I'm going to fight back. But I respect you. I see you. I understand you. I don't hate you. I would literally buy you a drink.
I've had the same problem for a couple years - specifically the GPU crashing. Had a very hard time isolating the issue - seems like a mix of static + the EMI spike OP talks about (it happens most reliably when I stand up quickly from my desk chair).
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.
My guess is that, in the vein of the "monitor flickering" symptom, your PC sees the DP/HDMI cable disconnect and reconnect due to the static. The reconnection wakes it up.
I pretty much only use o1 for more rigorous tasks (coding/math). Eg the other day I gave it the tax rates for my area and used it to explore different tax scenarios
Great writeup. To add an example, I personally use JSON for most of my work, but have found myself using XML for certain AI use cases that require annotating an original text.
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.
I recently evaluated Dagster, Prefect, and Flyte for a data pipeliney workflow and ended up going with Temporal.
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.
This is a pretty good way to go bankrupt when you have a real health emergency
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
Congrats on the launch, looks like a great product.
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?
I just had it fix some outdated copy in a part of the UI. The nice thing is I didn't have to find the file myself, I just described what was wrong like I would a junior eng and let it find and fix it. Worked on the first try!
Just merged my first simple PR with sweep. This is going to be so useful for the kind of things that would take 5 minutes to do but get procrastinated for weeks because you just can't find the time to context switch for it.
Obviously it is the argument, that's why it's titled "Tailwind and the Femininity of CSS". Or do you think the 5 paragraphs about how sexism causes people to dislike CSS is a non sequitur from the introduction about how the author prefers Tailwind to CSS. Break it down for me!
"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.
This article is hilariously bad. The argument goes:
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.
This looks great! Is there a reason one couldn't use this with v4 UUIDs? A quick test shows that they encode/decode just fine. Wondering if I could use the encoded form as a way to niceify our URLs without having to change how the IDs (currently v4 uuids) are stored
Personal email: my username at gmail.com