Adam retweetledi
Adam
995 posts

Adam
@fadehelix
🇵🇱 | 🇬🇧 Senior Frontend Developer passionate about transforming business needs into working software | PSM & PAL Certified
Poland Katılım Aralık 2009
280 Takip Edilen138 Takipçiler

Sometimes you can find such gems even on LinkedIn :) joshcollinsworth.com/blog/antiquate…
English
Adam retweetledi

@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.
English

If you are wondering if @boilingfrogspl Software Craftsmanship conference is for you next year 👇
Hubert Stemplewski ⚛️💻@hstemplewski
A few things after @boilingfrogspl. 1. It change my way of thinking about software architecture. 2. It change my way of thinking about work-life balance. 3. It change my way of thinking about my career. Great conference 🙌🏼
English

@mariuszgil @cytrowski @tomasz_ducin Czy to jeszcze BSD !?
Jako ten gupi frontend dziekuje, bo mega konkretna wiedza niezaleznie od skali w ktorej sie pracuje.
Polski

Nowy rozdział w podkaście trzeba zacząć mocno 🔥 Dziś zapraszam na rozmowę o architekturze makro front-endu Atlassiana, monorepo z ponad 1k pull-requestów dziennie i pracy przy takim systemie. Gościem specjalnym jest dziś Bartosz @cytrowski, prowadzi @tomasz_ducin 🔥

Polski
Adam retweetledi

@fireship_dev came with super useful content once again. This time it's all about React compiler and other shiny stuff in incoming v19 youtube.com/watch?v=4k6Xgj…

YouTube
English

"React Trends in 2024" by @rwieruch #ReactJS robinwieruch.de/react-trends/ is a perfect thing to read during the morning coffee :)
English
Adam retweetledi

wxt.dev 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
English

Adam retweetledi

🔥 #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?

English










