Day 45 of code till internship: ✅ dove deeper in closures ✅ learnt creating custom ApiErrors , ApiResponse and AsyncHandler function ✅ solved 4 question on closure on Leetcode ✅ closure interview questions by @akshaymarch7

Chai aur Backend - 𝗗𝗮𝘆 09 𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴𝘀: - cookie-parser, cors - some middlewares like urlencoded, static, json etc. - asyncHandler method - wrote some standardized ApiErrors, ApiResponses Notes attached👇 @nirudhuuu #chaicode #backend #webdev #cohort

ApiErrors, AsyncHandlers, ApiResponses. Feels about 80% clearer than yesterday on this topic, and that’s a win. Slow understanding is still understanding.

#Day16 ( Backend ) - Started a project from Hitesh Sir's course ( Name - VidTube ) - Connected Database - Done AsyncHandler, ApiResponse & ApiErrors

Day 16 of #100DaysOfCode - Learned about reversing a LL and slow & fast pointer in LL @rohit_negi9 - Started with the mega project from @ChaiCodeHQ and did the basic setup, apierrors - Completed a lec on LCM in apti #100daysofcoding #code #DSA

How are you dealing with API Errors in your API designs? Check out our blog series on 𝘿𝙤𝙞𝙣𝙜 𝘼𝙋𝙄 𝙀𝙧𝙧𝙤𝙧𝙨 𝙒𝙚𝙡𝙡 Part I: swagger.io/blog/problem-deta… #apis #apidesign #problemdetails #apierrors

Struggling with API errors? Check out this 2-part blog series on effective error handling in HTTP APIs, leveraging RFC 9457 (formerly RFC 7807). 🚧🔧 #apis #apidesign #problemdetails #apierrors Part I: swagger.io/blog/problem-deta… Part II: swagger.io/blog/problem-deta…

The LLM/ChatGPT community on Twitter seems oddly silent about an important issue. The newly released OpenAI GPT-4-0613 model, set to become the default in less than a week, has a significant problem with uptime. It frequently experiences 500 type APIErrors, rendering it virtually unusable for development (check screenshot). Furthermore, there have been notable changes in the model's behaviour. While the previous versions, like 0314, had a balanced approach to prompts, the focus has shifted heavily towards system prompts and function descriptions. This means that without restructuring prompts, the performance deteriorates rapidly. The requirement for users to transition to the newer model within just three months, without any alternative, coupled with the instability of the endpoint, raises concerns about OpenAI's dedication to developers. Several discussions on the OpenAI Discord platform support these observations and frustrations: discord.com/channels/9745198… discord.com/channels/9745198… Very sorry if this sounds like a rant, but any help is appreciated 🙏 @OpenAI @npew @BorisMPower @OfficialLoganK

Error en la API: El endpoint "users/add" debería ser "users/create". Utilizar el verbo HTTP correcto es clave para mantener la consistencia en la nomenclatura de los endpoints. #APIErrors

Very happy and grateful to be writing for @checklyHQ . Will share the link when complete #apierrors