Fausto Portugal

Three years ago (Dec 27, 2021), @Sonny Sangha and @Jay Rathod embarked on a journey to create something extraordinary, and today, we celebrate Papafam's incredible milestone. Anyone who have listened to the podcast knows the ideas started 25 of December I recommend you listen yourself. I want to express my deepest gratitude to @Sonny Sangha and @Jay Rathod for being such inspiring mentors, not only in the world of coding but also in life. Their passion, resilience, and generosity have created a community where aspiring developers like me can learn, grow, and thrive. Principles to Learn from Sonny & Jay as a Developer: 1. Learn How to Learn: Sonny emphasized, "You need to learn how to learn before starting coding"(Podcast Ep. 1, 11:04). Develop your unique learning style, whether through hands-on practice or reverse engineering. 2. Teach to Master: "Your skills will improve if you teach someone"(Podcast Ep. 1, 22:18). Teaching someone at a lower skill level not only strengthens your understanding but also builds confidence. 3. Embrace Self-Learning: Sonny and Jay are self-taught developers who show that perseverance and curiosity can lead to mastery. Sonny said, "You could go from zero to amazing developer with the free stuff on the channel" (Ep. 8, 12:12). 4. Enjoy the Process: "You have to enjoy the process; otherwise, you will quit" (Podcast Ep. 1, 38:20). Coding is a journey of constant growth, not just a destination. 5. Overcome Challenges: Sonny candidly shared his struggles with imposter syndrome and debugging but stressed the importance of perseverance. He noted, "Whatever you do, always have the idea to improve" (Podcast Ep. 5, 47:50). 6. Mentorship is Key: "You need a mentor who has done what you want to do and can save you from errors" (Podcast Ep. 6, 47:01). Both Sonny and Jay credit their growth to learning from others and giving back through mentorship.

New comment Jan 5

Celebrating 3 Years of Papafam - Grateful to Sonny & Jay 🎉

Fausto Portugal

2 likes • Dec '24

What a great summary Raymond, I also feel happy to belong to this great community, I have learned more than I expected in the last 6 months.

Fausto Portugal

Dec '24 •

General discussion

Let’s build an AI Help Bot with NEXT.JS 14! | Add chatbotsByUser

Following the tutorial at minute 2:46:20, chatbotsByUser is added in ...view-chatbots/page.tsx In index.graphql we must add: chatbotsByUser(clerk_user_id: String!): [Chatbots] @dbquery( type: "postgresql" schema: "public" query: """ SELECT "clerk_user_id", "created_at", "id", "name" FROM "chatbots" WHERE "clerk_user_id" = $1 """ configuration: "postgresql_config" ) followed by updating the schema on the server with the stepzen deploy command.

Clay Huntly

Jul '24 •

Pair Programming

Please Help

Need help figuring this out. Assistly youtube project Mutation for the ADD_CHARACTERISTIC is not populating the db with the mutation all the code is correct I think I'm missing something here? JS: const handleAddCharacteristic = async (content: string) => { try { const promise = addCharacteristic({ variables: { chatbotId: Number(id), content, }, }); toast.promise(promise, { loading: "Adding...", success: "Information added", error: "Failed to add Information", }) } catch (error) { console.error("Failed to add characteristic", error) } } Mutation: export const ADD_CHARACTERISTIC = gql` mutation AddCharacteristic($chatbotId: Int!, $content: String!) { insertChatbot_characteristics(chatbot_id: $chatbotId, content: $content) { id content created_at } } `; Am I missing something here?

New comment Dec '24

Fausto Portugal

0 likes • Dec '24

I have the same problem. The message that appears is: "Failed to add Information"

Fausto Portugal

1 like • Dec '24

Add the following code and that's it. page.tsx const handleAddCharacteristic = async (content: string) => { try { const promise = addCharacteristic({ variables: { chatbotId: Number(id), content, created_at: new Date().toISOString(), }, }); toast.promise(promise, { loading: "Adding...", success: "Information added", error: "Failed to add Information", }); } catch (err) { console.error("Failed to add characteristic:", err); } }; mutations.ts export const ADD_CHARACTERISTIC = gql` mutation AddCharacteristic($chatbotId: Int!, $content: String!, $created_at: DateTime!) { insertChatbot_characteristics(chatbot_id: $chatbotId, content: $content, created_at: $created_at) { id content created_at # Add other fields you might want to return after adding } } `;

Maison Chetty

Oct '24 •

General discussion

query error

I am currently trying to do Sonny old live streams(Let’s build an AI Help Bot with NEXT.JS 14! (Neon PostgreSQL, Clerk, AI Agent, OpenAI, IBM)) and i have gotten stuck with an issue, I keep getting this error: Error: Server response was missing for query 'CreateChatbot'. this is my code:

New comment Dec '24

Fausto Portugal

0 likes • Dec '24

Copy the tutorial he made @swift-e-9509 Following the tutorial while implementating, I encountered the same snag at the 1:48:35; the "ApololioError." Despite closely following the tutorial steps, this error was persistent. After some digging, I realized the cause was a missing piece in the GraphQL mutation setup: the created_at parameter. Here’s a quick fix for those who might be facing the same issue: 1. Update Your GraphQL Mutation: Ensure your mutation includes the created_at field to track when each chatbot is created. Amend your GraphQL mutation in //graphql/mutations/mutations.ts like so: import { gql } from "@apollo/client"; export const CREATE_CHATBOT = gql` mutation CreateChatbot($clerk_user_id: String!, $name: String!, $created_at: DateTime!) { insertChatbots(clerk_user_id: $clerk_user_id, name: $name, created_at: $created_at) { id name } } `; 2. Correctly Pass the Date in Your Frontend: In your React component where the mutation is called (e.g., //app/(admin)/create-chatbot/page.tsx), ensure you pass the current date and time as follows: const [createChatbot, { data, loading, error }] = useMutation( CREATE_CHATBOT, { variables: { clerk_user_id: user?.id, name: name, created_at: new Date().toISOString(), // Dynamically set current date and time }, } ); With these tweaks, the "ApololioError" was resolved for me. I hope this solution helps anyone stuck at the same spot—happy coding!😎

1-10 of 14

Level 2

6points to level up

Fausto Portugal

@fausto-portugal-4312

Always learn

Active 4m ago

Joined Jun 16, 2024

México