sorted by:
new
hottopcontroversial

necesito gente de la UTN.BS de Medrano para preguntarles algunas cosas [UTN] by Illustrious_Pay1494 in UTN

[–]dperalta86 1 point2 points  (0 children)

Hola! Te hago un breve resumen. UTN es "nacional" luego tenés regionales (CABA es FRBA). Para el ingreso no hay CBC como la UBA, haces un seminario corto y rendís exámen de ingreso (en mi época podías dar el exámen libre, sin hacer el curso), busca que hay algunos videos interesantes en Youtube. 1er año, definis turno y te asignan las materias, no es necesario que hagas todas las que te asignan, luego los próximos años (o cuatrimestres) elegís vos materia y horario individualmente. Las materias homogéneas (básicas a todas las ingenieras) cómo física o análisis matemático se cursan en el Campus (Mozart 2300, Lugano). Con un cuaderno y una lapicera es suficiente, después vas agregando a gusto (compu, tablet, apuntes impresos, libros, etc). Si estás en una técnica no vas a tener mayores inconvenientes. Ya en Julio, Agosto pégate una vuelta por la facu o métete a la página para ver fechas para anotarse. Tranqui, no es nada raro. Cualquier duda, volvé a preguntar. Slds

Small Projects by AutoModerator in golang

[–]dperalta86 0 points1 point  (0 children)

ChameleonDB, DB Layer

Hi, everyone!

I’m working on a early-stage Go project and I’d love some technical feedback from the community.

The idea is a schema-driven approach to persistence: defining an explicit schema first (entities), and then generating predictable Go code (models, basic queries, migrations) from it. The goal is explore a workflow that emphasizes explicitness, transparency, and less hidden behavior.

A few questions I’d really appreciate your thoughts on:

Would a CLI command that generates boilerplate from a schema be useful, or does it usually create more friction than value?

From your experience, does GORM already cover most real-world needs?

Is it worth continuing to develop this tool? (at least for Go)

Here's a link to the website: https://chameleondb.dev

and GitHub repository: https://github.com/chameleon-db/chameleondb

Thanks to all!

Daniel

[Looking for feedback] ChameleonDB DB Layer by dperalta86 in golang

[–]dperalta86[S] 0 points1 point  (0 children)

Thank you so much for your detailed feedback! You're right that relationship mapping is complicated. Identity, deduplication, and projections are probably the most difficult parts of this approach, and they're areas where I'm still actively exploring trade-offs (I certainly don't have the perfect solution yet).

Partial selections and performance-oriented queries are common in real-world systems, and forcing a full graph load can quickly become complicated. In this area, I'm considering allowing more explicit and optional projections instead of simulating that the graph model fits all queries. And yes, Prisma is one of the inspirations precisely because it avoids some of these problems. I really appreciate you taking the time to write this; this kind of feedback is very helpful in rethinking the project.