canonical-ci-engineering team mailing list archive

[Ursula Junque <ursula.junque@xxxxxxxxxxxxx>]

Hi,

On Wed, Apr 1, 2015 at 3:20 PM, 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.
>
> The old adage is really true, there is nothing quite so long lived as a
> temporary solution.
>
> Please take the time to do things properly instead of piling up crap that
> just needs to get fixed later.
>

I think this is what we are doing, that's why this discussion is happening.
Also there's not only one way of "doing things properly", "proper" might
vary depending on the context you have. You have CI train and we can
understand your frustration, but please, don't extrapolate that to
everything that has CI in it. :)

Now for my two cents. :)

I think Celso has a point: we have lots of things in place but very few of
them seem to be "production ready". We might not be giving proper attention
to finishing things before starting others, *as a team*. It was even raised
during the retrospective that if we finished a component and everything
that entails, adjusted it and then moved to the next, we would end up with
better results. Not doing this was one of the reasons we had things
partially completed last sprint, and I believe we still have time to avoid
the same to happen in this one.

I'm not saying this is not an important discussion to have, I'm only
questioning if this is the most important discussion to have now. If you
compare it to the other things we still have to do, is this really the most
urgent problem we have? Is it that certain that we will have problems and
that a library *now* is a solution to these? If the answer is yes and we
have data to back it up then fine, if not, we might have other problems
that need addressing first. Again, I'm only raising another aspect to
consider the priority of this discussion, not saying it's not relevant at
all.




> I think we as a company have maxed out our technical debt load and need to
> pay it down sooner rather than later.
>
> --
> Mailing list: https://launchpad.net/~canonical-ci-engineering
> Post to     : canonical-ci-engineering@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~canonical-ci-engineering
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Úrsula Junque
Ubuntu CI Engineer

ursula.junque@xxxxxxxxxxxxx
ursinha@xxxxxxxxxxx
ursinha@xxxxxxxxxx

Ubuntu - "I am what I am because of who we all are."
Linux user #289453 - Ubuntu user #31144