They have oceansize vibes. Must have been a great evening!

Looks great. Any plans to release for the Switch?

Yes! Switch version is in QA so we hope it will only be few months away from PC release.

I’m struggling naming my views. Any recommendations? Same naming as tables?

For what it's worth. I like to call out views in the naming.

I'll typically use a "vw_" prefix prior to a name which would be similar to table naming. "v_" is also an option, but I also write a lot of DB functions and stored procedures and with all the types, tables, and column names that get used, indicating variables and parameters can be helpful... so "v_" indicates a variable name in the function context which is why views get "vw_".

I do this but at the end: some_table_vw

That's an easy swipe to make. What would you suggest instead?

> But definitely not within database functions and procedures.

I generally find Hungarian notation silly, however, there's a compelling argument to have them in functions and procedures — perhaps more than for views. The type of the variable matters just as much as where/how it was declared, such as in/out params.

That's the 'steelman' argument for them, as I understand it.

Mid-range one-liners don't really make convincing arguments, though do they? I appreciate this comment may have been made more in service of a certain smugness and self-satisfaction rather than any real or concrete complaint... but you do you.

On the flip side... perhaps using techniques from the 80s with a programming language and paradigm also from the 80s... and that hasn't changed all that much... isn't all that crazy.

At the end of the day: the evaluation of a given technique such as I described, should be measured against if it makes the development experience simpler and more comprehensible. Being able to instantly tell if a given reference in a procedural query comes from a table a view, a variable, or a parameter, I find helpful since we're typically using many names from these different origins and contexts and frequently side-by-side, such as in a complex query driving the procedural code.

Of course, If you don't like that, or simply don't find it sufficiently "modern" or "fashionable" (my God, what might others think!?)... again, I invite you to do you.

Ah, naming things. Something about one of the hard problems in computer science...

I think consistency is more important than perfection. If you use something like vw_ as recommended in the sibling comment, that's fine, then try to apply it to all views. (Without being overly strict; sometimes there are good reasons to defy conventions. They're conventions, not laws!)

Just keep in mind that a view is both code and a data contract just like a table definition is. All the usual best practices around versioning, automated deployments, and smooth upgrade paths apply. As soon as an application or downstream view, function, etc relies on that view, changing it risks disruption or breakage. Loud breakage if you're lucky, silent data corruption if you're not!

Zed has quickly become my daily driver for mostly python and some rust development. Awesome editor.

Django-Ninja is fantastic and based on pydantic.

This. I found DRF gets very confusing with all the abstraction for complicated stuff. For simple APIs, it's very nice (I used it on govscent.org). SidewaysData uses Ninja and I love it so far.

DRF becomes hard to understand when you use magical stuff like class based controllers and so on. stick to functions and it's actually very simple!

You're absolutely right - however I did not even know I could use functions. I didn't see that in the docs somehow.

Also I think I remember with DRF I had trouble generating a good openapi client. With ninja it works really well.

I much prefer Ninja as well. Is it active, these days? It feels like it's got much less of an ecosystem than FastAPI.

> Is it active, these days?

Yes. They are currently migrating to Pydantic 2 which Ninja 1.0 will be based on.

We had a lot of trouble with the IoT Core shutdown.

I can recommend Mouser, DigiKey and RS-Components.

My AirPod Pros emit some loud, short static noise bursts from time to time. Mostly in situation where there is a single loud noise in the environment.

I think there is a replacement program for this issue - https://support.apple.com/airpods-pro-service-program-sound-...

Thank you! Spoke to Apple support and will now send them in. This seems to be the problem.

Like ultra sonic bursts from devices trying to identify other devices in the room? What a irony that would be, add tech destroying the hearing with which they try to reach the audience.

Extension: Use pipx for pip python applications like ansible.

So the first pyramid is standing?

With the "functionally equivalent" rule (i.e. if the wording is different, but the Master can't find a counterexample, the guess is correct) this might not be too hard to find.