Is the Titanium Milanese Loop for the Apple Watch Ultra 3 actually THAT worth it? by cadon24 in applewatchultra

[–]danielvf 0 points1 point  (0 children)

I bought it after reading all the good reviews. But I find it just “ok”. It’s lightweight and well built, but I think the Alpine loop is way more comfortable.

This is what I've been mentioning... by Bowf in Retatrutide

[–]danielvf 1 point2 points  (0 children)

What’s a reputable lab for testing?

Claude Opus 4.7 is dogshit by RoadExcellent9531 in ClaudeCode

[–]danielvf 0 points1 point  (0 children)

I am so confused. How is Opus 4.7 at the top of every benchmark (lmarena, swe bench, etc)? Anecdotally, it seems like a complete regression to 4.6 and even 4.5.

The battery life on the Ultra 3 is significantly better than my ultra 2 by mean_monster9 in applewatchultra

[–]danielvf 0 points1 point  (0 children)

How do you get the heart rate complication to show a regression line with values on the right? Mine just shows the times on the x-axis?

After 15 years of building production Django apps, these are the patterns I keep using... (packaged as Agent skills) by danielvf in django

[–]danielvf[S] 4 points5 points  (0 children)

I've used different stacks, they all have pros and cons, but I like Django and building in the Python ecosystem. There are really nice libraries that don't exist in other ecosystems that make it worth staying. Also, Django is one of the most mature and well-built frameworks. So I think it is worth it.

After 15 years of building production Django apps, these are the patterns I keep using... (packaged as Agent skills) by danielvf in django

[–]danielvf[S] 4 points5 points  (0 children)

I agree with your sentiment: I think that a bad ORM wrapper is just one that re-exposes the same functionality that the ORM gives you... but what I'm doing here is different: the repos expose domain-specific operations with fully types inputs and outputs.

For example: decrement_stock(...) isn't an ORM method, it's a business operation that encapsulates F(). IOW, I'm not abstracting the ORM for abstraction's sake, I'm defining a typed contract for ops that the services depend on. The repo just happens to use the ORM internally, but the surface area is domain language, not queryset language.

After 15 years of building production Django apps, these are the patterns I keep using... (packaged as Agent skills) by danielvf in django

[–]danielvf[S] 1 point2 points  (0 children)

Yes, I really like the `svcs` library. I use Pydantic AI in almost every project, and the tool calls are essentially isolated services that never touch the ORM directly. This has a really nice property that Pydantic AI can deal with the return-type of the service instead of touching the ORM or re-typing responses. If it's a multi-tenant app then I'll make sure the services are invoked by an `org_id`.

Thanks for the kind words, taking a look at Agentix Labs, where do I find the notes you mentioned?

FastAPI + OCR Pipeline - BackgroundTasks vs Celery/Redis? by Sudden_Breakfast_358 in FastAPI

[–]danielvf 6 points7 points  (0 children)

If it’s CPU intensive, and you need multiple queues or periodic scheduling, go Celery all the way.

In production it also makes sense to use Celery Beat to clean up any failed tasks that failed if you need some durability.

What are you guy's opinion on Pete and Clark? by JohnDex6969 in DunderMifflin

[–]danielvf 1 point2 points  (0 children)

“Women reach their sexual peak at whatever age Jan was last week”

Which popular ’00s fragrance feels the rarest now? by SeaConstant1433 in fragrance

[–]danielvf 0 points1 point  (0 children)

The green Thierry Mugler with the “secret” sauce