Running the last stage of my project. Designing the frontend of my #ALX_SE foundation stage project. Sincerely @Bhorie_ is a cook 🎉😍💯🙌. Remaining linking all with Api and Backend. @Timemaster 🙌🙌.
#ALX_SE@alx_africa
Quizzed a kid on digital time today. He knew 11PM is 23:00 and the likes. Then he was asked what comes after 00:00. He said it’s none of his concern because he’s usually asleep by then 😂😂😂
Four Ingredients for Exceptional Results:
Quantity: You take lots of shots.
Quality: You take thoughtful shots.
Consistency: Keep shooting for a long time.
Luck: You get a few favourable bounces.
- James Clear
Honestly whatever you do in this life, just win man. Everything people mock you for will seem like genius in retrospect once you win. Don't argue, just win.
Compilers are deterministic. Give them the same code with the same compiler settings, and you'll always receive the same binary. You can take responsibility for your software at the code level.
LLMs, on the other hand, are stochastic. Even if you set the temperature to zero, you're likely to get different responses on the same prompt. Therefore, you need to understand the code it produces if you want to take ownership and responsibility for it.
The universal webhook pattern, no matter the provider:
1. You give the provider (Stripe, GitHub, etc.) a URL
2. An event happens on their system
3. They send an HTTP request to your URL (with payload)
4. Your server responds with 200 OK (just an acknowledgement)
5. Your server handles the next action (DB update, UI notify, etc.)
That's it
Webhooks are APIs where the server calls you