De quoi s'agit-il
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
- Software Craftsmanship
- Continuous Integration
- Continuous Delivery
- Trunk Based Development
- Test Driven Development
- Hexagonal Architecture
- Clean Architecture
- Domain Driven Design
- Use Case Driven Design
- System Design
- Clean Code
- Refactoring
- Technical Leadership
- Learning Culture
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.
You can follow us on:
- YouTube: https://www.youtube.com/c/techexcellence
- LinkedIn: https://www.linkedin.com/company/techexcellenceio
- Twitter: https://twitter.com/techexcellence_
- GitHub: https://github.com/valentinacupac/techexcellence/discussions
Founder: Tech Excellence was founded by Valentina Cupać, Technical Coach @ Optivem.
Community Guidelines: We want to build a safe community. Please ensure you have an appropriate profile photo image. When posting comments, please ensure your communication is professional. In the case of violation of these guidelines, your membership will be revoked.
Événements à venir (1)
Tout voir- Property Based Testing: Avoid Accidental Quality (Mourjo Sen)Lien visible pour les participants
Automated tests are the cornerstone of modern software development. It ensures that every time we build new functionalities, we do not break existing features our users rely on.
Traditionally, we tackle this with example-based tests. We list down specific scenarios (or test cases) that verify the expected behaviour.
However, example-based tests have a critical flaw. The quality of our software depends only on the examples in our test suites. This leaves out a class of scenarios that the authors of the test did not envision – the “unknown unknowns”.
While example-based tests focus on reproducibility of known bugs, property based tests focus on discoverability of unknown bugs. It shifts our focus from enumerating examples to verifying the fundamental properties of our system.
Outline of the session:
- Example vs property based tests: Verifying predetermined scenarios vs finding bugs
- Thinking about fundamental properties of systems
- Why the property of associativity does not hold for floating point numbers
- Sampled test cases lead to accidental quality
- Property based tests find bugs in unknown unknowns
- Shrunk failing cases are key feedback to fixing bugs
- Introduction to a Meeting application for the demo
- Demo
- Bugs found were not coded in the testsABOUT MOURJO
Mourjo Sen is a senior software engineer at Booking.com. He has ten years of experience in building resilient well tested microservices. He is originally from India and currently lives in Amsterdam with his wife.
- LinkedIn: https://www.linkedin.com/in/mourjo
- Twitter: https://x.com/mourjo_sen
- GitHub: https://github.com/mourjo
- Website: https://mourjo.me/
