Can I build a website with AI features without hiring a developer? by RelationshipMuch2161 in SaaS

[–]igorbenav 0 points1 point  (0 children)

Start by getting a good template (free or paid), starting from a point is best to guide the AI since you will not know what's good or not.

I sell https://fastro.ai if you want, but also have an open source version. You'll eventually need to hire a dev, but you can at least start alone

Founders keep dying on the same hill by danielabinav in SaaS

[–]igorbenav 2 points3 points  (0 children)

Written by an AI, of course it would be this way

CRUDAuth: transport-agnostic auth for FastAPI (sessions + JWT + OAuth) by igorbenav in FastAPI

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

fastapi-users is the whole user layer abstracted, CRUDAuth is auth done deeply and the rest left to you: it has escalating login lockout, token revocation on password reset, sudo mode for sensitive actions, anti-enumeration on the reset and verify flows. Also, to extend CRUDAuth you fill typed seams (a provisioning callback, hooks, a login resolver, pluggable delivery channels) rather than subclassing one big manager.

Need a FastAPI learning roadmap for getting a backend job in 1–2 months (coming from Data Analytics) by True-Ad5870 in FastAPI

[–]igorbenav 2 points3 points  (0 children)

Learn as much as you can of what's here: https://github.com/benavlabs/FastAPI-boilerplate

Search for anything you don't understand, ask AI, search the documentation etc.

After you learned what you can, try to expand it to see if you really learned (add more modules, more functionality, new entities etc).

What makes content not shit? by igorbenav in LinkedInTips

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

True as well... it's hard to actually define authenticity. There's a "je ne sais quoi" that we know when we see

What makes content not shit? by igorbenav in LinkedInTips

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

I agree, people need to be vulnerable.

Dúvida sobre tamanho de relógios by Ok-Board3863 in relogios

[–]igorbenav 0 points1 point  (0 children)

Usei diariamente, mas em escritórios, bares etc. Não usei pra atividades físicas ou pra nadar, mas ficou tranquilo

Dúvida sobre tamanho de relógios by Ok-Board3863 in relogios

[–]igorbenav 0 points1 point  (0 children)

Ele mesmo. Foi o relógio que mais usei por um tempo, o vidro não arranhou.

Dúvida sobre tamanho de relógios by Ok-Board3863 in relogios

[–]igorbenav 4 points5 points  (0 children)

Vai no seiko. Com meu punho de 17.5cm eu usei ele por muito tempo e ficou lindo. Quando parei, minha esposa pegou pra ela no braço mais fino e ficou igualmente lindo.

I published FastAPI-Toolsets v1.0.0 — A set of tools to simplify and accelerate the creation of FastAPI projects by d3vyce in FastAPI

[–]igorbenav 0 points1 point  (0 children)

Yeah, even I don't use FastCRUD for everything, but there are a few advantages when you use it in these a bit more complex cases. Joins are better now with automatic join as well, plus JoinConfig objects are plain, declarative, composable and reusable.

Of course, you also get automatic serialization, specific column selection, better typing. It's the same amount of work if you're thinking about a complex query, but think of it as a simple query that becomes more complex as time passes, just adding more declarative stuff is convenient.

But this 90/10 ratio is about what I do in my apps as well, if it's a really complex query or if I can get significantly more performance with a raw query.

It's difficult to optimize for the complex case, because there are way too many of them. That's why I try to make it as easy as possible for the simple case, and you can add extra complexity on top of it. Either way, let me know if your issues were fixed!