colemannerd

il y a 16 joursdiscuss

Marfa is an amazing little town. I was there 3 months ago; while it is out of the way, even as a visitor, everyone is nice and genuinely there to provide an amazing artistic experience. If you ever want to experience the actual weird, southwestern, cowboy country, go to Marfa. And have a drink outside this public radio station. It's quite a nice getaway.

colemannerd

le mois dernierdiscuss

Thank you mike!

colemannerd

l’année dernièrediscuss

Please be careful. I'd love to adopt Dagger, but the UI in comparison to GHA, is just not a value add. I'd hate for y'all to go the AI route that Arc did... and lose all your users. There is A LOT to CICD, which can be profitable. I think there's still a lot more features needed before it's compelling and I would worry Agentic AI will lead you to a hyper-configurable, muddled message.

colemannerd

il y a 2 ansdiscuss

Thank you so much! I’ll be watching

colemannerd

il y a 2 ansdiscuss

Are migrations still specified in json?

colemannerd

il y a 2 ansdiscuss

default values! Since type hints are *hints*, it is difficult to set default values for complicated types. For instance, if you have lists, dicts, sets in the type signature, without a library like pydantic, it is difficult and non-standard. This becomes even more problematic when you start doing more complicated data structures. The configuration in this library starts to show the problems. https://koxudaxi.github.io/datamodel-code-generator/custom_t...

The issue very much is a lack of a standard for the entire language; rather than it not being possible.

colemannerd

il y a 2 ansdiscuss

We've migrated our pyenv poetry application - that's pretty complex with data pipeline flows and apis. The only issue we had was loading .env files - we had done some custom env var scripting as a workaround to an AWS issue and that was hard to migrate over. However, once that was done (and was due to bad implementation initially outside of poetry), moving from poetry to uv was rock solid. No issues and it just worked. I was surprised.

colemannerd

il y a 2 ansdiscuss

I would really encourage you to think more on this. Good enough for you... is not really the goal. We want standard tools that help with packages and virtual environments that can scale to an organization of 2 python devs... all the way up to hundreds or thousands of devs. Otherwise, it fragments the ecosystem and encourages bugs and difficult documentation that prevents the language from continuing to evolve effectively.

colemannerd

il y a 2 ansdiscuss

I think this is a great take. I'm on board on the HCL hate - it really reminds me of shoe-horning a templating solution into a complex, code level concern - but just removing YAML is not enough. My one caveat to this is a lot of the "platform engineering" products out there right now seem to want to abstract away all concerns behind a UI, which is just replacing YAML with UI problems. What we really need are open-source, cross-language sdks that allow self serving by developers using the tools they already know, but with additional configuration being able to color that settings by more specialized folks in their areas. For instance, an sdk that lets developers say ram is light, medium, heavy, etc. in whatever language they operate in; followed by a review of the sdk and some additional configuration layered on by the ops folks who monitor the entire company's spend and define what light/medium/heavy is. Too many of the platform engineering "solutions" seem to be about vendor lock-in.

colemannerd

il y a 2 ansdiscuss

I've personally seen the issues the article mentions with pyenv and virtual envs first hand when relying on pip.

colemannerd

il y a 2 ansdiscuss

BUT importantly... it REALLY does not work well for lots of teams. For me, this setup has caused production outages multiple times across multiple teams. Maybe the root python ecosystem should learn and adopt from other ecosystems that have figured out complex deployment in a much easier way.

comments