Davy Jones@lemmy.dbzer0.com to Programming@programming.dev · 17 hours agoWhich software design principles do you rely on most?message-squaremessage-square21fedilinkarrow-up135arrow-down10file-text
arrow-up135arrow-down1message-squareWhich software design principles do you rely on most?Davy Jones@lemmy.dbzer0.com to Programming@programming.dev · 17 hours agomessage-square21fedilinkfile-text
I’m curious which software design principles you find most valuable in real projects. Two concise summaries I’ve found: Clean Code by Robert C. Martin A Philosophy of Software Design by John Ousterhout
minus-squarebradboimler@lemmy.worldlinkfedilinkEnglisharrow-up10·edit-215 hours agoI write my code for future maintainers. I optimize for clarity, testability, and readability. I’ve become a huge fan of dependency injection. That does not mean I like DI frameworks (Guice). I tend to do it manually with regular code. When I maintain code and I sit there wondering what it actually does, I write a unit test for it right then and there And so on
minus-squaresip@programming.devlinkfedilinkarrow-up3·edit-213 hours agoDI without a tool/injector is just composition. just saying
minus-squarenebeker@programming.devlinkfedilinkEnglisharrow-up2·13 hours agoA good reminder that composition is a useful concept.
I write my code for future maintainers. I optimize for clarity, testability, and readability.
I’ve become a huge fan of dependency injection. That does not mean I like DI frameworks (Guice). I tend to do it manually with regular code.
When I maintain code and I sit there wondering what it actually does, I write a unit test for it right then and there
And so on
DI without a tool/injector is just composition. just saying
A good reminder that composition is a useful concept.