Category Archives: Uncategorized

Development or Publication Status of Project

A few weeks ago I was discussing my publishing workflow with Chris Long and explaining that by starting on hcommons.social with a more informal post and then feeding my posts there into this blog I could begin to build a more scaffolded model of the development of publication status of my projects and ideas. After that discussion, I went back to my office and drew up an initial draft of the model as I see it. The image below is a revised version after further discussion with Chris, Kathleen Fitzpatrick, Bonnie Russell, and others.

Image showing scaffolded approach to publishing from mastodon to my blog to semi formal publishing space to formal journal, monograph etc. See text description of graphic on this page.
Development or Publication Status of Project Scaffolded Model

The model starts in the lower left with Mastodon as an initial starting point. Things I write in Mastodon are often short, informal, or in the true ideation stage. Occasionally they are intentional micro-posts intended to communicate an idea, project update, etc.

My Blog is the second stage and contains more long-form pieces, somewhat formal, and often revisions or extensions of thoughts from hcommons.social. Posts to the blog often have some sort of peer feedback involved in the process (e.g. my conversations around this work were not only with Chris, Kathleen, and Bonnie, but also with other colleagues from the MESH and EDLI teams).

Semi-formal publishing spaces comprise a somewhat broad range of places that involve an editorial process of some sort, and typically some sort of more formalized process of peer feedback or review. These spaces can be things like self-published works, works in open-access repositories, or library-based publishing platforms (among others). The editorial process in these is sometimes bordering on the formalized process of the next stage or could be very lightweight. Same with peer review/feedback, perhaps even a structured peer review process that functions similarly to the next step. The end product in this stage is something I consider to be a finished, published piece.

Formal journals and monographs are our more traditional notions of what publishing is. Involved and heavily structured peer review, revision, and editorial processes are common and the publication exists within a more formal end-product and typically with a known publisher.

A note to the process that came up as I worked on this post is that sometimes a piece of work may start in the blog (as it is here) and then become referenced on hcommons.social depending on the content and needs of the artifact. In this case, I wanted to ensure that a text description of the graphic was available when I posted so I opted to post it here on the blog first.

students in the ios lab

iOS Design Lab

The iOS design lab is a project that we started Michigan State University to help our students gain valuable skills that they need to be successful in 21st-century work. The first year is a two-semester program, with an option for a summer internship to continue working on a project.

We start students out doing work in groups and teams that are arranged by connecting their interests and passions. The first several weeks of the semester the individual students look at what they are interested in, areas they want to work in or topics they want to focus on. They form teams and the teams engage in a lot of design thinking, brainstorming, and conversation over the course of the semester to design the idea for an application that they will develop. By the end of the first semester, the teams have thought about their ideas, developed some strategies for dealing with the ethical, moral, safety, cultural, etc. components of their applications and are preparing to think about how they will handle more of the technical components as they move forward.

During the second semester, they focus largely on the technical portions of app development. They develop a familiarity with the Xcode, create small apps that allow a sense of accomplishment and which develop skills with Swift, and software, and developing a level of competency with thinking computationally and learning to use different components of the programming language to accomplish their goals. We work over the semester to get them into some state where they are able to both develop things for the app, think confidently about what they are doing and need to do in the future, and to get themselves ready to move forward with finishing out the app over their summer break.

Across both semesters we work with them to do journaling and documenting their code or other thinking in various ways. We help them collect photos of themselves in practice and we help them to collect artifacts of their brainstorming and other creative activity. The portfolio they produce at the end of the first year of the program shows a holistic process where they’ve engaged in the social, technical, cultural and creative acts of creating an application that is designed to be successful. As we move toward year two we envision the year to be one of putting their learning into practice with a different project and working to develop applications for other people or projects as they continue to develop the portfolio.

Each student is eligible at the end of year one to apply for a World Wide Developer Conference (WWDC) scholarship, to apply for the World Wide Developer Academy in Naples Italy, or to take the exam to gain a credential been certified in Swift. Additionally, each of the students who complete the year will receive a micro credential granted by the University, and a line in My Spartan Story (the University level co-curricular record).