@mariuszgil@boilingfrogspl That's why I consider @boilingfrogspl the most valuable IT conference at least in Poland. Being there is like battery charging for any IT worker who want's to learn more than code.
I was considering to replace my Prettier + Eslint setup with @biomejs but I am that oldschool frontend dev who writes CSS ;) and there is no support for CSS and HTML yet. But Biome is still very interesting project.
@mariuszgil@cytrowski@tomasz_ducin Czy to jeszcze BSD !?
Jako ten gupi frontend dziekuje, bo mega konkretna wiedza niezaleznie od skali w ktorej sie pracuje.
@fireship_dev came with super useful content once again. This time it's all about React compiler and other shiny stuff in incoming v19 https://t.co/SLaOnrY4HT
https://t.co/EyfshqsT5C looks really awesome for building cross-browser web extensions.
◆ Target Chrome, Firefox, Edge and Safari
◆ Fast Dev Mode with Hot Reloading
◆ TypeScript by default
◆ Automate publishing
I just did 8 kyu kata at Codewars and I learned that about +x and -x operators :) My conclusion is that even trivial challenges can teach something interesting. Dopamine level boosted.
🔥 #Architecture#Focus 🔥
Why should your system be DESIGNED FOR FAILURE? 🤕
DESIGN FOR FAILURE is:
💥 an architectural approach 🏗️
💥 where errors and unavailability are system’s first-class citizens 👊
(failure is as important as happy path)
💥 we plan for quick recoveries 🏎️ rather than error-free systems 💥
💥 so that, if an outage happens, we’re not doomed ☠️
wait, isn't try..catch enough? 😏
👎 certainly not...
WHY?
🧨 everything would eventually fail at some point
🧨 what would be business and technical CONSEQUENCES?
🧨 if one part of the system fails, would the ENTIRE SYSTEM GO GOWN 🥶 as well?
🧨 failures can COST lots of 💸💸💸
🧨 your business will love you 😘 really 😘😘😘
HOW?
🤧 test errors
🤒 test failures
🤕 test outages
🥴 test, test, test...
no, but seriously, HOW?
📝introduce RETRIES, especially with EXPONENTIAL BACKOFF (coming up!)
📝consider adding CIRCUIT BREAKERS (coming up!)
📝implement SYSTEM OBSERVABILITY (coming up!)
📝provide CORRELATION IDs/TOKENs (coming up!)
📝limit TEMPORAL COUPLING (coming up!)
📝identify SINGLE POINTs OF FAILURES (coming up!)
📝test failure scenarios via CHAOS ENGINEERING (coming up!)
WHAT to test?
💣 how does the UI handle network errors?
💣 is the user properly informed if a certain service goes down?
💣 does the user lose their local state?
💣 how does the UI recover?
💣 if anything goes wrong, do developers know IMMEDIATELY? (observability)
💣💣💣 are above tests automated?