brunaxLorax's comments

brunaxLorax | 1 month ago | on: Coding assistants are slow. So we multitask

I agree. However as you said, you can consider code agents like human contributors. My feedback is that an army of Claude Code instances with a strict CLAUDE.md file is more rigorous than a human team.

brunaxLorax | 1 month ago | on: Coding assistants are slow. So we multitask

I recently came across https://claudecode.run/ (not affiliated). There are currently several similar products that help that multi-instance Claude Code layout

brunaxLorax | 1 month ago | on: Coding assistants are slow. So we multitask

How quickly? There is no limit to that. If I can do my day of work in few hours I would be glad to take the afternoon off or to go twice as fast (importunately that's more the second!)

brunaxLorax | 1 month ago | on: Coding assistants are slow. So we multitask

With git worktrees you can you have your agents working on literally different folders so they don't step up on each other.

brunaxLorax | 11 months ago | on: Manifest: A 1-file micro-back end

Fixed ! thank you

brunaxLorax | 11 months ago | on: Manifest: A 1-file micro-back end

Hello, Manifest dev here, most backend-as-a-services rely on an UI and it's harder for AIs. In comparison, Manifest high-level DSL is really understandable by gen AIs. It's also very easy to validate in comparison to bootstrap frameworks that come with a lot of files.

But you are right we should explain it somewhere !

brunaxLorax | 11 months ago | on: Manifest: A 1-file micro-back end

correct :)

brunaxLorax | 11 months ago | on: Manifest: A 1-file micro-back end

Hello ! Manifest dev here, they are on the way ! There is a DB sync at the moment that does the job but we are going to implement the migrations soon :)

brunaxLorax | 1 year ago | on: Ask HN: AWS Lambda Credible Alternatives?

It will be an express based REST API that connects to an external Database.

The API will have to expose endpoints and do CRUD operations for the most part.

brunaxLorax | 1 year ago | on: Show HN: I built a backend so simple that it fits in a YAML file

(dev here) Backend-as-a-service products are very popular right now because they remove or simplify a lot of the backend complexity. It comes super handy for some projects.

Yes, the DB is SQLite. We chose it among others as it is file based and thus you get get up and running in seconds.

Authentication and authorization are key features, I agree. They were not integrated in the POC but they will come very soon. There actually is auth for the admin panel, I just need to standardize it for other entities.

I got it for the CMS use case, Manifest's aim is not to be a competitor of large frameworks that gives you the control of everything. We rather think that it will fit for another typology of projects. You can use it as a headless CMS, but there already is products like Strapi or Directus that get the job done. I am thinking more about projects with more "app" logic, but the next step is adding custom logic to it.

brunaxLorax | 1 year ago | on: Show HN: I built a backend so simple that it fits in a YAML file

Migrations are a tricky point I agree. In your system, do you keep your original model files as they were at the beginning or do you change them too ?

brunaxLorax | 1 year ago | on: Show HN: I built a backend so simple that it fits in a YAML file

I am thinking about having some hooks for the custom logic. I like the entity listeners/subscribers from typeORM: https://orkhan.gitbook.io/typeorm/docs/listeners-and-subscri... but I the end I guess we would probably need some functions stored somewhere. Not sure how to implement that though

brunaxLorax | 1 year ago | on: Show HN: I built a backend so simple that it fits in a YAML file

Yes there is a lot of similarities in the foundation and the syntax. The end goal is different though as Manifest aims to be a production-ready product: it already comes with the admin panel and will soon include features like authentication, authorization and so on.

brunaxLorax | 1 year ago | on: Show HN: I built a backend so simple that it fits in a YAML file

Mmmm... It comes from ORMs in general I guess. I appreciate the effort of some ORMs to get a nice syntax, making it feel like natural language. I guess Laravel Eloquent was my first crush in my PHP days. Then modern ORMs like TypeORM and Prisma do an excellent job IMO.

I also like the idea of transposing ORM-style queries in the browser to abstract the whole API response-request part.

brunaxLorax | 1 year ago | on: Show HN: I built a backend so simple that it fits in a YAML file

This is a key question for real-life use cases. YAML is a markup language so you cannot program and add logic in it.

I think about having a set of hooks that trigger the code logic hosted somewhere. Language-agnostic / serverless, that kind of stuff maybe... Any ideas ?

brunaxLorax | 1 year ago | on: Show HN: I built a backend so simple that it fits in a YAML file

Looks really nice !

brunaxLorax | 1 year ago | on: Show HN: I built a backend so simple that it fits in a YAML file

Stay tuned :)

brunaxLorax | 1 year ago | on: Show HN: I built a backend so simple that it fits in a YAML file

Hi perrygeo, Manifest dev here, I totally agree with you: quick starts can be harmful in the middle/long term so most of the times I would probably accept to invest more time in the beginning building something flexible.

However, you are talking here as a senior/expert developer - as you were already coding in 2010 ;) - but junior devs OR frontend devs may not be able to create that Django+DB+API app so easily. That is an important point to consider.

brunaxLorax | 1 year ago | on: Show HN: I built a backend so simple that it fits in a YAML file

Oops... Thanks !

brunaxLorax | 1 year ago | on: Show HN: I built a backend so simple that it fits in a YAML file

Thank you !

I love pocketbase it is a really enjoyable product, very neat. Manifest can be seen as a different approach, using code rather than UI.

Yes the "hook part" is tricky to consider as I am scared that I will have to trade-off some simplicity in order to cover more features/use cases.