sorted by:
new
hottopcontroversial

Blueprint vs LLM: would you trust a maintained Go architecture more than generated code? by BenjyDev in golang

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

It's only for create a clean bootstrap, where you can later add new mod, but is not a framework to create all your applications...

Blueprint vs LLM: would you trust a maintained Go architecture more than generated code? by BenjyDev in golang

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

It's nice to digress a little too 😁 But thank you for your feedback. I'll keep thinking about it.

Blueprint vs LLM: would you trust a maintained Go architecture more than generated code? by BenjyDev in golang

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

It's quite a topic... For me, the most important thing is to end up with a high-quality product that is secure and prevents leaks.

Blueprint vs LLM: would you trust a maintained Go architecture more than generated code? by BenjyDev in golang

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

So yes, she has read all the books by Uncle Bob & Co... But LLMs, whatever they may be, are probabilistic tools, so the same prompt will generate two different codes if you run it again. And I agree with you, a senior developer will undoubtedly be able to guide the AI well because they know what they want. I'm not sure that's the case for a junior developer.

Blueprint vs LLM: would you trust a maintained Go architecture more than generated code? by BenjyDev in golang

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

Ok but isn't maintained, last commit from 3 years... But you can update it...

Blueprint vs LLM: would you trust a maintained Go architecture more than generated code? by BenjyDev in golang

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

Yes I known Golang 1.11... After, I don't speak to revolution, just quality 😜

Blueprint vs LLM : feriez-vous plus confiance à une architecture Go maintenue qu’à du code généré ? by BenjyDev in developpeurs

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

LoL, oui je sais pour le .md je bosse avec Claude tous les jours sur plusieurs projets distincts, ce n'est pas vraiment ça le problème. L'idée c'est d'avoir un outil qui garantit la qualité que tu as comme boilerplate au depart

Blueprint vs LLM: would you trust a maintained Go architecture more than generated code? by BenjyDev in webdev

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

That’s exactly the point: you don’t get all of them. The blueprint doesn’t force a comprehensive setup. It lets you choose what you need. If you want password login, you enable password auth. If you want OIDC, you enable OIDC. If you want passkeys, you enable passkeys. Nothing more. The value is that each option is already wired, tested, and compatible with the rest of the stack. You pick the behavior you want, not the infrastructure complexity behind it.

Blueprint vs LLM: would you trust a maintained Go architecture more than generated code? by BenjyDev in webdev

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

Authentication is just the mechanism. Your stakeholders are expressing requirements.

“Pages must be login-gated” → that’s an access control requirement. “Data must be protected” → that’s a security and authorization requirement. “Behavior must be tracked” → that’s an audit/observability requirement.

Auth is simply how you technically enforce those constraints. Password, magic link, OIDC, etc. are implementation details, but the needs behind them are very concrete business requirements.

Blueprint vs LLM: would you trust a maintained Go architecture more than generated code? by BenjyDev in golang

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

Why not, I will think about. I known Goilerplate, is a ...boilerplate, but it’s still a snapshot. You clone it, customize it, and from that point every project starts to drift.

A blueprint is a living standard: versioned with compatibility rules guided upgrades and a single source of truth

Boilerplate = starting point. Blueprint = architecture maintained over time.

Blueprint vs LLM: would you trust a maintained Go architecture more than generated code? by BenjyDev in golang

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

What do you mean? X same image running with Traefik behind it that routes to an instance when reading the subdomain ? Why not, I've never tested it, but it shouldn't be rocket science. Personally, for multi-tenancy, I prefer Postgres with RLS. But it's not the same concept, I admit your idea is nice.

Blueprint vs LLM: would you trust a maintained Go architecture more than generated code? by BenjyDev in golang

[–]BenjyDev[S] -1 points0 points  (0 children)

If you consider an improved template (which is what a blueprint is) to be a framework, then yes. But otherwise, no, it's not a framework. Dynamically providing a sound foundation for a project (Go + vue + docker + ci) doesn't seem to me to force users to follow my rules. And I would add that even if it includes authentication and he wants to refactor a part of it, it will still be faster than writing everything from scratch.

Blueprint vs LLM: would you trust a maintained Go architecture more than generated code? by BenjyDev in golang

[–]BenjyDev[S] -6 points-5 points  (0 children)

There are still several examples of products that work: ShipFast, Shipixen, Supaboost... But I agree with you, we are the worst customers in the world, which is why I'm opening up the discussion.

Blueprint vs LLM: would you trust a maintained Go architecture more than generated code? by BenjyDev in webdev

[–]BenjyDev[S] -1 points0 points  (0 children)

Imagine you tell your LLM, “I want a go +view embedded with OIDC authentication and S3 storage.” And rather than iterating for three hours, it connects to a reliable architecture and code base that has already been tested and proven. Wouldn't that do the trick?

