# Optivem Journal TDD | Hexagonal Architecture | Clean Architecture This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Using acceptance tests to catch regression bugs in legacy code before production DevFeed: [Using acceptance tests to catch regression bugs in legacy code before production]() Original publisher: [Read original article]() Author: Valentina Jemuović Published: 2026-09-16T07:33:58Z Content type: tutorial Language: en Sources: [Optivem Journal]() Topics: [Testing](), [Requirements](), [legacy]() Tags: [automated](), [bugs](), [e2e](), [legacy-code](), [regression](), [requirements](), [testing](), [ui](), [unit-tests]() ### AI overview This hands-on article explains why automated unit and end-to-end tests may still allow production bugs in legacy code. It presents acceptance test-driven development (ATDD), where requirements and tests describe the same observable behavior, making coverage clearer and reducing dependence on UI steps. ### Source excerpt You automated, and manual regression testing is still there. Those two facts have the same cause. ## Refactoring Should NOT Touch Your Acceptance Tests DevFeed: [Refactoring Should NOT Touch Your Acceptance Tests]() Original publisher: [Read original article]() Author: Valentina Jemuović Published: 2026-09-03T06:00:37Z Content type: opinion Language: en Sources: [Optivem Journal]() Topics: [Refactoring](), [Pull Request](), [test]() Tags: [change](), [dsl](), [refactor](), [refactoring](), [test](), [tests]() ### AI overview The article argues that a refactoring pull request should not change acceptance tests or their DSL, because doing so changes behavior rather than merely restructuring code. ### Source excerpt A "refactor" PR that changes the acceptance test or the DSL isn't a refactor -- it's a behavioral change ## Don't Let AI Multiply Bad Tests DevFeed: [Don't Let AI Multiply Bad Tests]() Original publisher: [Read original article]() Author: Valentina Jemuović Published: 2026-09-01T08:22:21Z Content type: opinion Language: en Sources: [Optivem Journal]() Topics: [Testing](), [Artificial Intelligence]() Tags: [ai](), [bugs](), [testing](), [ui]() ### AI overview AI-generated tests can multiply existing problems when a test suite is brittle or tightly coupled to the user interface. The article argues that teams should improve tests so they reflect the application domain before using AI to generate more of them. ### Source excerpt AI learns from the tests you already have. If those are bad, you now get bad tests much faster. ## Clean Architecture: Use Cases Should NOT Catch Stripe Exceptions DevFeed: [Clean Architecture: Use Cases Should NOT Catch Stripe Exceptions]() Original publisher: [Read original article]() Author: Valentina Jemuović Published: 2026-08-27T06:01:02Z Content type: tutorial Language: en Sources: [Optivem Journal]() Topics: [Error Handling](), [stripe]() Tags: [architecture](), [error-handling](), [exceptions](), [stripe]() ### AI overview The article addresses error handling in the application layer and argues that Clean Architecture use cases should not catch Stripe exceptions. ### Source excerpt Error Handling - Application layer ## Senior Engineer ≠ Years of Experience DevFeed: [Senior Engineer ≠ Years of Experience]() Original publisher: [Read original article]() Author: Valentina Jemuović Published: 2026-08-24T06:01:00Z Content type: opinion Language: en Sources: [Optivem Journal]() Topics: [Software Engineering](), [Development](), [engineering-culture]() Tags: [effective](), [engineering](), [experience](), [learning](), [mistakes](), [software]() ### AI overview This opinion argues that years of software engineering experience do not reliably measure engineering ability. Repeated habits, including poor design, avoiding tests, and overengineering, can become more entrenched over time, while continuous learning, experimentation, feedback, and willingness to change are presented as stronger indicators of effectiveness. ### Source excerpt "I've been doing this for 15 years, so I already know." ## Why Software Architects Should Keep Writing and Reading Code DevFeed: [Why Software Architects Should Keep Writing and Reading Code]() Original publisher: [Read original article]() Author: Valentina Jemuović Published: 2026-08-11T06:00:37Z Content type: opinion Language: en Sources: [Optivem Journal]() Topics: [coding](), [Code](), [consistency](), [pull-requests](), [Artificial Intelligence]() Tags: [code](), [coding](), [consistency](), [developer](), [engineering](), [model]() ### AI overview This opinion article argues that software architects should remain engaged with code rather than treating coding as beneath them. Writing, reading, and reviewing code helps architects understand implementation costs, maintain consistency, and judge whether AI-generated code fits the existing system. ### Source excerpt You can't feel what your own design costs unless you build something in it. And nobody is going to tell you. ## How a Tech Lead Encouraged Testing in Legacy Code DevFeed: [How a Tech Lead Encouraged Testing in Legacy Code]() Original publisher: [Read original article]() Author: Valentina Jemuović Published: 2026-08-04T06:02:15Z Content type: opinion Language: en Sources: [Optivem Journal]() Topics: [Test-driven development](), [legacy](), [clean-code](), [Template](), [Software Engineering]() Tags: [clean-code](), [legacy-code](), [tdd](), [tech-lead](), [training](), [unit-tests]() ### AI overview This opinion article recounts how an engineering leader struggled to introduce testing and clean-code practices across multiple companies. As a Tech Lead, the author created a testable Clean Architecture template, recruited developers who valued quality, built an initial module, and trained the team to use the approach. ### Source excerpt "We don't have time to write the code twice." ## When Clean Architecture Overhead Is Justified in Larger Projects DevFeed: [When Clean Architecture Overhead Is Justified in Larger Projects]() Original publisher: [Read original article]() Author: Valentina Jemuović Published: 2026-07-28T06:01:50Z Content type: opinion Language: en Sources: [Optivem Journal]() Topics: [Software](), [Object-relational mapping](), [Databases]() Tags: [architecture](), [clean-architecture](), [database](), [databases](), [developer](), [developers](), [orm](), [software]() ### AI overview The article argues that Clean Architecture adds real overhead through extra interfaces, abstractions, indirection, and separate domain and ORM entities. It contends that this trade-off becomes worthwhile as midsize and enterprise projects grow, because decoupling business logic from infrastructure and database structures makes change easier. ### Source excerpt Stop counting lines of code ## Every Developer Is Already an Architect DevFeed: [Every Developer Is Already an Architect]() Original publisher: [Read original article]() Author: Valentina Jemuović Published: 2026-07-21T13:02:36Z Content type: opinion Language: en Sources: [Optivem Journal]() Topics: [Software](), [Code](), [API]() Tags: [api](), [architecture](), [code](), [developer](), [engineering](), [software]() ### AI overview The article argues that developers make architectural decisions whenever they write code, even when those choices appear to be implementation details. It explains how unexamined decisions can accumulate into an unintended architecture and emphasizes making such decisions deliberately. ### Source excerpt Most developers think architecture is someone else's job. ## Broken Systems Don't Need More Developers DevFeed: [Broken Systems Don't Need More Developers]() Original publisher: [Read original article]() Author: Valentina Jemuović Published: 2026-07-14T09:12:34Z Content type: opinion Language: en Sources: [Optivem Journal]() Topics: [systems](), [legacy](), [Back end](), [Test-driven development]() Tags: [architecture](), [code-reviews](), [developers](), [engineering](), [legacy](), [legacy-code](), [meetings](), [merge](), [onboarding]() ### AI overview Adding developers to a tightly coupled legacy system may slow progress because onboarding, interruptions, meetings, code reviews, and merge conflicts increase. The article argues that architecture, rather than team size, is the main bottleneck. ### Source excerpt If four developers aren't delivering fast enough, why not make it eight? ## Clean Architecture Mistake: ORM ≠ Domain DevFeed: [Clean Architecture Mistake: ORM ≠ Domain]() Original publisher: [Read original article]() Author: Valentina Jemuović Published: 2026-07-09T06:02:30Z Content type: opinion Language: en Sources: [Optivem Journal]() Topics: [Object-relational mapping]() Tags: [architecture](), [clean-architecture](), [orm]() ### AI overview The article warns that ORM entities should not be confused with domain entities. ### Source excerpt Do NOT confuse ORM entities with domain entities. ## Your Architecture Doesn't Rot Overnight DevFeed: [Your Architecture Doesn't Rot Overnight]() Original publisher: [Read original article]() Author: Valentina Jemuović Published: 2026-07-07T06:00:37Z Content type: opinion Language: en Sources: [Optivem Journal]() Topics: [legacy](), [systems](), [Software](), [Test-driven development]() Tags: [architecture](), [business-logic](), [code](), [dependency](), [legacy](), [refactor](), [requirements]() ### AI overview The article explains how repeated convenience-driven decisions gradually weaken boundaries between business logic and infrastructure. It argues that architectural decay often remains hidden while the application works and tests pass, eventually making seemingly simple changes difficult to locate and implement. ### Source excerpt As deadlines become tighter, convenience starts winning. ## TDD in Legacy Code - Maintainable Component Tests - Backend DevFeed: [TDD in Legacy Code - Maintainable Component Tests - Backend]() Original publisher: [Read original article]() Author: Valentina Jemuović Published: 2026-07-02T06:02:41Z Content type: tutorial Language: en Sources: [Optivem Journal]() Topics: [Back end](), [Test-driven development](), [legacy]() Tags: [api](), [backend](), [component](), [erp](), [legacy](), [legacy-code](), [refactor](), [tdd](), [tests]() ### AI overview A tutorial on refactoring brittle backend component tests that are coupled to a backend API and ERP system, with the goal of making them more maintainable. ### Source excerpt Many Backend Teams write unmaintainable Backend Component Tests - coupled to the Backend API and ERP. I'll show you how to refactor these brittle tests. ## Why Legacy Code Turns Small Changes Into Multi-Day Firefighting DevFeed: [Why Legacy Code Turns Small Changes Into Multi-Day Firefighting]() Original publisher: [Read original article]() Author: Valentina Jemuović Published: 2026-06-30T06:02:36Z Content type: opinion Language: en Sources: [Optivem Journal]() Topics: [legacy](), [Test-driven development](), [Development](), [Software]() Tags: [dev](), [engineering](), [legacy-code](), [tdd]() ### AI overview This commentary examines how legacy code can turn a small change into days of investigation and risk. It argues that tangled dependencies, missing tests, and outdated code prevent senior developers from improving architecture and make routine maintenance frustrating. ### Source excerpt The field took twenty minutes. Everything around it took three days.