Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
bolha.us is one of the many independent Mastodon servers you can use to participate in the fediverse.
We're a Brazilian IT Community. We love IT/DevOps/Cloud, but we also love to talk about life, the universe, and more. | Nós somos uma comunidade de TI Brasileira, gostamos de Dev/DevOps/Cloud e mais!

Administered by:

Server stats:

252
active users

bolha.us: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.6

#models

1 post1 participant0 posts today
Public
RTN

"Neue Enthüllungen zeigen .. düsteres Bild hinter .. Fassade von Tesla. .. Buch deckt gefährliche Technik und einen cholerischen Chef auf."

"Besonders eindrücklich ist der Fall des Schweizers Thomas Karl. Sein Model S führte auf der Autobahn grundlos Vollbremsungen durch.

In den USA gab es bereits über ein Dutzend Todesfälle durch die fehlerhafte Software."

nau.ch/news/amerika/tesla-file

23.3.2025

#Autopilot#Buch#eAuto
Public
fanf42

We just reached the end if the last days of @RuthMalan System Design course, and is was exceptional 🎉

I mean, of course Ruth is a well of knowledge on systemic and technical architecture design, and her slides+context by themselves are worth the cost of the training. They are just amazing, a succession of pearls distilling the vast knowledge of that broad field. Look by yourself!.

But in addition, I spent 6 days doing group work with an amazing team - that said from someone for whom even anticipating social interactions is burning energy like the sun -, and I practiced a lot of unfamiliar tools that gave shape to intuitions, the kind of "actually that's that you're looking for and you forgot all these parts in your attempt" feedback you get when you're at the beginning of a learning curve.

Thank you Ruth for having organized and shepherded that meeting!

TitoSystem Design Workshop Mar 2025System Design and Software Architecture Workshop for software architects and other system designers . These will all have async work coordinated over Slack, and in-class work, coordinated over Zoom, on: Feb 24-26 and Mar 3-5, 2025 at 11 am - 3:30 pm Eastern Time ( 6 x 4 hr sessions, with a 30 minute break each day) Overview We work in small teams on creating a draft system design and architecture, and lecture topics are driven by the concerns that are being addressed as we do so. This allows us to work on shaping a system design, moving from exploring the system concept to architectural definition, weaving guidance, discussion and practice. As we iterate through architecture design with its trade-offs, decision making, modeling and specification, we grapple with: system design: systems concepts, uncertainty and complexity, context, framing, constraints, forces and trade-offs. business and technical strategy system capabilities and properties: understanding needs/concerns and designing system capabilities and system properties including run-time qualities such as scalability and reliability, and development-time qualities such as evolvability/extensibility. architectural patterns: structural patterns such as layers, hexagonal architecture, and microservices, and mechanisms that may be architecturally significant in various contexts. systems and architecture modeling including an introduction to (just enough, as relevant) Unified Modeling Language (UML) and C4, but drawing on other templates and modeling as appropriate to the design stage and its decision focus. architectural views: structural views help document and communicate the architecture in terms of the components and their relationships, and are useful in assessing architectural qualities like extensibility. Behavioral views are useful in thinking through how the components interact to accomplish their assigned responsibilities and evaluating the impact of what-if scenarios on the architecture. Behavioral views are especially useful in assessing run-time qualities such as performance and security. Execution views help in evaluating physical distribution options and documenting decisions. component specification, interfaces and APIs: components are identified and assigned responsibilities, and interfaces are designed. key architectural design principles and heuristics, including abstraction, separation of concerns, postponing decisions, and simplicity, and related techniques such as interface hiding and encapsulation, as well as system decomposition principles, factoring and refactoring, and good interface design. architecture improvement: we pause periodically to consider what it means to improve and evolve systems and their design, and why, when and how to do that. Instructor: Ruth Malan Outside the US/Canada/EU/UK: Please contact us for purchase parity pricing and scholarship options More information: www.ruthmalan.com
#systemic#techArchitecture#patterns
ExploreLive feeds
About