- Видео 57
- Просмотров 92 358
Tech Excellence
Сербия
Добавлен 30 май 2022
Technical Excellence is the foundation of sustainable software engineering. Without technical excellence, there's no quality; the development is slow and cannot be sustainable. Without technical excellence, there's no agility.
Do you want to share knowledge about software quality, to build better products?
This group is for engineering leaders and software developers who are motivated by building high-quality solutions and continuously improving. Technical Excellence is both a mindset and a set of practices to help us build quality software faster and deliver value sooner.
Our focus will be on the following topics:
- Extreme Programming
- Test Driven Development
- Continuous Delivery
- Trunk Based Development
- Clean Architecture
- Domain Driven Design
Our sessions will be in English, held remotely, and open to participants across the globe.
Our goal is to share knowledge, discuss diverse perspectives and synthesize our collective knowledge.
Do you want to share knowledge about software quality, to build better products?
This group is for engineering leaders and software developers who are motivated by building high-quality solutions and continuously improving. Technical Excellence is both a mindset and a set of practices to help us build quality software faster and deliver value sooner.
Our focus will be on the following topics:
- Extreme Programming
- Test Driven Development
- Continuous Delivery
- Trunk Based Development
- Clean Architecture
- Domain Driven Design
Our sessions will be in English, held remotely, and open to participants across the globe.
Our goal is to share knowledge, discuss diverse perspectives and synthesize our collective knowledge.
So you think you might be an architect (Sonya Natanzon)
We are all familiar with the title software architect, but you may not know what a software architect does or how to become one. Perhaps someone even gave you the title, but you are not sure what’s expected of you. Or you suspect you might be doing a job of a software architect, but can’t pinpoint when or explain how you made the leap and whether you are fulfilling the expectations of this nebulous role.
In this talk, you will learn:
• How to define a role of a software architect for yourself and your organization
• What do software architect do (a day in the life)
• Typical pitfalls to avoid
ABOUT SONYA
Sonya is a seasoned engineering leader and software architect. She works at the intersec...
In this talk, you will learn:
• How to define a role of a software architect for yourself and your organization
• What do software architect do (a day in the life)
• Typical pitfalls to avoid
ABOUT SONYA
Sonya is a seasoned engineering leader and software architect. She works at the intersec...
Просмотров: 0
Видео
Orchestration vs. Choreography: The good, bad & the trade-offs (Laila Bougria)
22 дня назад
One of the goals of building microservice-based architectures is to reduce the complexity of individual components. In doing so, much of that complexity shifts from individual services towards interservice communication, making how we design those service interactions essential in our system design. That's where orchestration and choreography come in, two coordination techniques that can help u...
Optimizing for a fast flow of value with Architecture for Flow (Susanne Kaiser)
22 дня назад
In today’s fast-paced business environment, it’s essential for organizations to continuously adapt and evolve to remain competitive and stay relevant in the market. This talk explores the synergy of combining Wardley Mapping, Domain-Driven Design (DDD), and Team Topologies as "Architecture for Flow". Architecture for Flow provides a holistic, pragmatic toolset for designing, building, and evolv...
Architecture Modernization: Aligning Software, Strategy & Structure (Nick Tune)
22 дня назад
Legacy architectures are a business risk, stifling your organization's ability to innovate. On the other hand, modernized architectures can be a competitive advantage allowing your business to innovate at speed and scale their organizations. But effective modernization is far more than just rebuilding the old system with new technologies and the latest architectural patterns. It's an opportunit...
Test Doubles without Tears (Marco Consolaro & Alessandro Di Gioia)
22 дня назад
Introduction: Join us for a focused session on the practical use of test doubles popularised by the London School of TDD, where we will also demonstrate it in real-time. The session will be live coding: Morse Code Kata. Learning Outcomes: • Differentiate between Dummies, Mocks, Stubs, Fakes, and Spies. • Understand the concept of Command/Query separation in software design. • Choose the appropr...
Complexity and Modularity: Two Sides of the Same Coin (Vlad Khononov)
22 дня назад
Every software engineer and architect strives to design modular software systems and avoid complexity. Yet, frequently, the outcome is the opposite: what promised to be an elegant, well-thought architecture results in another big ball of mud. Why does this pattern persist and how do we learn not to repeat it? In this talk, I will explore the nature of modularity and complexity, including their ...
Domain-Driven Refactoring (Jimmy Bogard)
22 дня назад
Books, workshops, storming and more, all build up an idealized domain model. All describe great techniques for domain-driven greenfield applications. But what about the code we have? How can we take what's already built, and move it towards a better, more cohesive design? In this session, we'll look at anemic, procedural, boring code and examine code smells that can point us in the right direct...
Metal-In Test-Driven Development: A Dual-Target TDD Approach (Fran Climent)
Просмотров 76523 дня назад
How can we get rid of the hardware bottleneck in order to speed up our embedded development processes? Could we treat our embedded code as a complete subsystem decoupled from the underlying hardware? If yes, how could we achieve it? Outline of the practical session: - Develop a highly decoupled and portable ‘BatteryMonitor’ module following Metal-In TDD approach. - Highlight the differences bet...
Clean Architecture: Crafting Flexible Software Systems (Olaf Thielke)
25 дней назад
This talk explores the concept of Clean Architecture, its importance in software development, and how it addresses common challenges. We'll discuss the purpose of software architecture, examine traditional development pitfalls, and introduce Clean Architecture principles. Through a real-world case study with audience participation, we'll demonstrate the practical application and benefits of thi...
TDD: Theme & Variations (Kent Beck)
27 дней назад
Test-driven development (TDD) has become a polarizing development practice. Claims about TDD range from “absurd” to “essential” to “damaging” to “joyous.” In this talk, we’ll take a step back and look at TDD in context, including its history, current practice, and potential future. Outline of the session: - History of TDD - Canon TDD - Variations: TCR, Exploratory, Mocks, Top-down, Bottom-up, U...
Hexagonal Architecture (Alistair Cockburn)
29 дней назад
Learn from it’s creator the rules and structure of the “Hexagonal”, more correctly called the Ports & Adapters architecture. In this lecture, Dr. Cockburn will describe why he created it, its benefits and also its costs, the UML description, and also some sample code. As an extra challenge, he will invite you to write your first Ports & Adapters application in your favorite language /during/ th...
Modern Software Engineering: Building Better Software Faster (Dave Farley) - TE Conf 2024
Месяц назад
What really works to help us build better software faster? What are the fundamentals of our profession, that if we get them right, and apply them whatever our goal and whatever our technology, will increase our chances of success. Some of these ideas have been hiding in plain sight, and if we just take them and build our practice and process on them, we do get better results. So what are they, ...
How Domain-Driven Design scaled a Big Ball of Mud product (Kenny Baas-Schwegler)
Просмотров 8952 месяца назад
Many products start out with a simple, naive model able to prove market fit. And most of the time that one model grows, because more features need to be put in at a fast pace. This can have a huge impact once the product needs to scale. Because that fast pace can turn the model into a Big Ball of Mud, and most of the time that model isn’t the most useful model to solve the core business problem...
From EventStorming to TDD (Oliver Zihler & Alina Liburkina)
Просмотров 1,5 тыс.2 месяца назад
Last time, we showed how EventStorming, DDD, and Clean Architecture can help us foster shared mental models between domain experts and developers effectively. This time, we will focus on one main variation of EventStorming, Design-Level EventStorming, to demonstrate how we can effectively employ it during iteration planning to split user stories and derive business rules and aggregates, such th...
Product Minded Engineer (Tamás Bunth)
Просмотров 4133 месяца назад
In this meetup, the Speaker will argue for the importance of familiarizing Software Engineers with Product Thinking. He will show various insights, tools and skills that are often overlooked when we discuss the important competencies of Software Engineers, and he will show how to use them to become more impactful, more valuable and more satisfied in an engineering role. Outline of the session: ...
Just avoid layers. Simple as that. The result of you instead localizing your code around subjects will end up in about this architecture. The name is bad as it could suggest you should stick with the layers.
Thank you for this excellent talk! It is probably the best one I've heard regarding this topic. Is there any tool available that will collect all three metrics (S, V, D), that will automate the calculation for me? I guess no, because I think it will be hard to find the connections for some of the coupling types.
Yes
man OOP makes this stuff so overcomplicated this entire architecture just looks like a request handler function anyone that has any experience with express.js for instance has already been using this architecture.
isnt this BDD?
next time please add some transparency to the top right TE logo, or move it outside the presentation area
Thanks for the feedback!
loved the exercice ! thank you so much
It’s not because I am from Serbia like Cupać but I really don’t know if there is better channel than this one about the TDD! Keep going guys!!!
Appreciate it! Glad that you're onboard with TDD 👏
Totally agree!
Keep doing this amazing work. Great content indeed.
Thanks for the support :)
Great video! 😊
Thank you!
This is excellent one.
Thank you!
A very nice session on service boundaries and fat messages. However I still prefer to store the OrderDetails on the First Order Microservice, in one place and use a Saga and specific Commands to send specific portions of the OrderDetails Data to each of the rest Microservices in the ecommerce scenario. Otherwise we need to have extra layer of temporal persistency for each microservice (we already have a local-database at each microservice, we propably have a lookup database, and we have to deal now with a new temporary storage ), add on top to implement all these using hexagons and CQRS projecions and the code becomes really-really complex. My two cents......Great session though!
Fantastic pragmatic presentation.
One thing I didn't hear you talk about is using Read Models to avoid the cross-service interactions. I have always professed that a Read Model is generally UI oriented and ignores all boundaries. Then again, I have been talking about Packaged Business Capabilities (UI + API + Data + Events all packaged as one thing) for about 6 years.
I am 20 minutes into the video and I can tell by now that it is awesome, packed with real life examples.
Glad you enjoyed it!
Here are the slides: www.dropbox.com/scl/fi/jtyb6lmscycau8axkmg5t/ddd-service-boundaries.pdf?rlkey=gxpcxtadgx7iq7c7og4orhizr&e=1&st=a6atkiny&dl=0
Thanks Adam for the awesome session!
You're welcome!
Designing a UI for Microservices: go.particular.net/tech-excellence-ui-2 Service Oriented Architecture: go.particular.net/tech-excellence-boundaries-2
This architecture has been around for over 20 years in the modular monolith/modular client. What this video really shows is how little most developers really understand about software architecture and how poorly it seems to have been taught for a long time.
Agree and then populating all medias with good clean architecture courses :) I feel same aspect Divide and Conquer only different context.
Hexagonal Architecture should just be called what it really is, to avoid so much confusion. What it really is a way to organize code based on the concepts of Input or driver ports and Output or driven ports. Input ports are driven by the users or the app and they drive the application, Output ports are driven by the application and they drive interactions with external systems. That's it. Just some ports. How you organize your projects is not prescribed. You only have to call your inputs and outputs ports and abstract them away however you see fit, so that you can focus on testing the app's behavior based on how it's driven.
I used already Vertical Slice architecture at the beginning of my career, it was then known as Big Ball of Mud
Can not agree more😅😅😅
The biggest advantages of using vertical slice architecture is FEWER MERGE CONFLICTS!
People that have had to face the difficulties of not having taken the right micro decisions at the right time, will totally understand this talk and even have some flashbacks, 😹😹
Totally agree 😂
This is the Gilded Rose github repo: github.com/emilybache/GildedRose-Refactoring-Kata
I hope you end up using Mock Service Worker instead of mocking window.fetch... will have to watch to the end and see, because I don't like having to dirty the API adapter by injecting what is basically an http client. It might make sense in C# but in JS world you have things like window.fetch or axios and their interfaces are not compatible, unless you abstract them yourself and create a common interface.
If we mock the request (a method that communicates to the outside world) using MSW, the test will run a bit slower than if we pass a fake implementation of the request. Doing MSW in the integration tests - where we assert user journeys by rendering specific parts of the app - totally makes sense. However, asserting all the implementation details of the adapter (e.g., headers that are passed into the request) by involving MSW in the unit test is inefficient, nor it's efficient to assert these implementation details in integration tests. A better approach is to have a trivial unit test doing this job.
23:44 I find the IBAN validation API adapter a bit too complicated. You shouldn't need a closure to cache the IBAN to be validated. You could just create an Adapter class or object that would contain IBAN related functions like validating an IBAN, extracting encoded information from that IBAN and so on. This would mean less mallocs to just validate an IBAN. Just have a singleton adapter and functions you can directly call on it, like `validateIBAN(iban: string)`.
The closure leaves an opportunity to pass an argument when the adapter is for mutations: // Adapter factory function createAdapter(options) { return (x) => { // do communicate with an outside world }; } // Use Case const useCreateTodo = () => { const factory = useAdapterFactory(); const mutation = useMutation({ mutationFn: factory() }); const [formValues, setFormValues] = useState<FormValues>(); const handleSubmit = () => { const result = await mutation.mutate(formValues); }; };
Plus, the closure allows passing the request (a method that communicates to the outside world). This makes it easy to write a unit test for such an adapter because a fake request can be provided.
I've discovered the same architecture, in the same way you did. And, by experience, do not reuse code between handlers. There is nothing wrong on having copied/pasted code. Keep in mind modifications will come per feature, so, probably, this code will need to evolve independently, and the duplicated code will not be duplicated any more.
Here's a link to code demo: github.com/javisan81/hierarchy
Thank you for sharing this perspective on microdecisions in software engineering! The concept of making small, specific decisions rather than tackling problems overly complexly really resonates with me. I believe this minimalist approach can lead to cleaner, more maintainable, and easier-to-understand code. Definitely something to consider in a product!!! I see Agile in action here, as it aligns well with the iterative and incremental approach of microdecisions.
Glad it was helpful!
so you went from Controller -> Service -> Repo to Controller -> Handler -> Service -> Repo xD great
Services are only introduced when it is DRY. Instead of giant ball of mud where anything goes.
He didn't invent VSA. He formalized it. VSA is described in the Clean Architecture book by that old guy, uncle Bob or something like that. 😅 Joke aside I don't know for sure if it's even older than that or who's described the idea first.
Fantastic presentation, thank you so much for putting this together. Great examples in a real world scenario. Very clearly demonstrated the pitfall of relying on coverage, and the confidence you can get by utilising mutation testing. I’m definitely going to give Stryker a go in my projects.
Glad you enjoyed it!
Thanks for the great talk and answers to my questions!
You're welcome!
Here's the link to the code demo github.com/dmoka/MutationTestingMeetup
Thanks for your video and GitHub demo project, this is what WE(I believe WE not just me) want, a real-life app component TDD step by-step.
Great talk Jonas, thanks for the explanation!
You're welcome :)
Enjoy the entire session. Learn so much. It increase my knowledge about clean architecture
Thank you
It was amazing session
Thank you so much.
Superb
Thanks alot
Amazing session!!
Thank you!
Thank you...
Great Explaination.
Glad it was helpful!
Thank you
Excellent talk and demo.
Thank you :)
Thanks
Pierre really is the GOAT
Amazing discussion, thanks guys!
You're welcome, thanks for joining the discussion :)
Great presentation! Jimmy mentions on 59:00, that they've built a "Unit of work" for a data storage that does not support it out of the box. Are there any examples available online?
It was an interesting session, hope you can make a next one as a following session with practical part(implementation wise)
Thank you, that's a great suggestion 🙌
Hello people, great video . Why is the validation of the isbn in the application side , is it not part of the business domain?
I think a useful distinction is that unit tests should run in a single process. As soon as you've got multiple processes involved, things get slower, less deterministic and harder to debug.
I love the meta discussion about learning!
You're welcome @NitsanAvni :)
always a pleasure to follow you Michaël Azerhad