Changes: A plug-in to show spelling alternation of the search phrase was added. A bug in the search server was fixed

estraier.sf.net

 > http://www.teamellen.com/ellen-article-2380.html
 > Early this morning, one of the Sony VAIO laptops that power
 > the critical information systems onboard B&Q - including
 > routing and navigation software - suffered a meltdown. The
 > VAIO's have survived 70 days without a glitch, despite continual
 > pounding onboard B&Q but last night's storm was the last straw
 > for one of the two hard disks. At 0750 Charles Darbyshire,
 > Technology Manager, received a call to report the failure and
 > just seven minutes later, MacArthur had replaced the hard disk
 > with a pre-start mirrored backup unit, re-configured the software,
 > and was up and running again - preparation counts!

www.erikveen.dds.nl/distributingrubyapplications/index.html

This URL points to the place where I’ve dumped my thoughts about building, packing and distributing Ruby applications. Theory and practice. The ultimate goal is to be able to distribute just one executable which contains both the application and the Ruby interpreter.

That’s achieved by the combination of Tar2RubyScript [1] and RubyScript2Exe [2].

It’s definitely worth reading if you have to distribute your Ruby applications!

gegroet, Erik V.

 [1] http://www.erikveen.dds.nl/tar2rubyscript/index.html
 [2] http://www.erikveen.dds.nl/rubyscript2exe/index.html

www.manageability.org/blog/stuff/official-struts-demise

As announced in the Apache News Blog that there will be no further work to develop Struts 2.x.

 From: Chris Pine <cpine@hellotree.com>
 Newsgroups: comp.lang.ruby
 Subject: [ANN] Ruby 2.0!
 Date: Mon, 24 Jan 2005 02:29:57 +0900

 Big news!

 Ruby 2 (a.k.a Ruby Secunda Kathrine Pine) was released January 22, 2005
 at 1:51:42 pm (PST) after a few hours of intense, last-minute debugging
 and deployment.  We've been working on this project for just over 9
 months and are quite pleased with the results!  (Well, my wife really
 did most of the work, though I *did* play a seminal role in the initial
 project conception phase.)

 <<< THE NAME >>>

 Ruby     -- named after our favorite language, of course!
 Secunda  -- our second child (after C), and the second Ruby
              (in the roman tradition of numbering your children,
                          e.g. "Quintus" and "Octavius")
 Kathrine -- named after the lead programmer on this project
             (a tradition in her ancestral development house)
             Pine     -- yes, our last name, but also Matz once told me that
                          "matz" is Japanese for "pine"!

 <<< FEATURES >>>
 * Powerful audio output (even on those little tweeters)
 * Net Wt. 9 pounds (or a little over 20k carats as Dave Thomas notes)
 * FIFO digestive queue
 * Ruby.length == 20 inches
 * UNBEATABLE copy protection
 * Dark brown hair
 * Just plain FUN!  (true to the Ruby lagacy)

 <<< KNOWN ISSUES >>>
 * FIFO queue occasionally behaves like a LIFO stack
 * Ruby.sleep(ALL_NIGHT) seems to resume unexpectedly
 * While C (her big brother) sends plenty of messages to Ruby,
   Ruby doesn't seem to respond to C calls.

 <<< SCREENSHOTS >>>
 Screenshots will soon be available here:
 http://pine.fm/FamilyPictures/?page=filter&year=2005&month=1

 Currently, though, we've only put up our pre-release screenshots (and
 around 4000 pictures of C).

  <<< DOWNLOADS >>>
  You wish!
  :)

  Chris

link

Nice slogan, too .. "Isn’t it nice when things just work?".

  I don't have a sample contract. The times I've worked this way the contracts
  have been verbal, not written.

  There were some comments about what to call these contracts. One analogy I
  found with the help of Greg Betty at Intelliware is "target costing". Target
  cost product development starts with a target cost (a $400 digital camera,
  for example). From that you can figure out how much you can pay to
  manufacture the product. The goal is to pack as much functionality as
  possible into the product given the price, either by reducing the cost of
  components or the cost of assembly. This process is called value
  engineering. I think Bill Wake's ideas about unbundling point to an
  effective way to do this in software development.

  You could write a target cost software development contract by specifying
  how much the contract would cost, along with the quality levels/practices
  and the process for choosing scope. The difference between fixed cost and
  target cost is that fixed cost contracts imply that the scope is fixed,
  while target cost contracts explicitly float the scope. One thing I like
  about target cost is that choosing scope is a value-added activity where
  choosing scope in fixed cost contracts is a transaction cost (the principle
  of opportunity at work).

  Kent Beck
  Three Rivers Institute

  #!/bin/bash
  lout -s <<END_OF_TEMPLATE | gv -
  @SysInclude{doc}
  @Document
  @InitialFont { Palatino Base 11p }
  //
  @Text @Begin
  @Verbatim @Begin
  @Include{"$1"}
  @End @Verbatim
  @End @Text
  END_OF_TEMPLATE

