Clik here to view.
Using Spring & Java Annotations to Inject Reusable Capabilities – Part II
In an earlier post, I wrote about using the Spring BeanPostProcessor to inject cross-cutting concerns. That can easily be extended to inject a proxy more transparently across all beans in the...
View ArticleClik here to view.
Getting Started With Reuse By Harvesting Existing Code
Many teams want to incrementally build a portfolio of reusable components so multiple projects can leverage them. This post will provide a list of potential areas to look for achieving systematic reuse...
View ArticleClik here to view.
Tools and Software Infrastructure for Systematic Reuse
A lot of readers have asked me to provide details on what tools and software infrastructure is needed to enable systematic reuse. That is a very good question and it is a critical enabler for building...
View ArticleClik here to view.
Systematic Reuse Success Factor #12 – Empower Tech Architects
They key word in the phrase “systematic software reuse” is “systematic” – that is what distinguished ad-hoc reuse from continuous, iterative, investment-oriented reuse that provides benefits across...
View ArticleClik here to view.
5 Tips to Ease Reusable Asset Integration
Resuable software assets need to be created and evolved with two perspectives – functional value and ease of integration. A library that offers little functional value and is difficult to integrate...
View ArticleClik here to view.
Software Reuse Quick Tip #30
Tip #30 – Enforce Consistent Dependencies via Maven Parent POM Maven parent POM can be used as a consistent mechanism to define dependencies and dependency versions. The module that defines common set...
View ArticleClik here to view.
Systematic Reuse Needs Extensibility
Accidental complexity is a real risk with trying to pursue systematic reuse . In trying to get reuse, you don’t want developers to jump through layers of indirection and complexity before they can...
View ArticleClik here to view.
5 Tips to Co-Create Reusable Components
Want to envision, design, and implement reusable software components that your development community will enthusiastically adopt? Co-create! Here are 5 tips to leverage co-creation when driving...
View ArticleClik here to view.
Paper On Incentive Compatibility and Systematic Reuse
This paper on Incentive Compatibility and Systematic Software Reuse provides several insights on incentives and organizational structure that will impact and influence systematic software reuse. A few...
View ArticleClik here to view.
Refactor Code Often, Continuously, Every Iteration
Refactoring is a way to improve code quality over time using incremental set of improvements – the idea is to increase the ability to make changes safer and faster and is not meant to deliver new...
View ArticleClik here to view.
5 Questions To Increase Systematic Reuse Effectiveness
Here are five questions to ask your teams to increase reuse effectiveness when evaluating a functional requirement: Is a requirement already met within the application or platform or is this the first...
View ArticleClik here to view.
Systematic Reuse Success Factor #13 – Constantly Revisit Assumptions
It is natural to get comfortable, perhaps too comfortable, with the state of your codebase. After all, it works and is probably meeting tangible business needs. However, if your team has to get the...
View ArticleClik here to view.
Software Reuse Quick Tip #31
Tip #31 – Inject Common Reusable Capabilities via JUnit Rules JUnit has an extremely useful extension mechanism – Rules. The @Rule annotation can help provide additional capabilities to your test...
View ArticleClik here to view.
Reduce Barriers to API Adoption
What is the one key aspect of making your APIs reusable? Simply put – reducing the barriers to adoption. It matters because your target audience – architects, developers, and project managers – are all...
View ArticleClik here to view.
Stop Planning & Start Harmonizing Implementations
You can wait for that dream initiative or project to build a whole new set of reusable components that will magically make your teams more productive. The only issue is – it is highly likely that it...
View ArticleClik here to view.
Ease Automated Testing of Reusable Components
In an earlier post, I listed reasons why automated tests are foundational for reuse. In this post, want to provide some approaches that will ease automated testing of your components. Mock API...
View ArticleClik here to view.
Don’t Implement Reusable Assets Unless Necessary
Resisting the temptation to implement a story is very hard for a dev team – it is all too easy to get carried away in introducing a new idea as a reusable asset. However, these are the moments where...
View ArticleClik here to view.
Tips for Identifying Reusable Candidates from Existing Code
Here are a few quick tips to examine your existing code to identify reuse candidates: Introduce Factory or Builder instead of repetitive boiler-plate code when constructing key objects. Several...
View ArticleClik here to view.
Software Reuse Quick Tip #32
Tip #32 – Fail the build when there is a test failure Systematic reuse needs automated tests – lots of them. Ensure that your continuous builds don’t keep running when they encounter a failing test –...
View ArticleClik here to view.
The Write Once Reuse Many Times Myth
How many times have you heard someone say – “we want to implement this once so we can reuse it over and over again…” – or some variation of this theme? The underlying assumption here is that it is...
View Article