Not copyrighting code and then reusing functions later
I’m coding something for my job to copy directories and then use regex to make all the filenames uniform. I’m an undergrad student programmer for my university and I’m not sure what a professional coder would consider reasonable in this case. My job is mostly to implement mathematical research. The current assignment is outside what I’ve been doing and seems like it would be really useful to have some of the functions available in case I (most likely) encounter a similar assignment at some point in my career in the future. It’s going to be really useful because the current filenames are so screwed right now that the admin assistants can’t really keep up (and even trying to do so might just cause more human error). I’m thinking that it may not overall be useful outside the current assignment because the regex will be so customised to the way the file are incorrectly named.
Where in computer science education does “reuse and integration” find comprehensive coverage? [closed]
Closed 9 years ago.
Where in computer science education does “reuse and integration” find comprehensive coverage? [closed]
Closed 9 years ago.
Where in computer science education does “reuse and integration” find comprehensive coverage? [closed]
Closed 9 years ago.
Where in computer science education does “reuse and integration” find comprehensive coverage? [closed]
Closed 9 years ago.
Where in computer science education does “reuse and integration” find comprehensive coverage? [closed]
Closed 9 years ago.
TDD and code reusability
Let’s say that I’ve been iterating over my feature with TDD. After several red-green-refactor cycles, I ended up with a nicely polished implementation with a part of the SUT encapsulated into some abstraction that provides a reusable piece of logic. There are a bunch of tests that support this piece of reusable logic.
Resolving dependencies independently of the IoC container
I’m working on a component, let’s call it MyComponent
, which is intended to be used by various applications. These applications will get MyComponent
as a NuGet package for instance.
What are the disadvantages of self-encapsulation?
Direct references to variables severely limit the ability of programmers to refine existing classes. The programming conventions described here structure the use of variables to promote reusable designs. We encourage users of all object-oriented languages to follow these conventions. Additionally, we strongly urge designers of object-oriented languages to consider the effects of unrestricted variable references on reusability.
What are the disadvantages of self-encapsulation?
Direct references to variables severely limit the ability of programmers to refine existing classes. The programming conventions described here structure the use of variables to promote reusable designs. We encourage users of all object-oriented languages to follow these conventions. Additionally, we strongly urge designers of object-oriented languages to consider the effects of unrestricted variable references on reusability.