#software reuse

[artofswreuse-blog]

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 continue running when they encounter a failing test. If you are using Maven, you can use the surefire plugin configuration as shown below:

[...] org.apache.maven.plugins maven-surefire-plugin false [...]

View On WordPress

[artofswreuse-blog]

Don't Implement Reusable Assets Unless Necessary

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 you must pause and ask yourself a few basic questions before rushing to write code:

Is this a one-off requirement or part of a recurring theme? Remember – when in doubt, don’t plan for reuse but…

View On WordPress

[artofswreuse-blog]

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 will be just that – a dream. Instead of planning for…

View Post

[artofswreuse-blog]

Address 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 trying to deliver value to their clients. Iteration…

View Post

[artofswreuse-blog]

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 full value out of it – the fair and ongoing return on…

View Post