Aleksey Skorobogaty

Aleksey Skorobogaty

@desmount.bsky.social

EnduranceLab https://endurance-lab.io | Amplify human intelligence, not replace it.

150 followers887 following15 posts

Aleksey Skorobogaty reposted

“If we conflate the richness of biological brains & human experience with the information-processing machinations of deepfake-boosted chatbots, or whatever the latest AI wizardry is, we do our minds, brains & bodies a grave injustice.” — @anilseth.bsky.social, winner of @berggruen.org Essay Prize

noemamag.comThe Mythology Of Conscious AI | NOEMAWhy consciousness is more likely a property of life than of computation and why creating conscious, or even conscious-seeming AI, is a bad idea.

Aleksey Skorobogaty reposted

In cellular automata, simple rules create elaborate structures. Now researchers are working backward — starting with the result to learn the rules behind it. @georgemusser.com, SFI’s 2025 Journalism Fellow, explores how this could reshape computation and self-organization in Quanta:

quantamagazine.orgSelf-Assembly Gets Automated in Reverse of ‘Game of Life’ | Quanta MagazineIn cellular automata, simple rules create elaborate structures. Now researchers can start with the structures and reverse-engineer the rules.

Aleksey Skorobogaty reposted

I love the Dijkstra quote: > The question of whether a computer can think is no more interesting than the question of whether a submarine can swim.

Aleksey Skorobogaty reposted

From an engineering perspective, software wants to be decoupled. From a business value perspective, software wants to be deeply interconnected. That's the fundamental friction that software design, and Domain-Driven Design specifically, attempts to address.

The article has connected some dots in my notes. Therefore, a thread🧵: filling the gap between “gravity” and “feature lift,” and how to empower product teams to make better decisions. Where domain eng. brings advantages, and how platform eng. could fit in. A story thro a data-flow perspective.

Aleksey Skorobogaty@desmount.bsky.social

Excellent article on positioning domain engineering between product engineering and infrastructure engineering. I fully agree with the financial model section. However, I prefer to call it ‘platform engineering: the hard parts,’ simply because in the middle, we face more volatile semantics.

View full thread

8/9: Consideration of all three problem spaces gives us the ability to anticipate future states and evolve toward that target. It helps grasp boundaries and trace trajectories for better relevance. Design for Tension empowers product teams to make the best possible decisions in the midst of change.

9/9:Platform eng. can scaffold a reliability mindset for product engineers by providing a causal understanding of systems _below the line_ and by helping connect the dots with systems _above the line_. A balanced and coherent view of boundaries gives confidence to evolve them in the right direction.

The article has connected some dots in my notes. Therefore, a thread🧵: filling the gap between “gravity” and “feature lift,” and how to empower product teams to make better decisions. Where domain eng. brings advantages, and how platform eng. could fit in. A story thro a data-flow perspective.

Aleksey Skorobogaty@desmount.bsky.social

Excellent article on positioning domain engineering between product engineering and infrastructure engineering. I fully agree with the financial model section. However, I prefer to call it ‘platform engineering: the hard parts,’ simply because in the middle, we face more volatile semantics.

View full thread

6/9: Business or domain concern gives us a sense of data — causal relations and transactional boundaries. That knowledge can be used to relax our consistency model and enhance availability (through clear isolation), which is good for event-driven, cloud-native applications.

7/9: Domain modeling unfold data semantics and enables more reliable systems with greater affordances – more user actions in context. Product relevance guides us to explore and verify models against the evolving landscape, mostly found in the interconnections of data-flow.

The article has connected some dots in my notes. Therefore, a thread🧵: filling the gap between “gravity” and “feature lift,” and how to empower product teams to make better decisions. Where domain eng. brings advantages, and how platform eng. could fit in. A story thro a data-flow perspective.

Aleksey Skorobogaty@desmount.bsky.social

Excellent article on positioning domain engineering between product engineering and infrastructure engineering. I fully agree with the financial model section. However, I prefer to call it ‘platform engineering: the hard parts,’ simply because in the middle, we face more volatile semantics.

View full thread

4/9: Platform eng. could help product t. design and build for Tension: - observability 2.0 (wide: cloud, domain, product) - components (event-driven foundation, reliability) - causal understanding (atl toolchain for grasp semantics) Design for Tension is a team sport. Activates platform eng. invest.

The article has connected some dots in my notes. Therefore, a thread🧵: filling the gap between “gravity” and “feature lift,” and how to empower product teams to make better decisions. Where domain eng. brings advantages, and how platform eng. could fit in. A story thro a data-flow perspective.

Aleksey Skorobogaty@desmount.bsky.social

Excellent article on positioning domain engineering between product engineering and infrastructure engineering. I fully agree with the financial model section. However, I prefer to call it ‘platform engineering: the hard parts,’ simply because in the middle, we face more volatile semantics.

2/9: Infrastructure Gravity leads us to pay attention to cloud concerns: how data is stored, processed, and transferred between components. Feature Lift is about product concerns — a field of relevance: how many opportunities for meaningful interaction the data allows us to realize.

3/9: Tension arises when we try to model volatile semantics into strict syntax. Tension here implies coherence: a proper domain data model reduces cloud concerns and amplifies product velocity. A sweet spot for DORA uplift.

Excellent article on positioning domain engineering between product engineering and infrastructure engineering. I fully agree with the financial model section. However, I prefer to call it ‘platform engineering: the hard parts,’ simply because in the middle, we face more volatile semantics.

jackdanger.comInfrastructure Gravity & Domain Engineering | Jack DangerThe following is an excerpt from Executive Engineering.   “You become responsible, forever, for what you have tamed.” – Antoine de Saint-Exupéry, in The Little Prince   Each company draws its own ...

I like these visuals. Linked lists and B-trees are exactly how I represent remodeling in my mind. When you’ve worked with a domain for a long time, you start remodelling it to better fit concurrent product streams and to ‘activate’ their velocity.

«The most effective response to cynicism isn’t to argue against it. It’s to build things that make it obsolete. Want to prove systems can work? Build better systems. Think people are fundamentally corrupt? Create incentive structures that reward cooperation and long-term thinking.»

medium.comWe Don’t Need More Cynics. We Need More Builders.Cynicism is the cheap seats. It’s the fast food of intellectual positions. Anyone can point at something and say it’s broken, corrupt, or…

Aleksey Skorobogaty reposted

Replying to @mikegraycodes.bsky.social

Organisations that take advantage of this fear to squeeze more out of their people might see short-term gains but will ultimately be left behind. Now is the time to double-down and invest in fostering trust, encouraging challenge, and creating a culture of safety.

Aleksey Skorobogaty reposted

You are up to date.