Hi guys, Please set the speed to 0.75x if you feel it's fast. I realized later in the next day when I watched 🥲 Thanks to "@Think_First12" for bringing this up as an end user 🙌
Content is awesome but I have a basic issue that is your voice speed. To listen you probably I had to set video speed at 0.75X. so if you had uploaded the video at 1.5 or 2X speed then please don't do that.
Thank you for the feedback, yes I did at 1.5x 🥲 My bad, realized next day when I watched with fresh context. Now it’s confirmed with your feedback that it’s speed overly adjusted, noted and will be improved from now on 🙌🏻
Good point, usually once an api end point is production ready, as per the semantic versioning lets say the frequency of major version change would happen once in 5 years as an example and this interval purely depends on the application growth, volume and re-architecture requirements. If an end point in a very short span keep changing then either its not production ready in the first place and we can stick same version until it goes live or bad design in the first place 😉
Good question! Simplifying API naming conventions boosts consistency and developer productivity, but security wouldn't be compromised. Security is a separate layer that must be strictly enforced like authentication, authorization, rate limiting, and data validation are crucial to protect APIs from risks - irrespective of how simple or complex the naming conventions are. In summary, even with self-explanatory naming conventions I don't see of a case where it exposes any security risks. If you can share an example, I can definitely explain in accordance with it. Thanks for dropping a comment - appreciate the thoughtful question! 😊