giseldo/deep-se
Viewer
•
Updated
•
23.3k
•
11
•
1
Giseldo Neo PRO
giseldo
AI & ML interests
GPT, PLN, ML
Recent Activity
liked
a dataset
17 days ago
giseldo/deep-se
updated
a dataset
17 days ago
giseldo/deep-se
published
a dataset
17 days ago
giseldo/deep-se
Organizations
None yet
giseldo's activity
liked
a
dataset
17 days ago
updated
a
dataset
17 days ago
published
a
dataset
17 days ago
liked
a
Space
18 days ago
liked
a
model
19 days ago
updated
a
Space
20 days ago
published
a
Space
20 days ago
updated
a
Space
21 days ago
published
a
Space
21 days ago
updated
a
Space
25 days ago
published
a
Space
25 days ago
updated
a
Space
25 days ago
published
a
Space
25 days ago
updated
a
Space
26 days ago
published
a
Space
26 days ago
updated
a
Space
26 days ago
published
a
Space
26 days ago
reacted to
hesamation's
post with ❤️
28 days ago
Post
8306
Google published a 69-page whitepaper on Prompt Engineering and its best practices, a must-read if you are using LLMs in production:
> zero-shot, one-shot, few-shot
> system prompting
> chain-of-thought (CoT)
> ReAct
LINK: https://www.kaggle.com/whitepaper-prompt-engineering
> code prompting
> best practices
> zero-shot, one-shot, few-shot
> system prompting
> chain-of-thought (CoT)
> ReAct
LINK: https://www.kaggle.com/whitepaper-prompt-engineering
> code prompting
> best practices
published
a
Space
about 1 month ago
reacted to
abidlabs's
post with ❤️
about 1 month ago
Post
3782
JOURNEY TO 1 MILLION DEVELOPERS
5 years ago, we launched Gradio as a simple Python library to let researchers at Stanford easily demo computer vision models with a web interface.
Today, Gradio is used by >1 million developers each month to build and share AI web apps. This includes some of the most popular open-source projects of all time, like Automatic1111, Fooocus, Oobabooga’s Text WebUI, Dall-E Mini, and LLaMA-Factory.
How did we get here? How did Gradio keep growing in the very crowded field of open-source Python libraries? I get this question a lot from folks who are building their own open-source libraries. This post distills some of the lessons that I have learned over the past few years:
1. Invest in good primitives, not high-level abstractions
2. Embed virality directly into your library
3. Focus on a (growing) niche
4. Your only roadmap should be rapid iteration
5. Maximize ways users can consume your library's outputs
1. Invest in good primitives, not high-level abstractions
When we first launched Gradio, we offered only one high-level class (gr.Interface), which created a complete web app from a single Python function. We quickly realized that developers wanted to create other kinds of apps (e.g. multi-step workflows, chatbots, streaming applications), but as we started listing out the apps users wanted to build, we realized what we needed to do:
Read the rest here: https://x.com/abidlabs/status/1907886
5 years ago, we launched Gradio as a simple Python library to let researchers at Stanford easily demo computer vision models with a web interface.
Today, Gradio is used by >1 million developers each month to build and share AI web apps. This includes some of the most popular open-source projects of all time, like Automatic1111, Fooocus, Oobabooga’s Text WebUI, Dall-E Mini, and LLaMA-Factory.
How did we get here? How did Gradio keep growing in the very crowded field of open-source Python libraries? I get this question a lot from folks who are building their own open-source libraries. This post distills some of the lessons that I have learned over the past few years:
1. Invest in good primitives, not high-level abstractions
2. Embed virality directly into your library
3. Focus on a (growing) niche
4. Your only roadmap should be rapid iteration
5. Maximize ways users can consume your library's outputs
1. Invest in good primitives, not high-level abstractions
When we first launched Gradio, we offered only one high-level class (gr.Interface), which created a complete web app from a single Python function. We quickly realized that developers wanted to create other kinds of apps (e.g. multi-step workflows, chatbots, streaming applications), but as we started listing out the apps users wanted to build, we realized what we needed to do:
Read the rest here: https://x.com/abidlabs/status/1907886