Loading ...
Sorry, an error occurred while loading the content.

Messages List

1092

Needs vs capability

Hi, Trying to understand the chapter 12 on needs vs capabilities interfaces, I have further elaborated my question on stack overflow. I hope someone can help
maatari01
Jul 16, 2014
#1092
 
1091

Essentials Skills for the Java Developer, Needs Vs Capabilities Inte

Hi, I'm trying to understand the main solution proposed to the challenge of applying the LAW OF DEMETER that the author mention by the end of this chapter. To
maatari01
Jul 15, 2014
#1091
 
1090

[ANN] Webinar this Monday on What Is Required At Scale

Sorry for the last minute email but I realized I had forgotten to announce this latest webinar in our What is Required at
Al Shalloway
Jun 20, 2014
#1090
 
1089

[ANN] Webinar on What Agile at Scale Requires. Wed 9am PDT

Sorry for the last minute email but I realized I had forgotten to announce this latest webinar in our Effective Agile At Scale Webinar
Al Shalloway
May 26, 2014
#1089
 
1088

[AS] two free webinars from Net Objectives. Executive's View of Agil

Apr 22, 9am Pacific. This Tuesday. An Executive's Guide to Agile
Al Shalloway
Apr 17, 2014
#1088
 
1087

Re: interface naming conventions

I’m teaching this week so have not had a chance to weigh in here, and even catching up looks daunting… but I’ll give my 2 cents. The problem, for me,
Scott Bain
Mar 11, 2014
#1087
 
1086

Re: interface naming conventions

If you want to decouple the test invocation from a specific test binding, try the template method approach that Scott actually gave a code sample for, I think
Amir Kolsky
Mar 9, 2014
#1086
 
1085

Re: interface naming conventions

I've been trying to promote the idea that a 3 layer model of UI, business layer, and database maps nicely to the Test Framework (MSTest in our case), test code
rstone1998
Mar 9, 2014
#1085
 
1084

Re: interface naming conventions

Frameworks are Adapters. In many cases frameworks are adapters to an outside entity (such as the user). This does not mean you do not need an adapter to
    Amir Kolsky
    Mar 9, 2014
    #1084
    This message has attachments
    1083

    Re: interface naming conventions

    Principles and design qualities. The principles on their own are useful for devs to follow. The reason is that they promote good code qualities. For example,
      Amir Kolsky
      Mar 9, 2014
      #1083
      This message has attachments
      1082

      Re: interface naming conventions

      Let’s start with the good, I agree with most of what you’re saying. Let’s discuss the partial class idea. We need to separate the Actor’s behavior from
        Amir Kolsky
        Mar 9, 2014
        #1082
        This message has attachments
        1081

        Re: interface naming conventions

        I’m coming to believe that “any” cohesion problems are, if not synonymous with SRP violations, different by so little that they could be treated
        rstone1998
        Mar 9, 2014
        #1081
         
        1080

        Re: interface naming conventions

        Writing an adapter should be very simple. It can by dynamic: Framework -> Adapter -> OurEntity. Or it can be static: Framework -> Adapter:OurEntity. (Your
        Amir Kolsky
        Mar 8, 2014
        #1080
         
        1079

        Re: interface naming conventions

        This is a fine point. ACTORS represents self-contained entities that have responsibilities which are inherent to the actors and define them. An ENCRYPTOR
        Amir Kolsky
        Mar 8, 2014
        #1079
         
        1078

        Re: interface naming conventions

        I didn't really address your comment on the Visitor pattern or some other type of adapter. While I like it, the problem with it may be my inability to write
        rstone1998
        Mar 8, 2014
        #1078
         
        View First Topic Go to View Last Topic
        Loading 1 - 15 of total 1,092 messages