Developer Life.
Debugging code and reading it 50 times without being able to figure out what's wrong.
Asking a peer to look, and with the second set of eyes, I'm able to figure out the bug almost immediately.
Why does having others look at your code, let you see it better?!
نحن متحمسون للغاية لرؤية أعداد طلبات الترشيح التي تلقيناها لجائزة ألف للتعليم للتميز في التعلم عن بُعد
يرجى الملاحظة أنه تم تمديد الفترة للتسجيل وتحميل الأدلة إلى تاريخ
22 يونيو 2020
للتسجيل يرجى التواصل مع إدارة المدرسة.
للتفاصيل، يرجى زيارة الموقع:
https://t.co/zCDcF4QyZO
@ExplorerAadi Of course with Desktop layout First, (either you have mockups ready or not) it's easier to define each section position & styles or CSS classes in wide screen then when the screen becomes smaller you'll start resizing, hiding,or reordering... etc sections to fit into that screen.
(thread)
what if we flipped hiring on its end... what if we made "candidate's desired work listing" sites instead of "job listing" sites, and if companies had to apply to the candidate and be screened to see if their job makes the cut?
📣 Just published: React Router v6 experimental
- Adds support for data fetching with suspense via `timeoutMs` prop 🙌
- It's experimental. This means it follows the same semantics as React's own experimental release channel 👀
Full release notes 👇
https://t.co/HNLkaDSti8
@getify Yes, you are right at that case I used to return any code from 4xx like 408 request timeout, with message: database connection dropped...
But not 500 which refer to unexpected state in terms of the application itself is not available to consumers
@getify Logically when you receive 500, that means the request went inside unknown issue not included in the code that handles edge cases and that's because of either it's really unexpected/predictable case or some edge case missed by the developer