canonical-ci-engineering team mailing list archive

[Thomi Richards <thomi.richards@xxxxxxxxxxxxx>]

Hi Robert,

On Thu, Apr 2, 2015 at 7:20 AM, Robert Park <robert.park@xxxxxxxxxxxxx>
wrote:

> On Apr 1, 2015 6:01 AM, "Celso Providelo" <celso.providelo@xxxxxxxxxxxxx>
> wrote:
> > And we should, at least, think about the fact that the services (and
> > the library) code is disposable. It's not meant to live forever, we
> > still want to be able to drop one or more services off and re-write
> > them entirely with some other technology if there is a need.
>
> I need to really strongly disagree with this point. We're entering Year
> Two of the temporary Google spreadsheet that was only meant to last a
> couple months and is literally crumbling under the load we've put on it.
>

Good Point.

However, I don't think "temporary" and "good" are mutually exclusive.
Ideally we could write a uSevice in < 100 lines of code, and have the cost
of throwing it away and re-implementing it be so low that we can, if we
want to, rewrite it. With a high quality library of reusable components, we
can have our services be "temporary" _and_ "good".

Cheers,
-- 
Thomi Richards
thomi.richards@xxxxxxxxxxxxx