exclusivity

 in context: the coding part of our optimization model's pretty much been taken over by andrew and ab, who do most of it and are fiercely protective of it. the rest of the scheduling team is like doop doop doop

. which leads to this conversation:

-------------------

Rustann: what do we have left to do?
besides a lot

me: haha
we could start on client slides
while andrew and ab talk in their Secret Coding Club
lol i kid
but i mean, might as well get it out of the way

Rustann: we could pass that off to winfield and dane
you think we could do EDD for glaze?

me:  you mean like connecting it to the matrix information?

Rustann: glaze has no washes i think
Rustann: we could form our own club

me: yeah let's do it
i'll bring the juice, you bring the cookies
we'd totally be way more awesome than their club
just sayin'.

Rustann: robes
!

me: oh damn
baller haha

Rustann: all or nothing
nut up or shut up


me: ok
we'll order the robes
you've convinced me

gmail status

Dane: Give me your data, i want to do things to it

02. Methodology

Yohan: Instead of putting "aiming for a solution", you should just put "solution". You want to be confident, not just hoping.
Dane: Title it "God, I hope this works."

01. powerpoint slides

Winfield: Should we call it "root problems"?
Jennifer: Well, problem is probably a bad way to word it since things like breakdown and utilization are part of the system and unchangeable.
Me: How about 'present issues'?
Rusty: No no, go with constraints. Constraints works.
Dane: That's not entirely true, though, because they're not really constraining you. They're just fucking you.


 lolz