Laws of Smalltalk Programming - Smalltalk

This is a discussion on Laws of Smalltalk Programming - Smalltalk ; Laws of Smalltalk Programming Any given Smalltalk program, when running, has to be migrated either to ..NET or JAVA. Laws of Smalltalk Programming, I Any software development in other languages cost at least 3x more. Laws of Smalltalk Programming, II ...

+ Reply to Thread
Results 1 to 4 of 4

Laws of Smalltalk Programming

  1. Default Laws of Smalltalk Programming

    Laws of Smalltalk Programming

    Any given Smalltalk program, when running, has to be migrated either to
    ..NET or JAVA.
    Laws of Smalltalk Programming, I

    Any software development in other languages cost at least 3x more.
    Laws of Smalltalk Programming, II

    If a program is useful, it will have to be changed.
    Laws of Smalltalk Programming, III

    If a program is useless, it will have to be documented.
    Laws of Smalltalk Programming, IV

    Double the number of programmers and you double the development time and
    quadruple the development costs.
    Laws of Smalltalk Programming, V

    If a program works properly, unit tests have to be added.
    Laws of Smalltalk Programming, VI

    Program complexity grows until it exceeds the capabilities of the
    programmers who must maintain it.
    Laws of Smalltalk Programming, VII

    In any team you will find at least one programmer, who produces more
    bugs than he removes.
    Laws of Smalltalk Programming, VIII

    Undetectable errors are infinite in variety, in contrast to detectable
    errors, which by definition are limited.
    Laws of Smalltalk Programming, IX

    Add only one unexperienced, imperative programmer to a smalltalk project
    and you double development time.
    Laws of Smalltalk Programming, X

    Have fun, Guido Stepken

  2. Default Re: Laws of Smalltalk Programming


    The title is off, it surely has to have 'Enterprise' or such in it to
    fit these laws.


    I would like to propose


    Teach a non-technical domain expert Smalltalk and your development time
    halves.
    Laws of Smalltalk Programming, XI


    You know the project is nearly finished when you gain functionality by
    removing large swaths of code.
    Laws of Smalltalk Programming, XII





    R
    -


    Guido Stepken wrote:
    > Laws of Smalltalk Programming
    >
    > Any given Smalltalk program, when running, has to be migrated either to
    > .NET or JAVA.
    > Laws of Smalltalk Programming, I
    >
    > Any software development in other languages cost at least 3x more.
    > Laws of Smalltalk Programming, II
    >
    > If a program is useful, it will have to be changed.
    > Laws of Smalltalk Programming, III
    >
    > If a program is useless, it will have to be documented.
    > Laws of Smalltalk Programming, IV
    >
    > Double the number of programmers and you double the development time and
    > quadruple the development costs.
    > Laws of Smalltalk Programming, V
    >
    > If a program works properly, unit tests have to be added.
    > Laws of Smalltalk Programming, VI
    >
    > Program complexity grows until it exceeds the capabilities of the
    > programmers who must maintain it.
    > Laws of Smalltalk Programming, VII
    >
    > In any team you will find at least one programmer, who produces more
    > bugs than he removes.
    > Laws of Smalltalk Programming, VIII
    >
    > Undetectable errors are infinite in variety, in contrast to detectable
    > errors, which by definition are limited.
    > Laws of Smalltalk Programming, IX
    >
    > Add only one unexperienced, imperative programmer to a smalltalk project
    > and you double development time.
    > Laws of Smalltalk Programming, X
    >
    > Have fun, Guido Stepken


  3. Default Re: Laws of Smalltalk Programming

    On Nov 3, 10:00 pm, Guido Stepken <step...@web.de> wrote:
    > Laws of Smalltalk Programming
    >
    > In any team you will find at least one programmer, who produces more
    > bugs than he removes.
    > Laws of Smalltalk Programming, VIII


    Especially true if there is only one programmer on the team.

    Mike


  4. Default Re: Laws of Smalltalk Programming

    Reinout Heeck schrieb:
    >
    > The title is off, it surely has to have 'Enterprise' or such in it to
    > fit these laws.
    >
    >
    > I would like to propose
    >
    >
    > Teach a non-technical domain expert Smalltalk and your development time
    > halves.
    > Laws of Smalltalk Programming, XI
    >
    >
    > You know the project is nearly finished when you gain functionality by
    > removing large swaths of code.
    > Laws of Smalltalk Programming, XII
    >


    Me stupido ... sorry i forgot ... agreed!

    Any other ideas?

    Have fun, Guido Stepken

+ Reply to Thread

Similar Threads

  1. Introduction to programming course using Smalltalk?
    By Application Development in forum Smalltalk
    Replies: 1
    Last Post: 11-20-2007, 02:02 PM
  2. Replies: 1
    Last Post: 05-31-2007, 05:41 PM
  3. Replies: 2
    Last Post: 05-29-2007, 01:17 PM
  4. Replies: 0
    Last Post: 12-13-2006, 04:36 PM