InDesign Systems CollectivebyChong Lu Khei·May 16AI makes creation easy but not responsibility - from a design system engineer perspectivePhoto by Shane Rounce on UnsplashA response icon3A response icon3
InStackademicbyMyshaaa·Apr 23Designing Apps for Failure: Fail-Open vs Fail-Closed SystemsTwo very important system design patterns when it comes to how a system should behave is fail-open and fail-close.
InAWS in Plain EnglishbyMudassir Syed·Mar 28NoSQL Data Modeling Explained with DynamoDB Single Table DesignGet your data model wrong and everything downstream pays for it.
Ameypande·Mar 24IntroductionWhen software systems grow, APIs often need to change. Sometimes, data models are moved to new namespaces or redesigned entirely.
José Marcos·Mar 21Scalable Angular Architecture: Organizing by Features and SlotsIn a large Angular + ASP.NET Core monolith, the standard way of organizing files (putting all services in one folder and all components in…
DebugBytez·Mar 11Why Some Software Systems Age Well and Others CollapseThe core principles that separate maintainable systems from collapsing codebases.
José Marcos·Mar 7Mastering SOLID Principles in C#: A Practical GuideWriting code is easy, but writing code that lasts is a challenge. If you have ever struggled with software that breaks every time you add a…
Cihan Özmen·Jan 30When ‘Just One More Condition’ Is a Bad Idea: Strategy PatternHave you ever thought, ‘If I just add one more if here, the project won’t blow up… right?’
Cihan Özmen·Jan 30Inheritance Called. It Wants Its Simplicity Back: Bridge PatternIn software architecture, we sometimes reach a point where inheritance, instead of helping us, starts to become a hindrance.
