When to dive into technical details

I just wanted to quickly react one of Peter's statements during the call 
today - we ran out of time there.

Peter (correct me if I am wrong) stated that it sounds premature to work 
on technical details while we have not formalized on the various ways in 
which shapes can be associated with graphs and resources, and related 

While I agree in the value of capturing such theoretical concepts on our 
wiki pages, I also believe there is very much value in working out 
specific solutions, examples and language paradigms. We already have 
several specific starting points, and it will be informative for the 
group on what impact the high-level design decisions have in real terms. 
Both can and should go hand in hand. Of course no choices are made, but 
I would not want to spend the next half a year on nothing but high-level 
discussions if there are already specific solution candidates on the table.


Received on Thursday, 20 November 2014 22:37:13 UTC