For a while I’ve been thinking about how adopt a different approach to tooling in our team, beyond nameless and obtuse groups of tools built on google sheets that record and reveal information about our projects. I think there’s value in considering these tools more like colleagues and team members with position descriptions and real roles to perform. I also think there’s value in extending the metaphor to the point of giving these team members names, for fun and function. Meet the team Introducing Wanda, Dennis, Terry, Justin, Gordon, Velma,…
Today I spoke to the team about how we might explore the use of a tool/service that allows us to easily store, manage and share regularly used content and/or code snippets. I was really interested in hearing from them if exploring the use of tools/service is something worth doing? Remembering this is not so much about creating cookie-cutter courses (because they’re all individual and unique), but more about creating readily reusable code that forms the foundation. An example – while the set of Arts translation and interpreting courses are based…
