Hey, I suspect it isn't done because it isn't a very good way to modify a > complex embedded base of software, Lila. Generally, when modifying a > complex embedded base, one designs first, iterates implementation and > internal testing, and then releases a relatively complete piece of > functionality. >
As far as I understand this is about adding a new service, not modifying complex existing behaviour. Is that wrong? Also, while I can't speak for Lila, it does seem to me she is suggesting to go with a simple solution that tackles a specific need well, as opposed to releasing something incomplete. The idea to build small dedicated units rather than monoliths is not something new or controversial in the world of software design. Even though it might be in certain insular communities. See also: https://en.wikipedia.org/wiki/Unix_philosophy Cheers -- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Evil software architect at Wikimedia Germany ~=[,,_,,]:3 _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
