Re:Fixing under-engineered code vs. fixing over-engineered code
by jrodthree24 on Thursday August 26, 2021 @01:37PM
(#28317955)
This seems kind of obvious though. Larger projects are more in need of the abstractions. You ARE gonna need it.
[ Parent
| on HN ]
Re:Fixing under-engineered code vs. fixing over-engineered code
by awkward on Thursday August 26, 2021 @01:47PM
(#28318130)
Generous to think that you would consider a project over engineered, but still rely on its internal abstractions.
Re:Fixing under-engineered code vs. fixing over-engineered code
by the_sleaze9 on Thursday August 26, 2021 @01:39PM
(#28317992)
The acronym YAGNI itself is flexible enough to handle this edge case accurately.
The GO4 were truly visionary.
Re:Fixing under-engineered code vs. fixing over-engineered code
by xnx on Thursday August 26, 2021 @01:58PM
(#28318266)
GO4?
Re:Fixing under-engineered code vs. fixing over-engineered code
by merrywhether on Thursday August 26, 2021 @02:15PM
(#28318498)
“Gang of Four”, the name commonly applied to the authors of the seminal book “Design Patterns”
Re:Fixing under-engineered code vs. fixing over-engineered code
by 0x500x79 on Thursday August 26, 2021 @02:10PM
(#28318431)
Gang of Four. https://en.wikipedia.org/wiki/Design_Patterns