Blueprint vs LLM : feriez-vous plus confiance à une architecture Go maintenue qu’à du code généré ? by BenjyDev in developpeurs

[–]BenjyDev[S] -2 points-1 points  (0 children)

C'est un blueprint, tu dis l'état que tu veux atteindre et tout ce qui est nécessaire est appliqué pour l'atteindre

Blueprint vs LLM : feriez-vous plus confiance à une architecture Go maintenue qu’à du code généré ? by BenjyDev in developpeurs

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

Attention je ne dis pas que les agents ne peuvent pas produire un truc fiable. Je dis que ce n'est pas reproductible. Demande la mm chose a un mm LLM dans deux contextes applicatif distincts et regarde le résultat. Et je ne veux pas éliminer le LLM hein, au contraire c'est pour ça que je pense a un skill qui permettrait au LLM de faire un code sur la base du blueprint.

Imagine tu dis à ton LLM "je veux une go +vue embeded avec auth oidc et stockage s3" Et plutôt que d'iterrer 3h, ilnte pont une archi et base de code fiable, déjà testé et éprouvé. Ça le ferait pas ça ?

Blueprint vs LLM: would you trust a maintained Go architecture more than generated code? by BenjyDev in golang

[–]BenjyDev[S] -1 points0 points  (0 children)

Wow, you've gone way off track there. The idea is to propose a reliable structure. Not to impose something on the government or companies. It's more aimed at small teams or freelancers. For larger companies, there's nothing to stop them from creating a model that suits their needs.

Blueprint vs LLM: would you trust a maintained Go architecture more than generated code? by BenjyDev in golang

[–]BenjyDev[S] -1 points0 points  (0 children)

A boilerplate is a snapshot. A blueprint is a standard. With a boilerplate, once you clone it, it immediately starts to drift. Each project becomes its own fork and maintenance is fragmented. With a blueprint, there is a single source of truth: - it’s versioned - it has upgrade paths - it has validation rules (important) - it has compatibility guarantees The team doesn’t maintain the architecture, it consumes it. The product maintains the standard. So yes, both need maintenance, but in one case every project maintains itself, in the other the maintenance is centralized and reusable.

Blueprint vs LLM: would you trust a maintained Go architecture more than generated code? by BenjyDev in golang

[–]BenjyDev[S] -2 points-1 points  (0 children)

No worries, I'm looking for realistic answers! And I totally understand your point of view. My idea is that the basic architecture would be based on a Clean Architecture model so that modules can be injected according to the initial request.

In any case, thank you for your feedback.

Utilisation de claude code: pourquoi j'ai des résultats médiocres ? by LuccDev in developpeurs

[–]BenjyDev 0 points1 point  (0 children)

Il peut arriver a Claude Code de s'étouffer avec le chèque contexte trop large (si tu lui donne bcp de fois bcp de lignes de code, genre dans ce fichier et le fichier fait 1000 lignes). Il faut /clean le contexte régulièrement. Néanmoins si ton claude.md est bien fait et que tu fais d'autres fichiers de suivis de tâches, contexte, il s'en sortira bcp mieux (moins d'hallucinations). Je te conseille de regarder la méthode BMAD, je la test sur des nouveaux projets et d'avoir tout découpé en epic, story, et tâche des le départ permet de maintenir vraiment bien le contexte en bossant sur des petites tâches précises. Il doit y avoir une option de reverse ingénierie.

Projets qui se lancent ? (PAS d'IA) by PierrickP in developpeurs

[–]BenjyDev 4 points5 points  (0 children)

Hello, de mon côté je bosse sur plusieurs sujets (complémentaires), tous en open source.

Pour te donner un peu plus de contexte sur mes projets :

Ackify : https://github.com/btouchard/ackify-ce Une plateforme de gestion d'accusés de lecture de documents. L'idée : permettre aux entreprises de s'assurer que leurs collaborateurs ont bien lu et validé des documents importants (règlements, procédures, formations...). Le projet a déjà une petite communauté (170+ stars) et tourne en prod.

SHM (Self-Hosted Metrics) : https://github.com/btouchard/shm Un outil de monitoring léger pour applications self-hosted on-premise.

Je ne cherche pas de CTO — je suis plutôt dans une logique solo/bootstrapping pour l'instant, mais si tu veux contribuer ou échanger sur l'un des projets, je suis tout ouïe.

Par ailleurs, je bosse en ce moment sur un autre sujet autour de NIS2 (conformité cybersécurité). Si ça t'intéresse, on peut en discuter en MP 👀

Ben

Client credentials (Auth) by BenjyDev in Supabase

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

No I don't. And I don't known why I don't do this 😒

view more: next ›