Coupling from a big-O perspective
Read OriginalThis article proposes viewing software coupling and the Don't Repeat Yourself (DRY) principle through big-O notation. It suggests analyzing the number of code edits (methods, files) required for a change, where DRY implies O(1) edits. The author discusses applying this analysis to software architecture, comparing it to algorithm efficiency and network call problems like n+1 queries.
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
1
The Beautiful Web
Jens Oliver Meiert
•
2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane
•
1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg
•
1 votes
4
Wagon’s algorithm in Python
John D. Cook
•
1 votes
5
An example conversation with Claude Code
Dumm Zeuch
•
1 votes