Kir Belevich finished reading Fiasco by Stanisław Lem

Fiasco by Stanisław Lem
Fiasco (Polish: Fiasko) is a science fiction novel by Polish author Stanisław Lem, first published in a German translation in …
This link opens in a pop-up window
Fiasco (Polish: Fiasko) is a science fiction novel by Polish author Stanisław Lem, first published in a German translation in …
Fiasco (Polish: Fiasko) is a science fiction novel by Polish author Stanisław Lem, first published in a German translation in …
he Star Diaries is a series of short stories of the adventures of space traveller Ijon Tichy, of satirical nature, …
A six-man crew crash-lands on Eden, fourth planet from another sun. The men find a strange world that grows ever …
A good introduction book to the topic, especially when it's not like there are many of them around. Very friendly and easy to read overview of different aspects of going the microfrontends route, from purely technical to organizational.
I've started to read the book after I played around with microfrontends already using Webpack Module Federation, which was actually mentioned by the author and in my opinion should definitely be included in the second edition. It's fair to say that it's a game changer not only from a bundle size and shared dependencies perspective. ESBuild implements the same concept too, following this new trend and solving the important tooling puzzle.
I personally would give a "framework-agnostic" topic a bit more pages and draw more parallels with microservices in general. React/Vue/Angular/Svelte microfrontend, encapsulated into a Custom Element with Shadow DOM / Scoped CSS, is almost literally an isolated Docker container analogue. And …
A good introduction book to the topic, especially when it's not like there are many of them around. Very friendly and easy to read overview of different aspects of going the microfrontends route, from purely technical to organizational.
I've started to read the book after I played around with microfrontends already using Webpack Module Federation, which was actually mentioned by the author and in my opinion should definitely be included in the second edition. It's fair to say that it's a game changer not only from a bundle size and shared dependencies perspective. ESBuild implements the same concept too, following this new trend and solving the important tooling puzzle.
I personally would give a "framework-agnostic" topic a bit more pages and draw more parallels with microservices in general. React/Vue/Angular/Svelte microfrontend, encapsulated into a Custom Element with Shadow DOM / Scoped CSS, is almost literally an isolated Docker container analogue. And the upcoming ShadowRealm API will potentially add even more value to this.
This book complemented my own experience here and there by explaining some of the aspects I didn't really think about before.
Favorite quote: "Autonomy inherently comes with the cost of accepting redundancy".
4.5 stars rounded to 5.
When Kris Kelvin arrives at the planet Solaris to study the ocean that covers its surface he is forced to …
If I had to choose one book on the topic, it would be this one.
"Riding the elevator" analogy emphasized through the chapters is simply brilliant - it gives so much understanding even without reading anything at all but walking with this in mind.
Even though first two parts, "Architects" and "Architecture", were my main points to focus on, there is no single page that I wasn't inspired by. "Communication" and "Organizations" parts were in fact much needed and just in time to read for my current project situation. The "Transformation" one is well applicable to any more or less dramatic transformation (supported or even led by architects) happening in large companies, not limited to enterprise mastodons struggling to become "digital natives".
Definitely a career-defining reading for me.
Plutonia (Плутония) is an early science fiction novel by Russian academician Vladimir Obruchev. It was written in 1915 in Kharkov …
Author makes it very clear that the architecture rules are the same whether it's 70s or present day. The role of Software Architect didn't change much when it comes to core principles and ways of thinking.
The book doesn't provide many practical examples but instead relies on a self-reflection on the personal experience, encouraging to mentally revisit some of the projects that reader used to work on. It definitely revealed many insights and helped me to name, structure and defragment those architectural decisions that were eventually right but at the same time made purely intuitive. It also clearly showed those that were applied incorrectly or were just simply unsuitable.
Highly recommended not only to current architects who will find a lot of food for thought but also to aspiring software developers who want to start thinking about architectural questions in advance and drawing diagrams before the actual programming process.