News for hackers. Stuff that matters.
Re:How to Accept Over-Engineering for What It Really Is by ofir_geller on Saturday October 22, 2016 @12:49AM (#12767240)
The specs are the part I found most interesting. 1) First the specs say 3 images, then they say 2. if you are dealing with a manager that can change the specs like that you might want to over engineer just a bit to cover 'arbitrary number of images'. yes I know this is probable just an error by the writer of the article, but it demonstrates something that happens in the wild. 2) Communication is the missing piece in this story. when a developer is given a task they should ask questions about future requirements. "Is it always going to be 3 images?", "will the images always grow by the same ratio?" and so on. the way to not solve imaginary problems is to talk with the stakeholders.
Re:How to Accept Over-Engineering for What It Really Is by fagnerbrack on Saturday October 22, 2016 @01:50AM (#12767423)
Good catch! That was a typo. And very good remarks on how to relate that to the real world, definitely agree with that!

(Btw I have fixed it :D)