Girvetz Hall - Room 1119

Now, more than ever, IT professionals are feeling overwhelmed by the number and complexity of tools available to them. From Kuberneties to Teraform, Chef to Ansible, It can sometimes be difficult to tell where one tool ends and another begins. With such overlap and complex integrations, it becomes necessary to change the way you reason about and chose your technology portfolio.

This talk does not suggest or advocate for any particular set of tooling, but rather discusses some methods of breaking down—

At the request of the presenter, this session was not recorded. - UCTech 2019 Planning Committee
 

By mid-2016, UCSB had worked for 4 years to implement UCPath.  Although 13 staff were allocated to the program, none of the 126 business process designs or 50 interfaces were complete, and over 85 departments still used paper timecards.  After changing how we managed the program, UCSB drastically accelerated its deployment schedule and completed deployment in September 2018. 

In this—

Release Toggles allow incomplete and un-tested codepaths to be shipped to production as latent code which may never be turned on.  These are feature flags used to enable trunk-based development for teams practicing Continuous Delivery.  They allow in-progress features to be checked into a shared integration branch (e.g. master or trunk) while still allowing that branch to be deployed to production at any time. Release Toggles allow incomplete and un-tested codepaths to be shipped to production as—

Data Science and Computer Science courses with large enrollments face grading challenges due to the size and nature of their assignments. In our university’s Introductory Data Science class, every student submission is broken up into auto-graded code sections and manually graded response sections to be separately graded, then merged to produce a final grade. In response, our university’s Department of Data Science has developed a grading solution pipeline to productionize this process, in addition to auto-grading software and—

At the request of the presenters, this session was not recorded. - UCTech 2019 Planning Committee

IT professionals face unbounded demand, constantly shifting technologies, and limited resources. As a result, our approaches to problem-solving require grit and perseverance and can too quickly exhaust us if we lack a framework and shared mindtools to manage our own and our teams’ expectations, not to mention those of our campus stakeholders.  In this session, two CIOs describe their theory and—

This past year I was tasked with redeveloping/designing our campus class schedule. This tricky little application needed to sit inside of our campus CMS and inside department websites; while also being severless. This presentation is on how I architected and built a javascript single page application, with dynamic routing, as an embeddable widget that can be replicated anywhere.

DevOps for accuracy, repeatability, and productivity at UC Davis Schools of Health.   

DevOps means different things to different groups, at UC Davis we have utilized Docker, Jenkins, ELK, and Ansible for automated deploys and will be rolling out continuous integration and continuous deploy (CI/CD).  We have learned so far that the “how” of DevOps is far more important than the “what”. 

UC Davis Schools of Health develops and supports software in-house that results in over 120 different—