Reef. Kaminski, P. 2004. Paper bibtex @unpublished{kaminski04,
added-at = {2006-03-24T16:34:33.000+0100},
author = {Kaminski, Piotr},
biburl = {http://www.bibsonomy.org/bibtex/25a255b4e342e1e8af7914e5a43b2aa80/neilernst},
citeulike-article-id = {227024},
comment = {- Good format for a proposal, divides nicely into hypothesis and proposed soln.
- maybe a good way of doing UML layout is more holistically: that seems to mimic human approaches.
- can developer not update code simultaneously with docs? e.g. tests, pseudocode (both are dev and doc).
- strongly quant. bias in design
- is source the 'ground truth'? or is there more to complex systems than the pure code (clearly, seems obvious some emergent behaviour is to be expected).
- XML is not ordered.},
description = {sdasda},
institution = {U. Victoria},
interhash = {9fccd4a33133e8b6902332ccb118b44e},
intrahash = {5a255b4e342e1e8af7914e5a43b2aa80},
keywords = {software engineering},
priority = {0},
timestamp = {2006-03-24T16:34:33.000+0100},
title = {Reef},
url = {http://www.ideanest.com/reef/},
year = 2004
}
Downloads: 0
{"_id":"CMQsKYQ57aBu2Mo7v","bibbaseid":"kaminski-reef-2004","downloads":0,"creationDate":"2016-04-12T13:16:35.920Z","title":"Reef","author_short":["Kaminski, P."],"year":2004,"bibtype":"unpublished","biburl":"http://www.bibsonomy.org/bib/author/kaminski?items=1000","bibdata":{"bibtype":"unpublished","type":"unpublished","added-at":"2006-03-24T16:34:33.000+0100","author":[{"propositions":[],"lastnames":["Kaminski"],"firstnames":["Piotr"],"suffixes":[]}],"biburl":"http://www.bibsonomy.org/bibtex/25a255b4e342e1e8af7914e5a43b2aa80/neilernst","citeulike-article-id":"227024","comment":"- Good format for a proposal, divides nicely into hypothesis and proposed soln. - maybe a good way of doing UML layout is more holistically: that seems to mimic human approaches. - can developer not update code simultaneously with docs? e.g. tests, pseudocode (both are dev and doc). - strongly quant. bias in design - is source the 'ground truth'? or is there more to complex systems than the pure code (clearly, seems obvious some emergent behaviour is to be expected). - XML is not ordered.","description":"sdasda","institution":"U. Victoria","interhash":"9fccd4a33133e8b6902332ccb118b44e","intrahash":"5a255b4e342e1e8af7914e5a43b2aa80","keywords":"software engineering","priority":"0","timestamp":"2006-03-24T16:34:33.000+0100","title":"Reef","url":"http://www.ideanest.com/reef/","year":"2004","bibtex":"@unpublished{kaminski04,\n added-at = {2006-03-24T16:34:33.000+0100},\n author = {Kaminski, Piotr},\n biburl = {http://www.bibsonomy.org/bibtex/25a255b4e342e1e8af7914e5a43b2aa80/neilernst},\n citeulike-article-id = {227024},\n comment = {- Good format for a proposal, divides nicely into hypothesis and proposed soln. \r\n- maybe a good way of doing UML layout is more holistically: that seems to mimic human approaches. \r\n- can developer not update code simultaneously with docs? e.g. tests, pseudocode (both are dev and doc). \r\n- strongly quant. bias in design \r\n- is source the 'ground truth'? or is there more to complex systems than the pure code (clearly, seems obvious some emergent behaviour is to be expected).\r\n\r\n- XML is not ordered.},\n description = {sdasda},\n institution = {U. Victoria},\n interhash = {9fccd4a33133e8b6902332ccb118b44e},\n intrahash = {5a255b4e342e1e8af7914e5a43b2aa80},\n keywords = {software engineering},\n priority = {0},\n timestamp = {2006-03-24T16:34:33.000+0100},\n title = {Reef},\n url = {http://www.ideanest.com/reef/},\n year = 2004\n}\n\n","author_short":["Kaminski, P."],"key":"kaminski04","id":"kaminski04","bibbaseid":"kaminski-reef-2004","role":"author","urls":{"Paper":"http://www.ideanest.com/reef/"},"keyword":["software engineering"],"downloads":0},"search_terms":["reef","kaminski"],"keywords":["software engineering"],"authorIDs":[],"dataSources":["ePTwKNCLFT28DzR9b"]}