On Thursday 11 June 2009 08:47:39 Jonathan Ben Avraham wrote:
> C'mon Shlomi, give the guy a break. He said he's a former professor. What
> can you expect?
I don't know - that he'll be intelligent enough to follow E-mail etiquette?
;-)צ
Regards,
Shlomi Fish
>
> - yba
>
> On Wed, 10 Jun 2009, Shlomi Fish wrote:
> > Date: Wed, 10 Jun 2009 23:52:24 +0300
> > From: Shlomi Fish <shlo...@iglu.org.il>
> > To: linux-il@cs.huji.ac.il
> > Cc: shlomo bauer <shlomoba...@gmail.com>
> > Subject: Re: software engineering project
> >
> > Hi Shlomo!
> >
> > This is the second time you've:
> >
> > 1. Replied to a message.
> >
> > 2. Without quoting any of the original. (May be considered as
> > top-posting.)
> >
> > 3. While changing the original subject line completely (without doing
> > [was Re:]).
> >
> > 4. While starting a completely new thread in the process.
> >
> > I wonder if it's your user agent (which does not identify itself in the
> > User- Agent: header) or if you are doing something completely off. In any
> > case, please stop, as this is bad E-mail netiquette. Quote the message
> > and reply to each part of the message after the quoting. Keep the
> > original subject with the additional "Re:". And don't start a completely
> > new thread.
> >
> > Regards,
> >
> > Shlomi Fish
> >
> > On Wednesday 10 June 2009 23:28:57 shlomo bauer wrote:
> >> HI,
> >>
> >> As a former professor teaching software engineering, I was bit
> >> surprised by your posting -- perhaps I misunderstood your intent.
> >>
> >> Although software engineering in the large is more about process than
> >> code that's not always the case. For example, software systems
> >> benefit from code refactoring. An example of refactoring
> >> is finding sequences of code that are repeated in a variety of places
> >> and replacing them with
> >> a function call.
> >>
> >> The resulting code has the same "meaning" but a different text -- the
> >> refactored code is easier to understand, etc.
> >>
> >> Writing a compiler inandofitself is not a software engineering project.
> >>
> >> A good project for you might be to look at a tool like valgrind.
> >> Consider how such tool can be incorporated in the software development
> >> life-cycle. Having done so, you might then try to
> >> find a taxonomy of defects (NIST in america published) by frequency,
> >> severity, etc. The
> >> interesting question then is what set of tools would be useful in
> >> helping uncover defects likely
> >> to be encountered by customers as well as ones that are catastrophic.
> >>
> >> If you really want to write code. why not do a comparative study of
> >> perl and haskell for a variety of scripting. Why these two? Because
> >> haskell was a big win for perl 6 (I'll leave it to you to find out
> >> why). from a software engineering perspective, language selection
> >> should be based on something more than, "all our code is in perl."
> >>
> >> Shlomo
> >>
> >> _______________________________________________
> >> Linux-il mailing list
> >> Linux-il@cs.huji.ac.il
> >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
--
-----------------------------------------------------------------
Shlomi Fish http://www.shlomifish.org/
My Aphorisms - http://www.shlomifish.org/humour.html
God gave us two eyes and ten fingers so we will type five times as much as we
read.
_______________________________________________
Linux-il mailing list
Linux-il@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
