[LAU] How can we convert money to fixing bugs in software?

Renato rennabh at gmail.com
Mon Jul 23 14:40:14 UTC 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, 21 Jul 2012 17:19:12 +0100
Folderol <folderol at ukfsn.org> wrote:

> On Sat, 21 Jul 2012 12:11:56 -0400
> Paul Davis <paul at linuxaudiosystems.com> wrote:
> 
> > On Sat, Jul 21, 2012 at 10:52 AM, Alexandre Prokoudine <
> > alexandre.prokoudine at gmail.com> wrote:
> > 
> > > On Sat, Jul 21, 2012 at 6:41 PM, Charles Henry wrote:
> > >
> > > > Also, you never know how long you'll spend working on a
> > > > problem, until you actually do it.
> > >
> > > Not only that. It's also quite possible that users will never
> > > collect the amount of money required to implement or fix
> > > something.
> > >
> > 
> > its even worse. even if you can tell how long you will spend fixing
> > a problem, you don't find out till you've done 90% of the fix
> > already.
> 
> This is the exact parallel of the situation with electronic repairs.
> The number of times I've been asked for a repair estimate... and the
> customer *never* believes it takes 5 hours to find an O/C resistor or
> that actually finding it *is* the fix.
> 


All reasonable points; while I think that the idea still could work,
at least in part, I am now convinced that my time is actually better
spent trying to learn some more programming... unfortunately the little
I know of C is of no help with C++ projects like seq24

cheers,
renato
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQEcBAEBAgAGBQJQDWJSAAoJEBz6xFdttjrf458H/28prFfWYLuKjOrFW1YqvU8I
Yw+sBm1VgeHIrLoOGbR3xYFFst3L1606fgjkmeLmaLqa5xPwBbpbY+/pPeIfFox9
+f08WoIcNXiMdJPjr06+6Og2+FPbTYW9QMuO1yqn8nGwMIiMMMG+9JhWc6ugt7pW
H+rLdIOIoZtzjYxZ01Otnb8eCnInRDPEozf6+JpoTDsTkzSPLd1u6BJzG/HuaBYx
QUbPXCyzaHQ9oMqcqsHfSd3BxCMVbT+AXGCrsvTUhdXzuVsqPWMZjuhuTXD8VAyq
PEXnP3i5NoJULDc5r0V5Yq0FFv1Q5YkfpTma8E0rC6D2f6y0+frRwPI3ObIpa4U=
=qHPb
-----END PGP SIGNATURE-----


More information about the Linux-audio-user mailing list