tag:blogger.com,1999:blog-8678405.post7195736300155647196..comments2023-09-02T15:54:52.482+01:00Comments on Ricky's technical blog: Really Own Your CodeRicky Clarksonhttp://www.blogger.com/profile/13845104548520132930noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-8678405.post-10958788865874503582007-05-11T18:27:00.000+01:002007-05-11T18:27:00.000+01:00I just can tell from my experience as professional...I just can tell from my experience as professional Java developer that in teams it is not possible to assign classes to single people and it is not possible to build a product solely from libraries. Most of the classes are interwoven, and commonly developers are assigned for specific area of application (or functionality layers) that do not follow the class hierarchy. Otherwise you would never have problems with conflicting changes, which we have quite often in large projects. <BR/>Another reason, of course, is the code being produced is owned by the company and not the developers for a very good reason: it's the companies value.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8678405.post-23486388590102181002007-05-11T18:05:00.000+01:002007-05-11T18:05:00.000+01:00Stefan, I don't understand your comment. Do you m...Stefan, I don't understand your comment. Do you mean that, because one class does many things, many developers need access to it?<BR/><BR/>That would be covered by the automatic licencing. An interesting result is that because it would be easy for the owner of the file to re-use it, but not so easy for those who only edit it, or depend on it, developers would be more likely to write modular code.Ricky Clarksonhttps://www.blogger.com/profile/13845104548520132930noreply@blogger.comtag:blogger.com,1999:blog-8678405.post-80253508218292015072007-05-11T17:50:00.000+01:002007-05-11T17:50:00.000+01:00Nice idea, but not really applicable for team-base...Nice idea, but not really applicable for team-based development. Usually, larger project's functionalities don't restrict implementation to single classes but are also orthogonal to the class hierarchy, requiring developers to share access on classes. If it were different, using SVN or CVS would become really easy.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8678405.post-84867565913460729532007-05-11T10:32:00.000+01:002007-05-11T10:32:00.000+01:00Code written in my spare time is my own. I don't ...Code written in my spare time is my own. I don't add it to my work codebase, but as a library (in other words, I don't know whether I'd be obliged to transfer the copyright, so I avoid the situation).Ricky Clarksonhttps://www.blogger.com/profile/13845104548520132930noreply@blogger.comtag:blogger.com,1999:blog-8678405.post-43414771261017091602007-05-11T08:54:00.000+01:002007-05-11T08:54:00.000+01:00I seen a statistic that most coders will reuse off...I seen a statistic that most coders will reuse office work in future projects... which isn't hard to believe. The statistic didn't have what kind of code though, which would have been more interesting, because everyone has their preferred helper methods sitting in a file somewhere that they bring with them. Of course, the coder's contract may forbid this.<BR/><BR/>Out of curiosity, what does your contract say regarding code that you do in your "spare time"? And further, what if you create something in your spare time and then add it to your work codebase? Are you obliged to transfer the copyright?Sam Hallidayhttps://www.blogger.com/profile/09759635048859616269noreply@blogger.com