Then, the topic shifts to the problems of project management as Johanna tries to answer a tough question such as, "What is the greatest mistake you see project managers do most often?" which leads into an interesting discussion about multi-projecting and why it can pose a problem for your projects. Also, more interesting advice from Johanna emerges when asked to give advice for new team-leaders/managers Johanna also talks about her new book: Hiring The Best Knowledge Workers, Techies & Nerds. And why she wrote it in the first place. To finish it all off Johanna answers one of the questions each project manager should ask themselves every once in a while: "What is the worst mistake youve done as a manager?"

Johanna Rothman is a well-known consultant, speaker, and author on managing high-technology product development. During her decade-long consulting career, she has enabled managers, teams, and organizations become more effective applying her pragmatic approaches to the issues of project management, risk management, and people management. Shes helped Engineering organizations, IT organizations, and startups hire, manage, and release successful products faster. Her assessment reports have helped managers and teams create and execute action plans that help them improve their projects and their processes. She is a sought-after speaker and teacher in the areas of project management, people management, and problem-solving.

link

The key to become a good hacker is to work on what you love! :-)

 Finally, after what seemed to be an endless series
 of release candidates, I am happy to announce the
 final release of version 182-14. Happy New Year!

 This release of the One-Click Ruby Installer for
 Windows is built from Ruby 1.8.2 final. It includes
 OpenSSL, and upgrades RubyGems and FreeRIDE to their
 latest versions.

 You can download this release from:
 http://rubyforge.org/frs/?group_id=167

 Curt

 Changes Since 1.8.1-13:
 - This is a build of Ruby 1.8.2 final.
 - Added start menu shortcuts for the RubyGems
 RDoc Server, and for viewing the RDoc of
 all installed gems.
 - Added OpenSSL 0.9.7e
 - Added RubyGems 0.8.3
 - Added FreeRIDE 0.9.2
 - Updated FXRuby to 1.2.2
 - Upgraded Ruby-odbc to version 0.994
 - TCL/TK support no longer sets any environment
 variables.
 - Corrected missing OpenGL support.
 - Added Start Menu shortcuts to documentation
 on ruby-doc.org.
 - Eliminated the installer dialog message that
 warned you might need to reboot your system.
 This allows for unattended installs using the
 command-line arguments:
     /S /D=<install dir>
     - Changed the layout of the Windows registry
     entries.
     - Fixed a typo in a windows registry entry
     (bug 643).
     - Upgraded Expat to version 1.95.7
     - Upgraded DBI to 0.23

The Linux Virtual Server as an advanced load balancing solution can be used to build highly scalable and highly available network services, such as scalable web, cache, mail, ftp, media and VoIP services. link

 ruby -i.bak -pe 'sub "2004", "2005"' *

Stefan suggested:

 find . -print | xargs ruby ...
 :-)

This program allows you to record the output of any standard OSS program (one that uses /dev/dsp for sound) without having to modify or recompile the program. It uses the same idea as the esddsp wrapper from the Enlightened Sound Daemon (in fact, vsound is based on esddsp). That is, it preloads a library that intercepts calls to open /dev/dsp, and instead returns a handle to a normal file. It also intercepts ioctl’s on that file handle and logs them, to help convert the audio data from its raw form. Vsound then uses sox to convert the raw data to the desired file format.

The upshoot of this is that instead of playing sound to the sound card in your computer, the data is recorded to a file. This is similar to if you connected a loopback cable to the line in and line out jacks on your sound card, but no DA or AD conversions take place, so quality is not lost.

One use of vsound is to help convert real audio files to some other format. Since the real audio format is proprietary, and all we have is a player, we can use the vsound to create a wave file like so:

 vsound -t -f /data/dvdburn/LL2/s2.wav  realplay rtsp://18.39.0.30/ailab/mit-ll2-s2-09nov02-80k.rm

  ftp://ftp.ruby-lang.org/pub/ruby/1.8/ruby-1.8.2-preview4.tar.gz
  md5sum: 2f53d4dc4b24e37799143645772aabd0

  The final 1.8.2 will be out on December 25th (JST), unless any
  critical bugs will be found.
                                      matz.

www.mcs.vuw.ac.nz/comp/Publications/CS-TR-02-9.abs.html

Apparently, this has been believed by many as a hoax, and so has been linked to the famous Alan Sokal hoax (the paper "Transgressing the Boundaries: Towards a Transformative Hermeneutics of Quantum Gravity").

However I think it’s more like: a serious article written in a tongue-in-cheek style and talking about an unusual topic.

Other authors i know who are writing about postmodern programming, are Larry Wall (Perl) and Richard Gabriel (new online book "Patterns of Software"). These days I am attempting to read the latter.

Richard Gabriel’s work on software patterns, and for that matter, all the work on software patterns for the last decade, has been tremendously influenced by a book supposedly on Architecture (!!!), by Christopher Alexander, called "The Timeless Way of Building".

Both C.Alexander and R.P.Gabriel spend a lot of time on an elusive concept they call "Quality", which I immediately connected to Robert Pirsig’s "Zen And The Art of Motorcycle Maintenance" (1976), a classic I finally read this year. The connection between the two is quite large (Pirsig’s book even more revolves around that "Quality" thing). It has to do with attempting to define the undefinable, in particular, those aspects of a thing that make it good and/or beautiful but that, trying to approach them from a formal standpoint, slip through our fingers.

There are a bunch of other interesting aspects (IMHO) in all of those texts.