This is TOGAF

Very interesting. Great talk by a great writer and thinker. Thanks.

5 minutes into the talk and all I hear is not far from an academic form of BS omg bro can't get to the point

Amazing talk to understand DDD's aggregates. So funny I bought the Blue book two days ago, and I read the quote about aggregates multiple times, did not understood it. And today I come accross a talk on this specific quote ! Incredible.

Good talk. I almost forget how annoying this guy sounds.

Thank you for really showing me light to figuring out achieving atomicty for event-driven systems backed by no sql.

My favourite GPT prompt is "You are Eric Evans." I just sit back and watch Eric hash out the model with the domain expert.

🎉🎉🎉🎉👏🏼👏🏼👏🏼👏🏼👏🏼👏🏼👏🏼

38:30 bis 38:45 why 43:52

Virtual Domain Experts that would be possible with AI

07:00 message

tThank you very much - I’m glad you included the slide about Message Queue - it helped to understand the diffeence well.

Great talk! Enjoyed the pace and content, thanks for this

This talk is excellent, so we went ahead and featured in the latest issue of 💥Tech Talks Weekly. Congrats to both speakers! 👏

Great talk 👏 FE apps, that really need it, could actually implement DDD if they own the invariant rules and the aggregates. Business rules can definitely be duplicated by FE and BE; but they are separate at the end and can not be mixed as if they belong to the same layer. So can FE be a bounded context of a DDD analysis applied in BE? I dont think so. I would separate them and have them indepently apply it.

Super helpful! Thanks

Very informative. Thank you very much

Excellent 👾

Great talk on software design.

The white fuzzy electronic noise for first 2 1/2 minutes is terrible, skip it-it’s not your headphones fritzing, it’s something wrong with the video. Hope they can fix it and maybe repost.

What

Beautiful

Great talk. Loved the rollercoaster tycoon shout-out!!

2 dakikada anlatılacak şeyi çok özelmiş gibi anlatmasak keşke...

How could anyone find bad system with 10% unit test coverage. It means NOTHING in terms of code/architecture quality. Code coverage is not a good measure of anything more than number of tests. Seen too much useless unit test written only to make test coverage happy.

horrible noise stops at 2:15

Which solution did exist to apply fitness function other boarders? I mean between microservices… archunit works well in a “modular monolith” or “layered architecture”

Good talk, i take capability over quality attribute, everyday ...

A very good presentation, well worth my time!

I was in this room in 2022 and I must say it is still one of the best talks I've ever seen. Learnings to write down and come back to every time. Only downside being that this is very hard to convince people of because they have a very stubborn notion of what RESTful is. At least I can point them to this video.

Carola is an excellent speaker and this talks is brilliant, so we featured it in the latest issue of 💥Tech Talks Weekly. Congrats!

Outstanding. This is a critical aspect of scaling technology and mastering complexity. Supports flow, testing, independence while reducing the cognitive load of the engineers. Great work.

How much time and money does it cost to unravel an existing system and how much does it cost to start all over again. The latter has the advantage that you can use newer technologies with extended capabilities. The first has the advantage that workflows and user experiences stay the same. I guess that external systems that talk to the systems API can remain as they are? Another thing I am curious about if you test whether the performance of the system drops or not when it is chopped up in containers or compartments.

If U People can come UP with more stuff , Definitely U will be the Long Term , Reliable Leader ( NOT Open AI LLM Design ) in AI, ML, NLP, Services in Real Enterprise Bus., Sovereign , G2G, G2B, G2Public, Court2Public

Tech like LLM based GPT,, BitCoin based DApps., may be Fascinating , But they CAN NOT provide AI, ML, DApp Solns., 2 RealWorld Enterprise Bus., , Sovereign, Govt, Courts, Admn, Civil Services, Except Lmtd Scope in AI, ML;

Thanks for this presentation. It showcases an innovative use case of a CMS for implementing a functional taxonomy. I found this approach to be brilliant, as it offers a more user-friendly and straightforward solution compared to Semantic Web tools or graph-oriented databases for this purpose. By leveraging the familiar structure and accessibility of a CMS, the implementation becomes more efficient and less complex, making it an appealing alternative for many organizations.

Great talk

It's a bit naive to assume all developers are accepting even when you present them with the facts. Some just don't want any changes to occur because they're scared. They're scared that if they can't learn this new way of work they'll be out of a job. Somehow these people are the most trusted senior developers in the company and it'll be really difficult to get the rest onboard. I also don't understand why we still feel like architects live in their own corners, while developers are working away. Architects should be embedded in teams, or work with multiple teams daily, so they are a part of the development.

Markus is a fantastic speaker and this talk has been featured in the latest issue of 💥Tech Talks Weekly as most-watched. Congrats 👏

яндекс не смог осилить этот акцент )))

Lots of info and Cool simulation. Is that code shareable ?

I use Scenario Hunting to quickly run and test the abstractions.

First, I guess. Experience does not give you expertise (sadly). The thing with DSLs is that a) it's yet another thing you have to learn (and teach) and b) at some point they always fall short. And then the people left with the inferior expressiveness are the ones who cannot change it. And if you believe that language shapes your thoughts ... Perhaps we're better off leaving them with the language they already know well, that's mature, and evolves the same for everyone (more or less).

Thanks!

I think I agree. I had 2 projects, Plan Weave and ChatGPT clone. Plan Weave has Redux and every component has local state potentially and there was lots of boilerplate from dead code and speculative code and premature optimizations. The ChatGPT clone started out worse than that with bi-directional prop-drilling, but now has a very clean architecture. There is centralized state and services that all components derive from and the components are all dumb, they just present. I have my business logic in one place and I made the Entities clear in my Redux store. I started to try to apply the same refactoring tricks I used in ChatGPT clone and at first progress was super fast! I eliminated 50% of the code bloat. However, I eventually hit a hard wall where it would require _a complete architectural overhaul_ to continue optimizing it and making it cleaner. So like the speaker says, it doesn't matter how much you condense or refactor your code, if the architecture for your code is rotten then you will still run into issues no matter what.

Watching the opening crawl at 2x speed was a unique way to experience that music 😄

What the fuck is this garbage? This guy talked a lot but says nothing of value

I think everyone agrees that complexity creep is a thing... and the only thing that can be done against that is to apply a constant equal counterforce of trying to clean up and simplify things in order to keep or force the complexity down to an acceptable level. But it is as said... often the complexity is a direct result of non-technical reasons. Often it's yesterday's solutions in how work, responsibilities and teams are organized which then lead to various shortcuts being taken that then while solving some issues for some in the long term end up causing different issues like the trade-offs they are. To redesign and refactor some of the horses it would be good if they were decoupled from each other as that would allow changing one without affecting the other but then one would have a bigger mass of things to maintain in exchange with possibly some duplication thrown in.

Very nice, thanks!

one dislike from me because of roma