home.social

#designpattern — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #designpattern, aggregated by home.social.

fetched live
  1. The Strangler Fig pattern gradually replaces legacy systems. Route new features to new code, legacy features to old code. Gradually migrate until the old system withers away. Safe modernization. #DesignPattern #SoftwareEngineering

  2. The Strangler Fig pattern gradually replaces legacy systems. Route new features to new code, legacy features to old code. Gradually migrate until the old system withers away. Safe modernization. #DesignPattern #SoftwareEngineering

  3. Circuit Breakers prevent cascading failures. When a service fails repeatedly, stop calling it temporarily. Give it time to recover instead of making the problem worse with more requests. #DesignPattern #SoftwareEngineering

  4. Circuit Breakers prevent cascading failures. When a service fails repeatedly, stop calling it temporarily. Give it time to recover instead of making the problem worse with more requests. #DesignPattern #SoftwareEngineering

  5. “NEED TO LEAVE SITE FOR YOUR SAFETY? - QUICK ESCAPE”

    #QuickExit…I never realized this was an issue too. Obviously, in an abusive situation, the first things checked today are digital, like browser history or someone literally looking over your shoulder.

    Is this #designpattern widely used (known?) on sites like domestic violence shelters or anonymous tip lines?

    design-system.service.gov.uk/p

  6. “NEED TO LEAVE SITE FOR YOUR SAFETY? - QUICK ESCAPE”

    #QuickExit…I never realized this was an issue too. Obviously, in an abusive situation, the first things checked today are digital, like browser history or someone literally looking over your shoulder.

    Is this #designpattern widely used (known?) on sites like domestic violence shelters or anonymous tip lines?

    design-system.service.gov.uk/p

  7. #ITByte: Event Sourcing Pattern helps capture all changes to an application state as a sequence of events.

    What is #Event Sourcing #DesignPattern in #Microservice #Architecture? How does it work?

    knowledgezone.co.in/trends/bro

  8. #ITByte: Event Sourcing Pattern helps capture all changes to an application state as a sequence of events.

    What is #Event Sourcing #DesignPattern in #Microservice #Architecture? How does it work?

    knowledgezone.co.in/trends/bro

  9. Hi there, I'm looking for good #SoftwareArchitecture resources, #blog, #wiki or #community.

    I know good enough the basis of #OOP and #DesignPattern and I'm looking for something more advanced.

    One of my goal is to create #localfirst #software but anything with #network and #web archi are welcome too.

    Thank you for sharing! 🙏🤗
    #boostswelcome :)

  10. Hi there, I'm looking for good #SoftwareArchitecture resources, #blog, #wiki or #community.

    I know good enough the basis of #OOP and #DesignPattern and I'm looking for something more advanced.

    One of my goal is to create #localfirst #software but anything with #network and #web archi are welcome too.

    Thank you for sharing! 🙏🤗
    #boostswelcome :)

  11. Building #iOSApps often means stitching together blog posts & Apple samples - rarely reflective of production-ready architectures.

    The Kotlin/Android ecosystem, by contrast, has aligned around well-documented, real-world patterns.

    Ivan Bliznyuk explores how these approaches can be adapted to Swift/SwiftUI to build maintainable, scalable iOS apps.

    Read now on #InfoQ 👉 bit.ly/4r5ZwI4

    #ArchitecturePatterns #DesignPattern #Kotlin #SwiftUI #MobileDevelopment

  12. Building often means stitching together blog posts & Apple samples - rarely reflective of production-ready architectures.

    The Kotlin/Android ecosystem, by contrast, has aligned around well-documented, real-world patterns.

    Ivan Bliznyuk explores how these approaches can be adapted to Swift/SwiftUI to build maintainable, scalable iOS apps.

    Read now on 👉 bit.ly/4r5ZwI4

  13. Trong phát triển phần mềm, phức tạp không thể bị loại bỏ hoàn toàn - chỉ có thể dịch chuyển nó sang nơi khác. Ví dụ: cache tăng tốc truy vấn nhưng sinh ra bài toán quản lý hết hạn dữ liệu. Phức tạp cốt lõi (do bài toán đòi hỏi) chỉ thay đổi vị trí, không mất đi. Áp dụng cho nhiều khía cạnh: kiến thức, quyết định, kiểm thử... Thiết kế tốt là chọn nơi "đặt" phức tạp sao cho tác động ít nhất. #SoftwareEngineering #KỹThuậtPhầnMềm #Complexity #PhứcTạp #Tech #CôngNghệ #DesignPattern #MẫuThiếtKế

    https

  14. Trong phát triển phần mềm, phức tạp không thể bị loại bỏ hoàn toàn - chỉ có thể dịch chuyển nó sang nơi khác. Ví dụ: cache tăng tốc truy vấn nhưng sinh ra bài toán quản lý hết hạn dữ liệu. Phức tạp cốt lõi (do bài toán đòi hỏi) chỉ thay đổi vị trí, không mất đi. Áp dụng cho nhiều khía cạnh: kiến thức, quyết định, kiểm thử... Thiết kế tốt là chọn nơi "đặt" phức tạp sao cho tác động ít nhất. #SoftwareEngineering #KỹThuậtPhầnMềm #Complexity #PhứcTạp #Tech #CôngNghệ #DesignPattern #MẫuThiếtKế

    https

  15. FYI: Architect's Guide: Building Modern Systems with Facades #shorts: An architect breaks down the facade design pattern. The facade acts as a simple interface to a complex system. It handles what service to use, acting like a gateway manager that controls upgrades. #facade #designpattern #architecture #API youtube.com/shorts/mrEvr4ZftDQ

  16. FYI: Architect's Guide: Building Modern Systems with Facades #shorts: An architect breaks down the facade design pattern. The facade acts as a simple interface to a complex system. It handles what service to use, acting like a gateway manager that controls upgrades. #facade #designpattern #architecture #API youtube.com/shorts/mrEvr4ZftDQ

  17. The Adapter pattern makes incompatible interfaces work together. Wrap third-party APIs to match your application's expected interface. Changes to external services stay contained. #DesignPattern #SoftwareEngineering

  18. The Adapter pattern makes incompatible interfaces work together. Wrap third-party APIs to match your application's expected interface. Changes to external services stay contained. #DesignPattern #SoftwareEngineering

  19. The Strangler Fig pattern gradually replaces legacy systems. Route new features to new code, legacy features to old code. Gradually migrate until the old system withers away. Safe modernization. #DesignPattern #SoftwareEngineering

  20. The Strangler Fig pattern gradually replaces legacy systems. Route new features to new code, legacy features to old code. Gradually migrate until the old system withers away. Safe modernization. #DesignPattern #SoftwareEngineering

  21. Circuit Breakers prevent cascading failures. When a service fails repeatedly, stop calling it temporarily. Give it time to recover instead of making the problem worse with more requests. #DesignPattern #SoftwareEngineering

  22. #Automated #fascism, the true #designpattern of the #siliconvalley #barons when they cobble together their models.

    For instance - #ElonMusk absolutely hates #wikipedia, because it requires "eViDeNcE" and "sOuRcEs" and "fAcTs" and "fAlSiFiAbiLiTy".

    How are you supposed to make people trust the lies of #grok if they can easily dismiss it with a single search?

    Anyways, #AI as automated #censorship is a direct path to automated fascism.

    404media.co/ai-is-superchargin

  23. Wann Modal, Dialog, Lightbox, PopUp & Co. verwendet werden

    Die Begriffe Modal, Dialog, Lightbox, PopUp usw. werden häufig nicht trennscharf verwendet. Doch es gibt klare Unterschiede, wann ein Dialog modal ist und wann nicht – was den Dialog zum PopUp macht und was zur Lightbox. Raimund und Jonas haben vor einiger Zeit im t3n Magazin einen Artikel zu diesem Thema veröffentlicht. Die Nielson Norman Group zeigt in einen ausführlichen Beitrag, mit vielen Beispielen, ebenfalls anschaulich die Unterschiede auf. Direkter Link zum Artikel

    kulturbanause.de/news/wann-mod

  24. Component Names im Vergleich

    Die Benennung von Komponenten kann zu den schwierigsten Aufgaben bei der Entwicklung von Design Systemen und Component Libraries gehören. Ziel einer sinnvollen Benennung sollte es sein, den Kompromiss zwischen dem – aus Sicht von UX/UI und Frontend – fachlich korrekten, und einem allgemein verständlichen Begriff zu finden. Bei Komponenten wie dem »Button« sind sich die meisten Beteiligten noch einigermaßen einig. Aber was unter einem »Panel« oder einer »Toolbar« verstanden wird, […]

    kulturbanause.de/news/componen

  25. Gründe, warum man keine Modal Screens einsetzen sollte

    Modal Screens sind ein beliebtes UI-Element im Webdesign, doch ihr Einsatz ist umstritten. Ähnlich wie bei der Verwendung von Slidern lösen Modals nur scheinbar ein Problem und erzeugen oft mehr Nachteile als Vorteile. Die Microsite ModalzModalzModalz versorgt euch mit Argumenten gegen die Nutzung der Overlays und mit Tipps zur gelungenen Umsetzung – sollte ein Modal Screen zwingend notwendig sein. Direkter Link zur Seite

    kulturbanause.de/news/gruende-

  26. Listen- oder Raster-Ansicht? Wie diese UI-Pattern Benutzer-Entscheidungen beeinflussen

    Gruppen von Elementen, aus denen ausgewählt werden soll, tauchen auf fast jeder Website auf, sei es eine Liste von Beiträgen oder eine Gruppe von Produkten. Wie ordnet man diese »Teaser« an und wie gestaltet man sie am besten? Es haben sich zwei populäre Lösungen entwickelt: Die Listen- und die Raster-Ansicht. Diese bedienen verschiedene Benutzerverhalten jeweils besser: das gezielte Suchen geht besser mit der Listenansicht, die Raster-Ansicht unterstützt das eher ungerichtete […]

    kulturbanause.de/news/listen-o