Sergey Baranov

Technology Strategy Advisor, Founder@ArchDays, Partner@ScrumTrek, Chairman@Russian Association of Software Architects

[Sergey Baranov @jsergey]

AI is a multiplier. It scales whatever skills the person wielding it has. A senior dev uses it to amplify order and structure. A newbie? It supercharges chaos and entropy at warp speed.

[Sergey Baranov @jsergey]

Done.

[Sergey Baranov @jsergey]

Such a beautiful #EventStorming session done in banking

[Sergey Baranov @jsergey]

#microservices

[Sergey Baranov @jsergey]

When your dog helps you in preparing to public speech :)
Much better than talking to mirror)

[Sergey Baranov @jsergey]

Enterprise architecture meets event mesh. Looking forward for another tiny paradigm shift :)

[Sergey Baranov @jsergey]

One more #EventStorming session. This time it was for investment business.
Each session has its own (to some extent) pain points. This one had problems with ubiquitous language. Participants definitely spoke using very different terms even in the same context.

[Sergey Baranov @jsergey]

Just finished the first iteration of the #EventStorming for the complex financial domain. In the beginning, we thought: «hey, this is a simple problem». In the end, we found that there are at least 11 different contexts involved :)

[Sergey Baranov @jsergey]

It's incredible how many people spend a lot of time to decouple their monolith using microservices and re-couple them back on a test layer using end-to-end test suites.

[Sergey Baranov @jsergey]

Now it's time for the online #DASA assessment (translated to Russian).
For the first time, different teams/departments have their own unique diagrams and, therefore, have different optimization goals. Not so good, but it's just the beginning of a big journey.

[Sergey Baranov @jsergey]

There are two things that slow down software development: technical debt and dependencies.

[Naval @naval]

All models rely on a small set of critical assumptions.

A good (simple) model uncovers them, while a bad (complicated) model obscures them.

[Ben Sigelman @el_bhs]

0/ Now that organizations are building or buying observability, they are realizing that it can get really damned expensive. And not just “expensive,” but “expensive and out of control.”

This is a thread about *observability value:* both the benefits and the costs.

[Scott W. Ambler @scottwambler]

If you automate a crappy process you just get more crap faster.

[Sergey Baranov @jsergey]

In the left is how I saw it «implemented» a lot of times. In most cases this leads to some kind of disconnecting «group okr» from «company okr». #okr

[Sergey Baranov @jsergey]

#devops

[Sergey Baranov @jsergey]

So true. #devops #lean

[Sergey Baranov @jsergey]

Ok. #chaos and #order.

[Sergey Baranov @jsergey]

This is how different team members assessed their #devops maturity according to #DASA model. What is valuable is conversation after that.

[Joseph Simpson @jjs0sbw]

Evolutionary algorithms are essential factors in the proper evaluation of system configuration. Substantial cost saving is based these evolutionary algorithms #systemengineering #incose_org #structuralmodeling #incose https://t.co/CHLYeUms4X