Skip to main content
16 events
when toggle format what by license comment
Apr 12, 2016 at 13:30 history edited gnat
edited tags
Jun 21, 2013 at 19:03 audit Reopen votes
Jun 21, 2013 at 19:46
Jun 4, 2013 at 11:06 audit Close votes
Jun 4, 2013 at 11:07
May 25, 2013 at 11:10 history edited albertoblaz CC BY-SA 3.0
explain a diagram's mistake
May 24, 2013 at 9:29 comment added mouviciel @pdr - An interface with too many method descriptions does contain features that are not needed.
May 24, 2013 at 9:19 comment added pdr @mouviciel: Don't invoke YAGNI (which is about implementing features you don't need) to justify inflexible code-design. Perhaps invoke KISS, but I maintain that segregated interfaces are less complex than null methods.
May 24, 2013 at 8:31 comment added albertoblaz @mouviciel You are right, but as we were in Software Design class, we tried to think about good, maintainable solutions preventing too much changes in the future
May 24, 2013 at 8:27 comment added mouviciel But you can't reject solution 1 on assumptions that are valid only on solution 2. Solution 1 may still be well suited in a specific context where solution 2 would be overengineered.
May 24, 2013 at 8:24 comment added albertoblaz @mouviciel That's the reason I added the "Extended case" part. I wanted to increment the problems and see if Solution 1 is suitable or not, and compare it against Solution 2
May 24, 2013 at 8:07 history tweeted twitter.com/#!/StackProgrammer/status/337842243710885888
May 24, 2013 at 8:00 comment added mouviciel Solution 1 and solution 2 don't answer the same requirements: In solution 1 there was no need to be able to sell() or open() something. Do you violate the YAGNI principle in solution 2?
May 24, 2013 at 7:30 history edited Joachim Sauer CC BY-SA 3.0
convert to inline images
May 24, 2013 at 7:28 vote accept albertoblaz
May 23, 2013 at 23:30 answer added pdr timeline score: 11
May 23, 2013 at 23:18 answer added Tulains Córdova timeline score: 1
May 23, 2013 at 22:31 history asked albertoblaz CC BY-SA 3.0