Sergey Baranov (@jsergey) header
Sergey Baranov (@jsergey) profile picture

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

Moscow, Russia
Joined October 2008
Photo by Sergey Baranov (@jsergey)Photo by Sergey Baranov (@jsergey)Photo by Sergey Baranov (@jsergey)Photo by Sergey Baranov (@jsergey)Photo by Sergey Baranov (@jsergey)Photo by Sergey Baranov (@jsergey)Photo by Sergey Baranov (@jsergey)Photo by Sergey Baranov (@jsergey)Photo by Sergey Baranov (@jsergey)Photo by 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.
6
Such a beautiful #EventStorming session done in banking
1
When your dog helps you in preparing to public speech :) Much better than talking to mirror)
Enterprise architecture meets event mesh. Looking forward for another tiny paradigm shift :)
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.
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 :)
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.
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.
There are two things that slow down software development: technical debt and dependencies.
Sergey Baranov retweeted
All models rely on a small set of critical assumptions. A good (simple) model uncovers them, while a bad (complicated) model obscures them.
35
195
14
1,362
Sergey Baranov retweeted
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.
3
33
6
90
If you automate a crappy process you just get more crap faster.
3
18
1
58
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
This is how different team members assessed their #devops maturity according to #DASA model. What is valuable is conversation after that.
2
2