Frontend System Design Guide: devtools.tech/fsd-guide Github Repo: github.com/Devtools-Tech-Team/ai-in-frontend Send your social post our guide to team.devtools@gmail.com
It is good to use Tailwind but first we should have a good understanding of CSS. Same logic applies here. We can use OpenAI or some other provider's APIs but it is good to know how to run your own model. Also, not all companies would be willing to send their data to some third party API over which they have no control.
@@DevtoolsTech, okay, I got it. So will the model that we use be hosted along with our main express.js server (I mean the main backend), or will it be hosted on a different instance? Also, which will be cheaper, using Open AI APIs or hosting our own model?
It requires a powerful server so it needs to be hosted on specialised machines running GPU(s) for good performance. APIs are pretty cheap but can add up quickly if your app takes off. I would say learn how to run a model to start with then use managed APIs as you grow.
Tailwind is good. No doubt about that. We don't write css for every little thing. Teams create DS system that covers a good chunk of the UI so it is a matter of plug and play. For colors, typography, spacing, borders, and others we mostly have tokens or mixins that are imported so very few things we need to write manually. With Tailwind, your content over the wire increases a lot and sometimes it gets overwhelming to read the code. There are pros and cons of both.
Frontend System Design Guide: devtools.tech/fsd-guide
Github Repo: github.com/Devtools-Tech-Team/ai-in-frontend
Send your social post our guide to team.devtools@gmail.com
Searching here and there to integrate ai power in front end skills. Then I got this video, such a missing piece for me. Thank you so much bhaiya
Glad to hear that! 🙌🏼
great content
Thank you! 🙌🏼
Thanks bro❤
Do share it with your friends and colleagues! 🙌🏼
Nice explanation. I just had a query: Why are we using the model instead of the direct OPEN AI API?
It is good to use Tailwind but first we should have a good understanding of CSS. Same logic applies here. We can use OpenAI or some other provider's APIs but it is good to know how to run your own model. Also, not all companies would be willing to send their data to some third party API over which they have no control.
@@DevtoolsTech, okay, I got it. So will the model that we use be hosted along with our main express.js server (I mean the main backend), or will it be hosted on a different instance? Also, which will be cheaper, using Open AI APIs or hosting our own model?
It requires a powerful server so it needs to be hosted on specialised machines running GPU(s) for good performance.
APIs are pretty cheap but can add up quickly if your app takes off. I would say learn how to run a model to start with then use managed APIs as you grow.
4:20 why w-6/12 not w-1/2
No reason. Not very used to Tailwind. I used whatever came to my mind first.
@DevtoolsTech then what you prefer for frontend styling
Depends on the case. Colocated sass files that are bundled up route based and act as per module/file styling.
@@DevtoolsTech it's bothersome to write sass files, I don't have much experience in frontend as backend is my field, still I prefer css and tailwind
Tailwind is good. No doubt about that. We don't write css for every little thing. Teams create DS system that covers a good chunk of the UI so it is a matter of plug and play. For colors, typography, spacing, borders, and others we mostly have tokens or mixins that are imported so very few things we need to write manually.
With Tailwind, your content over the wire increases a lot and sometimes it gets overwhelming to read the code. There are pros and cons of both.
🙏