I hope you get a chance to join the first Cal Poly Authors event of this year: it starts at 10 am!
The President’s Leadership Council (PLC) is an expanded body this year: it fills UU220 now (it used to fit in a conference room). This week I attended the first PLC meeting of the year. It included an overview of the latest campus master plan, with more detail about the “core” than we’ve seen before, including concepts for moving people around the perimeter of the core using transit loops, and the potential for a residential ‘village’ along Brizzolara (aka Brizziolari) Creek – with Trader Joe’s-scale food shopping for the up to 16,000 students envisioned as residents on campus by 2035. The core has a strong emphasis on blended formal and informal learning, and cross-college interactions.
Conny and her team have been putting the final touches on this year’s Kennedy Library Annual Publication before it goes to press. I am pretty excited about how it’s coming together. When you get your copy you’ll see a lot about the library’s student assistants and the work they do that has lasting impact on other students. SLAC is another source of ideas and long-term impact. We are really lucky to have an amazing library advisory board (formerly “LITAC”) , and I’m excited that they’ll get to see the library in full gear, visit our iDi showcase, and talk with members of the Cal Poly community about how libraries are transforming (thanks to Cheryl for this link).
I’ve been reading about something called “Conway’s Law.” It states that, “organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations,” and that “the interface structure of a software system will reflect the social structure of the organization(s) that produced it.” [ref] This means that “tightly coupled” organizations will produce more tightly coupled (less modular) software designs. Break a team into three subgroups and they’re likely to produce a three-part system. Open source projects tend to produce highly modular software. With less code. What is the implication? One may be that “We should model our teams and our communication structures after the architecture we want.” An interesting book looks at patterns of organization and software development. I’m looking at our website now: what does it says about how we are organized? And how will Conway’s Law apply to the ULMS?
Have a great weekend,