decoupling

I am attempting to apply the Strategy pattern to a particular situation, but am having an issue with how to avoid coupling each concrete strategy to the context object providing data for it. The following is a simplified case of a pattern that occurs a few different ways, but should be handled in a similar way. We have an object Acquisition that provides data relevant to a specific frame of time - basically a bunch of external data collected using different pieces of hardware. It's already too large because of the amount of data it contains, so I don't want to give it any further

I recently came across Robert Martin's (Uncle Bob) keynote on how to structure a rails app based on use-cases. I found this very interesting. Here is the link to the keynote: Architecture: the Lost Years Here is a sample project that structures the app based on the principles mentioned by Robert Martin in his keynote: Guru Watch I was wondering if there were well established rails applications out there that are structured in such fashion ( Use Case Driven Approach / Entity-Control-Boundary architecture / decoupling back end from front-end ) Well, I can't share the code, but I can point you to

As someone who has tried to find a way to help content authors develop and maintain big web sites by creating (HTML) components for years, I'm really excited to see web components gaining tracction at w3c, google and mozilla. But it seems to me that, there is no measure against javascript library bloat in the specifications. Say that I develop component A which has a dependency for underscore.js and want to use components B and C which have dependencies on lodash.js version 1.*, etc. I don't see any way to flag dependencies and library versions. This could lead to huge library bloat when we

I am building an Android App using MVVM and DataBinding. And I have a function inside my ViewModel that starts an Activity. Is it okay to have an onClick call inside a ViewModel? Like this. public class MyViewModel { public void onClick(View view, long productId) { Context context = view.getContext(); Intent intent = new Intent(context, ProductDetailActivity.class); intent.putExtra("productId", productId); context.startActivity(intent); } } And in my XML: ... android:onClick="@{(v) -> viewModel.onClick(v, viewModel.product.id)}"> Or would it be a best practice to move it to the View and call

What are Cohesion and Decoupling? I found information about coupling but not about decoupling. ant That article from Aaron is very good for understanding, also I'd recommend that you read manning publications Spring in Action book, they give very good examples on how the spring solves that problem it will definitely improve your understanding of this. EDIT : I came accross this in this great book called Growing object oriented software guided by tests : Coupling : Elements are coupled if a change in one forces a change in the other. For example, if two classes inherit from a common parent,