846 karma · joined May 15, 2010
$(document).on("click", "#foo", function(){...});
either
the takeaway would be that you should promote yourself and your work preemptively.
Or no keys on a phone.
Or is this university stuff? Or even spare time stuff?
class FooService : IFooService{} interface IFooService {}
where there is an interface with a single implementation. In this case, the "service interface" isn't a port, because it's not actually decoupled from the domain.
It has the potential to be one, but only if the FooService is extracted, dereferenced from the domain, and the application composes the FooService.
Saying "we need to make this into a port and adapter" gets the point across very quickly.
Think of P&A as terminology to help you disambiguate these use cases from the extremely overloaded words. If your team know these terms, it makes a lot of discussions a lot clearer.
The hexagon thing is a bit of a red herring IMO. I think of it as dependency inversion at the module level, rather than the class level.