486 karma · joined December 16, 2022
We seem to be rapidly approaching an inflection point, brought on by the compounding distributors such as Hims, that will need to be resolved: there are probably more people on the compounded version of this drug than most suspect and that number is growing by the tens of thousands every day. Meanwhile, Norvo Nordisk is trying to shut down this channel of distribution. That would be a bad idea and I think the FDA must be aware of that. This conflict between NN and the compounders needs to be resolved.
Personally I think the promise of this drug makes it a moral issue and have little sympathy for NNs position here: they will need to capitulate on their control over it and accept some kind of suboptimal pricing agreement. The potential positive outcomes of this drug supersedes their sole claim to it IMO.
Heh that was my first instinct as to why they built this as well but more for providing ergonomic ways to generate k8s objects for complex gitlab specific CRDs.
Additionally if you are hunting for sustenance, as in you really need the meat, then you take the first deer you can find. Waiting for the ideal deer is a good way to not end with a deer at all, regardless of whether you have them on camera or not.
Is lawsuit language usually so... dramatic? The tone of this document is weird...
These requests can be granted manually or automatically but they need to be logged and stored. Sometimes requests are required for every single access of a tool and sometimes it's time period based (24 hour access to Redshift or whatever) -- usually this depends on your role in an org. There isn't a coherent out-of-the-box way to provide the authorization and access gateways across all the different tools a business relies on -- so there is a big business opportunity for companies to basically provide turnkey identity and access management tools for companies.
Or, occasionally, an engineer loses their mind with the inefficiencies of these systems and processes and goes off on a jag to create the perfect internal tool to solve all these problems. That rarely (if ever) works, hence the video.
I suspect the rate of individualized adoption of AI augmented writing is well beyond what a casual observer here on HN would think it is.
I also share Chiang's worry about this:
> We are entering an era where someone might use a large language model to generate a document out of a bulleted list, and send it to a person who will use a large language model to condense that document into a bulleted list. Can anyone seriously argue that this is an improvement?
I do not think OpenAI Et al. set out to create a self-perpetuating slop machine like this but it sure feels like this is where it is going. For individuals it improves their life I guess but when zoomed out there is something quite dystopian about it.
Chiang is not saying this at all. I'm not sure how you interpreted it this way.
I have YT Premium and it works perfectly on every device I have and I have never had to configure anything nor research anything to not see an ad. I only vaguely understand some of the phrases or words you are using (have no clue what a newpipe is, but kind of understand what sideloading) is. I do not care to ever fiddle with my devices, there are more important or at least gratifying things in this world then futzing around with and tweaking devices.
> Paying for YouTube Premium is your eternal reward for submission to the Walled Garden.
If this is the great battle you have chosen to wage with your precious, fleeting time on earth, by all means, go with God -- but a lot of people really don't give a damn about Walled Gardens.
Perhaps that is true... I'm a Rails dev and ActiveRecord definitely tracks mutations on the object and selectively updates.
I would assume this is consistent with Django and I'd assume a policy is probably required to be specified by SQLAlchemy.
An example would be updating Kubernetes resources, the admission controller will verify the correctness of the change you are trying to make and reject the patch if it's non-comformant. Nested values have... value... in terms of contextualizing and isolating/localizing data leaves but at the end of the day aren't you still dealing with strict schemas and, when those schemas change you have to reconcile schema migrations?
All well and good but you do need to handle failures elegantly in code. The nice thing about flat DB tables and SQL is you don't really have to care if your goal is to update a single column authoritatively. The state of the other values in the table are, often, immaterial. It gets even more complicated reconciling deeply nested conflicts in open schemas.
Not knocking your approach, it's just a trade-off I guess.
My beef, if you will, with async (and I realize now I was a little loose in making the distinction between async and fibers) is that engineers reach for async because they are intimidated by threaded code. Instead they are used to the ergonomics of async/await in the browser and think it's basically the same with the async library in ruby and is somehow immune to the considerations you have to make when spawning a thread. This just isn't true. The dragons are mostly the same, or at least they are in our code base.
Fibers are cool and performant but usually they should be limited to lightweight work with large concurrency requirements.
But I dunno, he may just actually believe he's the most famous millennial ever. He's up there but I don't know how one could ever quantify that.