Optivem Journal
Subscribe
Sign in
Home
TDD in Legacy Code
Group Chat
Team Plans
Podcast
ATDD
Archive
About
Latest
Top
Discussions
Clean Architecture: One Class Per Use Case Is NOT Enough
Code Example
Sep 10
•
Valentina Jemuović
1
Refactoring Should NOT Touch Your Acceptance Tests
A “refactor” PR that changes the acceptance test or the DSL isn't a refactor — it's a behavioral change
Sep 3
•
Valentina Jemuović
3
1
Don't Let AI Multiply Bad Tests
AI learns from the tests you already have. If those are bad, you now get bad tests much faster.
Sep 1
•
Valentina Jemuović
5
2
August 2026
Clean Architecture: Use Cases Should NOT Catch Stripe Exceptions
Error Handling - Application layer
Aug 27
•
Valentina Jemuović
8
6
3
Senior Engineer ≠ Years of Experience
“I've been doing this for 15 years, so I already know.”
Aug 24
•
Valentina Jemuović
10
4
3
Hexagonal Architecture: Don't Follow the Diagram
Don't create a class just because the Hexagonal Architecture diagram has one
Aug 20
•
Valentina Jemuović
6
2
3
TDD in Legacy Code - Contract Tests - Components
How can Frontend & Backend Teams find out that they can't communicate, instead of waiting for slower Acceptance Tests?
Aug 14
•
Valentina Jemuović
4
2
3
The Best Architects Never Stop Coding
You can't feel what your own design costs unless you build something in it. And nobody is going to tell you.
Aug 11
•
Valentina Jemuović
16
10
4
Clean Architecture: Stop Avoiding Every Framework Dependency
Code Example
Aug 6
•
Valentina Jemuović
7
2
3
Nobody Wanted to Write Tests
“We don’t have time to write the code twice.”
Aug 4
•
Valentina Jemuović
7
4
4
July 2026
Fragile Unit Tests in Clean Architecture
So tightly coupled to the domain that they break on every refactor - even when behavior never changes
Jul 31
•
Valentina Jemuović
12
4
3
"Clean Architecture Is Overhead."
Stop counting lines of code
Jul 28
•
Valentina Jemuović
7
4
4
This site requires JavaScript to run correctly. Please
turn on JavaScript
or unblock scripts
