Recorded at:

Heresies and Dogmas in Software Development

Sections

Architecture & Design

Topics

Strange Loop 2011 ,

Strange Loop ,

Design Pattern ,

REST ,

Enterprise Architecture ,

Object Oriented Design ,

Conferences ,

Patterns ,

Design ,

Architecture ,

CORBA ,

ORM

Share |

RELATED Research

1. Back to top

   Strange Loop

   by Alex Miller

   If you're interested in other upcoming videos from Strange Loop, the full release schedule is here and all slides are here. If you want to be notified about Strange Loop announcements in the future, sign up for the mailing list.

   Reply

2. Back to top

   Nice talk

   by Duraid Duraid

   The principle that I use, which I think holds for all these examples, is: a software solution lies in the middle between the problem domain (user stories, requirements, etc) and the solution domain (database, functional, OO, ORM, REST, CORBA, etc). The closer to the problem domain, the better solution it is albeit less efficient (in general) and vice versa.
   
   It's easy to see how this applies to the goto statement.
   
   In regard to the object middleware and the idea of functional 'wrappers', I think that's a completely wrong idea. I don't think the purpose of functional programming is to remove the need for object middleware (or object models) but the idea is to replace object models with a functional models that claim to have better composability, reusablity and closer representation of the problem domain but definitely not in order to gain efficiency. For efficiency you just need to be closer to the solution domain, or in other words, closer to the machine and not use functional nor object programming but C or assembly.

   Reply

3. Back to top

   All edges, no body

   by William Cherry

   It seemed that a lot of the advice was based on edge cases. Yes, there are edge cases where a goto makes sense, 99.5% of the time it makes code harder to read and can introduce subtle bugs (e.g. jumping over cleanup code). Yes, writing raw SQL can make your app faster. But raw SQL is harder to understand then a well defined method name. If you need to raw SQL in spots to get the speed that you need then use the ORMs ability to drop down to the native level in that one section.
   
   And remember that these "premature optimization" are going to be maintained by the new intern and you don't want him thinking that a goto would be perfect to fix that stack overflow.

   Reply

4. Back to top

   Identifiers With Spaces

   by Ryan Scheel

   There are cases where spaces in identifiers are useful. Javascript has the same property.
   
   var o = {
   "identifier with spaces" : function () { return 0; }
   };
   
   console.log(o["identifier with spaces"]);

   Reply