From westerman at purdue.edu Tue Aug 4 06:47:05 2009 From: westerman at purdue.edu (Rick Westerman) Date: Tue, 04 Aug 2009 09:47:05 -0400 Subject: [Purdue-pm] No August meeting Message-ID: <4A783BD9.9030706@purdue.edu> Sorry for the late notice. There is no meeting today. Our one scheduled speaker's talk can be summarized into a couple of minutes summary -- basically "Perl 6 does not compile on Fedora 11 Linux." No one else has signed up to speak nor have I pounded down the doors trying to get people to speak ... myself included! So let's see what we can do for the September meeting. Please come up with talks as you can. -- Rick Westerman westerman at purdue.edu Bioinformatics specialist at the Genomics Facility. Phone: (765) 494-0505 FAX: (765) 496-7255 Department of Horticulture and Landscape Architecture 625 Agriculture Mall Drive West Lafayette, IN 47907-2010 Physically located in room S049, WSLR building From westerman at purdue.edu Tue Aug 4 08:31:04 2009 From: westerman at purdue.edu (Rick Westerman) Date: Tue, 04 Aug 2009 11:31:04 -0400 Subject: [Purdue-pm] Schedule for the academic year Message-ID: <4A785438.3090007@purdue.edu> The meeting schedule for the academic year is every third Tuesday of the month, beginning Sept. 16, 2009 and ending May 18, 2010. Please note one exception: October 20 is not available so we are meeting on October 13. We will continue the brown-bag lunch format, 11:30 to 1:30 in WSLR 116. So that gives everyone 7 weeks or so to come up with a good talk for September. And if we have too many talks then the October meeting closely follows on September's meeting. -- Rick Westerman westerman at purdue.edu Bioinformatics specialist at the Genomics Facility. Phone: (765) 494-0505 FAX: (765) 496-7255 Department of Horticulture and Landscape Architecture 625 Agriculture Mall Drive West Lafayette, IN 47907-2010 Physically located in room S049, WSLR building From jacoby at purdue.edu Tue Aug 4 08:54:49 2009 From: jacoby at purdue.edu (Dave Jacoby) Date: Tue, 04 Aug 2009 11:54:49 -0400 Subject: [Purdue-pm] Schedule for the academic year In-Reply-To: <11191_1249399881_n74FVKfB007349_4A785438.3090007@purdue.edu> References: <11191_1249399881_n74FVKfB007349_4A785438.3090007@purdue.edu> Message-ID: <4A7859C9.9040307@purdue.edu> Rick Westerman wrote: > And if we have too many talks then the October meeting > closely follows on September's meeting. If only we had that problem. -- Dave Jacoby Address: WSLR S049 Genomics Core Programmer Mail: jacoby at purdue.edu Purdue University Jabber: jacoby at jabber.org Phone: hah! From westerman at purdue.edu Tue Aug 4 10:13:28 2009 From: westerman at purdue.edu (Rick Westerman) Date: Tue, 04 Aug 2009 13:13:28 -0400 Subject: [Purdue-pm] More on ... Schedule for the academic year Message-ID: <4A786C38.8060707@purdue.edu> > The meeting schedule for the academic year is every third Tuesday of > the month, beginning Sept. 16, 2009 and ending May 18, 2010. Of course I meant beginning Sept. 15th which is a Tuesday. > Please note > one exception: October 20 is not available so we are meeting on > October 13. We will continue the brown-bag lunch format, 11:30 to > 1:30 in WSLR 116. -- Rick Westerman westerman at purdue.edu Bioinformatics specialist at the Genomics Facility. Phone: (765) 494-0505 FAX: (765) 496-7255 Department of Horticulture and Landscape Architecture 625 Agriculture Mall Drive West Lafayette, IN 47907-2010 Physically located in room S049, WSLR building From gribskov at purdue.edu Tue Aug 11 06:53:03 2009 From: gribskov at purdue.edu (Michael Gribskov) Date: Tue, 11 Aug 2009 09:53:03 -0400 Subject: [Purdue-pm] False Hubris code example Message-ID: <4A8177BF.3010405@purdue.edu> Why do people consider code like this to be "good"?? my $text = do { local( @ARGV, $/ ) = $file ; <> }; while it is compact, it is to my mind obscure and uneccessarily difficult to understand, succeeding by side effects of the overt code. A whole program written like this is a nightmare. IMO of course -- Michael Gribskov Professor of Biological Sciences Purdue University Lilly Hall of Life Sciences 915 W. State Street West Lafayette IN 47907-2054 gribskov at purdue.edu vox: 765.494.6933 fax: 765.496-1189 Calendar From gizmo at purdue.edu Tue Aug 11 08:27:00 2009 From: gizmo at purdue.edu (Joe Kline) Date: Tue, 11 Aug 2009 11:27:00 -0400 Subject: [Purdue-pm] False Hubris code example In-Reply-To: <30427_1249998798_n7BDrHNS009693_4A8177BF.3010405@purdue.edu> References: <30427_1249998798_n7BDrHNS009693_4A8177BF.3010405@purdue.edu> Message-ID: <4A818DC4.9080000@purdue.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael Gribskov wrote: > Why do people consider code like this to be "good"?? > > my $text = do { local( @ARGV, $/ ) = $file ; <> }; > > while it is compact, it is to my mind obscure and uneccessarily > difficult to understand, succeeding by side effects of the overt code. > A whole program written like this is a nightmare. IMO of course > Do you consider the rest of chromatic's program "bad" then? I would probably just use File::Slurp unless some constraint wouldn't let me. The one line is very idiomatic perl. Just some very deep understanding of what perl can do. joe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org iD8DBQFKgY3Eb0mzA2gRTpkRAni8AKCh/zbPI84hZVAQlJi3ZM4h/GtYOwCgjIY5 BrIWGKDQcpZkB+uXSkXtpOA= =VL6K -----END PGP SIGNATURE----- From gribskov at purdue.edu Tue Aug 18 06:37:32 2009 From: gribskov at purdue.edu (Michael Gribskov) Date: Tue, 18 Aug 2009 09:37:32 -0400 Subject: [Purdue-pm] False Hubris code example In-Reply-To: <4A818DC4.9080000@purdue.edu> References: <30427_1249998798_n7BDrHNS009693_4A8177BF.3010405@purdue.edu> <4A818DC4.9080000@purdue.edu> Message-ID: <4A8AAE9C.5030004@purdue.edu> I would never consider a person's code to be bad, only particular code. IMO, if it takes an experienced programmer a significant amount of time to just figure out what it does AND there is no over-riding need for efficiency, I consider it to be bad. Preferably, code should be as easy to understand as a written sentence. Almost all the effort in software development is in the maintenance phase of the life cycle, code that shows your programming chops by using obscure but "very idiomatic" parts of the language that require "deep understanding" make maintenance more difficult. the slurp code below definitely meets Wall's definition of false hubris == "unnecessarily dense, unreadable code". what i specifically don't like: 1) assigning value to @ARGV, which is, after all, supposed to represent the command line 2) assigning value of undef to $/ as a side effect of unbalanced left and right hand sides of assignment 3) by my timing with NYTProf, the compressed code is actually a little over 20% slower than the following { local $/ = undef; open( IN, "<$file" ); $text = ; close IN; } 4) the compressed code is 52 characters, the more understandable (IMO) code above is only 70. Why make it difficult to understand to save 18 characters of typing > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > Michael Gribskov wrote: >> Why do people consider code like this to be "good"?? >> >> my $text = do { local( @ARGV, $/ ) = $file ; <> }; >> >> while it is compact, it is to my mind obscure and uneccessarily >> difficult to understand, succeeding by side effects of the overt code. >> A whole program written like this is a nightmare. IMO of course >> >> > > Do you consider the rest of chromatic's program "bad" then? > > I would probably just use File::Slurp unless some constraint wouldn't > let me. The one line is very idiomatic perl. Just some very deep > understanding of what perl can do. > > joe > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (GNU/Linux) > Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org > > iD8DBQFKgY3Eb0mzA2gRTpkRAni8AKCh/zbPI84hZVAQlJi3ZM4h/GtYOwCgjIY5 > BrIWGKDQcpZkB+uXSkXtpOA= > =VL6K > -----END PGP SIGNATURE----- > _______________________________________________ > Purdue-pm mailing list > Purdue-pm at pm.org > http://mail.pm.org/mailman/listinfo/purdue-pm > -- Michael Gribskov Professor of Biological Sciences Purdue University Lilly Hall of Life Sciences 915 W. State Street West Lafayette IN 47907-2054 gribskov at purdue.edu vox: 765.494.6933 fax: 765.496-1189 Calendar From westerman at purdue.edu Mon Aug 31 12:33:46 2009 From: westerman at purdue.edu (Rick Westerman) Date: Mon, 31 Aug 2009 15:33:46 -0400 Subject: [Purdue-pm] Meeting in 2 weeks plus 1 day Message-ID: <4A9C259A.6040709@purdue.edu> A reminder that our next meeting is Tuesday, Sept 15th. 15 days away. If you have a talk to give then please sign up. Mark just got done with the annual activities fair and may have picked up some new Perl programmers who will attend our meetings. -- Rick Westerman westerman at purdue.edu Bioinformatics specialist at the Genomics Facility. Phone: (765) 494-0505 FAX: (765) 496-7255 Department of Horticulture and Landscape Architecture 625 Agriculture Mall Drive West Lafayette, IN 47907-2010 Physically located in room S049, WSLR building