POC stands for Proof Of Concept. Even though the title says about agile projects, POC are performed in other environments as well. I feel more confident considering them in the agile area. Certain forms of POC are a must regardless of methodology. It is almost not possible to build complex solution with no research. Some projects have an opportunity to use lessons learned from others. POC are less or more expensive. They are the initial investment to research feasibility before running a project. This post focuses mainly on POCs in software development projects in agile environments.
This post is on the Low of Demeter (LoD) in OO services implementations. The goal here is to take into account exemplary implementation in Java and consider it how it respects the Low of Demeter. Thanks to the code examples it is easier imagine how the LoD may affect implementation. Knowing the practical usage of the Low it will be more convenient designing and implementing solutions based on best practices. LoD prefers loose coupling and allows creating more maintainable code. The use case follows a simple service to transfer money between two accounts.
This post takes into account Cargo cult programming. The purpose is to get familiar with the leading definition and consider how does it occur in real life and how to handle it. The term is mostly used as Cargo cult programming however Cargo cult software engineering is more meaningful when it comes to software development. The term provides negative approaches to software engineering. It says what is bad. Correct implementations should avoid practices given in the definition.
Some time ago Adam Bien published on his blog the recording of the presentation delivered by him on the 33rd Degree Conference 2014 in Kraków. I was on the conference and this is the presentation I most liked. The exact title of the show is Rethinking Packaging, Modularization, Interfaces with Plain Java EE 7.