Master Sarkela (was: Help with FFI structure pointer)

nicolas cellier ncellier at ifrance.com
Wed Aug 2 21:38:17 UTC 2006


i agree that this must increase reuse and productivity.
We all would like to do such code mining job: the pressure must be lower 
because productivity is indirect. Pleasure to program without constraints...
If John really convinced someone, don't expect him to change job soon.

Nicolas


Le Mercredi 02 Août 2006 23:19, Ron Teitelbaum a écrit :
> > From: Andreas Raab
> > Sent: Wednesday, August 02, 2006 8:26 AM
> >
> > Ron Teitelbaum wrote:
> > > <apicall: MyStruct 'MyAPICall' (long) module: 'my.dll'>  and sending in
> >
> > nil.
> >
> > > And
> > > <apicall: MyStruct 'MyAPICall' (MyStruct) module: 'my.dll'>  <- this is
> >
> > so
> >
> > > cool!  I assume that Andreas wrote this code, it is beautiful!
> >
> > I did write the code but credits where credits are due: The design has
> > been *heavily* influenced by John Sarkela at the time who happened to
> > work with the customer and had done a similar design before (I think it
> > was for V but I don't quite remember).
>
> I interviewed John a number of years back and then fought like you wouldn't
> believe to get him hired on.  He didn't want to move and the company was
> foolish enough to think that mattered.  He agreed to 1 week a month which I
> thought was great.
>
> I was very impressed with his comments about code mining, refactoring and
> packaging.  His concept was a code miner or a team of miners should be
> responsible for reviewing all the code that goes into a system, that there
> are a number of hidden jewels that should be mined, cleaned up, reinserted
> if the same problem has been solved multiple times, and then communicated
> to the development team.  He believed that reliable complex programs could
> be built by better organization and communication during the development
> lifecycle.  He believe that the resulting stability, the expert review of
> core components, and the increased productivity from reuse as the system
> developed would pay for the code miners.  Having built some very large
> programs myself, and seeing the code that has gone in by others, and
> spending nights fixing problems on live systems I know he is right.  The
> concept would have made a great book and would have been more productive
> then pair programming!  (Don't get me started)
>
> I'm really sorry I didn't get the chance to work with him.  Where is he
> now?
>
> Ron Teitelbaum
> President / Principal Software Engineer
> US Medical Record Specialists
> Ron at USMedRec.com




More information about the Squeak-dev mailing list