There is an interesting moment when a software architect crosses the known line of traditional architecture and heads into the unkown space that is almost an art.
That moment when a solution exceeds the capacity of the compents and becomes something new. A simple shared text editor becomes a blog. Two servers talking together exchanging infomation becomes email. Two servers talking to each other, and needing a way to address informaiton becomes the web.
That tipping point is very interesting to me. when a solution someone envisions stops merely "replacing" the functionality they intended to replace and begins to "become more." That concept that you are doing the same things over and over and yet somehow this one time its different (I am still trying to figure out why the first person roasted a marshmellow – what would tip you over that point?).
This concepts keeps me awake at night sometimes. Wondering if by living in a strict framework/process world I am limiting my solution to the capabilities listed, rather than the potential capabilities.
What is that tipping point? What makes a solution expand?
(and why marshmellow roasted, its not like they are gross raw).