communication Archive

  • The adoption of reflection into main-stream programming tools and languages over the last six or seven years gave developers almost telepathic powers, allowing us to instantly understand any object without having to read through 200 pages of boring manuals. Code insight, instellisense, class browser, or whatever the feature is called...

    Documentation for Telepathic Developers

    The adoption of reflection into main-stream programming tools and languages over the last six or seven years gave developers almost telepathic powers, allowing us to instantly understand any object without having to read through 200 pages of boring manuals. Code insight, instellisense, class browser, or whatever the feature is called...

    Continue Reading...

  • A friend of mine has a problem – his team worked for months on a big system with great success, marvellous technical achievements and a very elegant architecture. However, the users don’t share his enthusiasm. They don’t appreciate the architecture, flexibility and openness to change. Somehow, they seem ‘blinded by...

    Blinded by the user interface

    A friend of mine has a problem – his team worked for months on a big system with great success, marvellous technical achievements and a very elegant architecture. However, the users don’t share his enthusiasm. They don’t appreciate the architecture, flexibility and openness to change. Somehow, they seem ‘blinded by...

    Continue Reading...

  • From the naïve view of an average enterprise software developer, the situation today is a bit insane - most customers will always choose more functionality and faster delivery over testing and documentation - not to mention GUI polishing. They will look you in the eye, tell you that they sincerely understand the software will have problems once it is live, and then come back furious when the software does not work. As if we were not all speaking the same language,  somewhere the meaning of 'it will have problems' gets lost in translation. Or maybe it's not the definition of 'problems', but the definition of 'done', or maybe developers and customers really come from different planets...<!--more-->

    Developers are from Magrathea, Customers are from Ursa Minor Beta

    From the naïve view of an average enterprise software developer, the situation today is a bit insane - most customers will always choose more functionality and faster delivery over testing and documentation - not to mention GUI polishing. They will look you in the eye, tell you that they sincerely understand the software will have problems once it is live, and then come back furious when the software does not work. As if we were not all speaking the same language, somewhere the meaning of 'it will have problems' gets lost in translation. Or maybe it's not the definition of 'problems', but the definition of 'done', or maybe developers and customers really come from different planets...

    Continue Reading...