Click. Connect. Learn.

All posts in community

National Standards and Local Communities

The goal of state and national standards is laudable: ensure that every kid, anywhere in the States, gets an education of comparable content and quality. However, that idealism and good intent can get lost in a variety of ways; Tom Hoffman breaks down the various shortcomings of Commmon Core pretty effectively.

But, another side effect of national standards like Common Core is that it stimulates a need for curriculum and assessments aligned to these standards. To meet this new requirement at the state level, a service provider would need, in very general terms:

Taj's broken arm
  • a content team available to align content to the new standards;
  • a team to design and write new assessments, or to adapt existing assessments;
  • in-house expertise to align the new/adapted assessments to the standards;
  • marketing copy and sales teams to push these materials to decision makers at both the state and district level.

Obviously, the details required to get this done go beyond this general list. Equally obviously, the organizations best positioned to move into this new space are the ones who have been selling to education prior to the existence of the Common Core standards, and/or organizations who played a role in creating the Common Core standards.

As of March 31, 2010, there were 65 original Endorsing partners; currently (late November, 2011) the list has swelled to 154 partners. It's also interesting to look at the number of organizations that are Common Core Endorsing Partners, and also actively lobby at the national level around Education.

It's not surprising that companies and organizations that were selling to education, and who were active in developing the Common Core standards, would also be active in paying lobbyists to help influence the legislation that would tilt the balance toward the infrastructure they were developing to service the need they were helping to create. It's also perfectly legal, but it points out a consequence of national-level standards that have gained widespread adoption within the states: Now that states have adopted these standards, schools and districts within these states now need to adopt them. In this way, national standards streamline a process where local communities send money outside their local economy by buying products manufactured by national or multinational corporations.

Leaving the influence of lobbying on our educational system aside, I would love to see an educational system where local schools could partner with local independent booksellers to buy texts, and local libraries to assemble reading lists that could be accessed by students. Setting up a system that encouraged and supported schools to work with businesses and institutions within their local communities would actually enrich the communities. When a school district sends money to Pearson, or Scholastic, or McGraw Hill, or any other multinational textbook and assessment company, that money is gone from the community, forever. An equivalent investment in the local economy would both create work and provide a needed boost to local institutions within communities - this would have an immediate benefit to these communities. It's also difficult to argue with tying schools, students, and communities together within a strong public library system.

However, national-level standards require a national-level distribution system, and local booksellers do not have the time of the expertise to align their merchandise with standards. While schools and districts have the expertise to develop assessments that align with standards, most are not funded to do this work at scale at the local level (FWIW, I'm sure that there are some schools that are doing this, and are doing a great job - please let me know about them in the comments). In this way, state and national level standards help ensure that local money leaves communities and flows to multinational corporations. The fact that these same multinational companies get increased access to lawmakers via their lobbying efforts doesn't help.

Image Credit: "Taj's broken arm" taken by Craig Allen, published under an Attribution license.

Unconferences! For All My Friends! Or, Putting the You in Unconference

Unconferences, peer-driven professional development, and teacher-centered professional development are all things I would like to see become more widely adopted. With the process of meeting and having an unconference becoming more familiar, and with EdCamp, a new flavor of unconference gaining visibility in the space, I've been thinking about ways that unconferences could become more prevalent as a recognized, even mainstream, form of professional development.

Grilling

As luck would have it, I tend to think when I cook, and this last weekend was prime grilling weather. So, here are some reasonably well-charred thoughts about how I would love to see K12-focused unconferences grow and develop.

Reach out to union leaders and district officials

EdCamp appears to be more popular among the educators already active on Twitter or other social networks, and they occur largely outside the structure of the organizations in which the participants work. As part of an excellent broader post, Dan Callahan provides a brief explanation of the thought process:

[E]arly on in the planning process, we made some serious decisions in support of our vision of what Edcamp is and should be. Foremost among those was the decision to not pursue PD credits for Edcamp. In these early stages that we’re working in, Edcamp needs the high-energy, hungry for participation crowd. Without those kinds of participants, Edcamp falls flat on its face.

While I understand some of the concerns here, I disagree with the conclusions for an unconference at this stage. To start, the "high energy, hungry for participation crowd" will come regardless, because they want what the camp offers. For the first EdCamp Philadelphia, pursuing PD credits would have been premature, as the nature and value of the event were unproven. However, now that there have been two of these events in Philadelphia, and people can articulate the value of the event, it is time to rethink the value of PD credits.

PD credits would help get more teachers into the mix, and if we have confidence in the model we need to welcome other voices with different viewpoints, and different concerns and needs. If what we want is a face to face meeting of people we know via twitter, then PD credits aren't needed - let's just have a tweetup and call it a day. If, however, we want to move beyond a small portion of professional educators, PD credits would help.

Having PD credits available for unconference-style events creates some additional opportunities that would not exist otherwise. As just one example, if an EdCamp was available to teachers within selected districts on a district-wide teacher professional development workday, teachers could opt to attend the EdCamp as one of several choices.

Also, to be clear: the main reason I am advocating for increased outreach to unions and district administrators is not because their approval or sanction is critical to running a successful K12 centered unconference, or even for current models of K12 unconferences to gain increased popularity. The main reason that union leaders and district admins need to get included into the conversation is to educate them about how unconferences work, and how they are an effective form of professional development. A smart union leader would do well to look at the unconference model, as it provides a clear way for more people to understand the value of an experienced teacher. Veteran teachers have a wealth of experience to share, and the unconference format is an ideal way to do it.

And, if reaching out to district admins and unions can save just one school from the drive-by intellectual mugging of a Willard Daggett, then our work is done.

Encourage more sharing of immediately usable knowledge

Gerald Aungst sums it up nicely:

I seem to be missing the steak, and I’ve been wondering why. It got me thinking about why edcamp still feels powerful and important to me, even though I walk away from many sessions feeling as though nothing of substance actually took place.

Given that unconferences are driven by the needs and desires of the participants, this is an easy one to address: if you want to learn about something, run a session on it. Use the session as an excuse to push your own mastery and exploration of a topic you want to know better. A session designed for teachers to share insights on how they structure their classrooms would be incredibly useful, and it would be made more useful by having students join the conversation.

Another way to help get more immediately useful information would be to give every participant a piece of paper on the way in with the question, "What is the single most useful classroom technique you have ever used?" The sheets could be collected after lunch, and conference organizers could collate and blog the responses. At the risk of stating the obvious, if you want different information, ask a different question.

Or, teachers could just blog about the techniques that they have used in the class, with no EdCamp necessary. If EdCamp attendees interested in gleaning practical tips made a point of asking fellow attendees about ideas and tools that could be implemented immediately - and then blogging these ideas - a body of classroom-tested practices would emerge out of an unconference format.

And, of course, if you are in a session and are at a loss about how to connect the abstract to the practical, ask the room to help you do just that. And then blog about it, so other people can share the knowledge.

Don't drink your own kool aid

People are excited about EdCamp, and that's great, but let's not get carried away.

[T]he edcamp philly crew met at a similar venue, Barcamp Philly. I can not say that I directly learned a single usable thing at that conference but going changed my life. It was meeting Dan, MaryBeth, Kevin, Hadley, Kim, Kristen, Rob and introducing them to my sister Chrissi and Collegaue Nicolae that spawned a international movement in education (emphasis added).

As I said earlier, I'm really glad to see people using the unconference model within education. These concepts have been developed and honed within open source, blogging, design, and software development communities, and they receive continual use within these communities because they work. People within education can learn from this pre-existing practice. The EdCamp organizers reference Barcamp as an inspiration, but current barcamps borrow liberally from practices used in Lightning Talks, Pecha Kucha, Ignite, and Birds of a Feather sessions, to name a few. And this is all good, as we all benefit from using different ways of working and communicating with our peers. But it would be myopic to imagine that unconferences would be as accepted within the education world if these other types of unconferences hadn't been happening in other areas.

It's also worth noting that education-related unconferences are nothing new either. Bloggercon, in 2003, addressed education and included a full unconference day. Since at least 2003, the open source labs and meetups that Paul Nelson, Jeff Elkner, Paul Flint, and (starting in 2006) Steve Hargadon, ran at NECC were unconference-like, with the potential for people to engage in inquiry-driven/peer-driven learning. The EduBloggerCons that Steve Hargadon started running - beginning in Atlanta in 2007, and continuing in different forms to the present day - are education-focused unconferences. It's also worth noting that the National Writing Project has been doing unconference-like professional development since the late 70's. Northern Voice has been running strong since 2005.

In short, there's a lot of prior art here. It's all - including EdCamp - good work. But branding something that is both relatively new on the scene, and relatively similar to past and present endeavors an "international movement" is the type of hyperbolic overreach we can do without. Education doesn't need Don King or Don Trump; we need smart people doing good work. Leave the marketing copy for the people who don't have real skills.

Overblown claims diminish credibility. Let the work speak for itself.

Strive for jargon-free zones

I recognize that this is a tall order, but we need to move away from jargon when we describe what we do. We don't need to talk about how we collaborate within our PLN's; we need to describe how we connect and learn from people in informal settings. Retreating into jargon obscures the work and the process that makes the experience valuable.

Along these same lines, any discussion of tools (I love site X or software Y! It's shiny!) needs to be grounded in specific learning opportunities that wouldn't be possible (or as accessible) otherwise. Chasing the horizon is fun, but the run needs to be worth it.

Eliminating jargon and eliminating an initial focus on the tools acts as a sanity check. This also helps make the ideas we are discussing more accessible to a broader audience.

Conclusions

Unconferences will continue to increase in popularity for two simple reasons: they work, and more people are getting comfortable participating within them. With small, targeted adjustments, the current reach of education-focused unconferences can be extended. But, given that the power of the unconference is within the participants, we all have a role and responsibility here. If there is something you want to see happen, step up.

Code Review: It's A Group Thing

Coming up this Wednesday, May 11th, the Portland Drupal Users Group will be devoting the entire meeting to code reviews of full project applications.

The meetup starts at 6:00 PM, and it will be held at TigerLogic, 1532 SW Morrison St, Portland, on the 2nd floor. I have heard rumors of pizza, and possibly beer. Show up to find out if these rumors are true!

I Hate Wires

During the meeting, there are several things we're looking to accomplish:

  • Make a dent in the full project application queue;
  • Make further inroads into defining a clear, replicable process for code reviews, thereby:
    • Making it easier for new developers to get familiar with Drupal;
    • Making the application review process less painful;
    • Beginning to establish code review sprints as a new community norm, like code sprints and documentation sprints.

If you are an experienced developer in Portland, COME ON DOWN! We need you to help answer higher level questions, and review code!

If you are a developer who wants to get more involved, COME ON DOWN! We need you to ask questions, answer questions, and review some code!

If you are a themer, COME ON DOWN! We need you to help review theme applications!

If you don't write code, and don't theme, COME ON DOWN! We need you to help with documentation, as we will also be working on documentation.

We are also fortunate to have Alan Palazzolo and Chacha Sikes joining us to help run the event.

So, on Wednesday, May 11th, at 6:00 PM come on down, review some code, write some docs, and meet some great folks.

Image Credit: "I Hate Wires" taken by Robert Anthony Provost, published under an Attribution license.

Community Development and Code Reviews

All of what follows in this post is based on two core principles:

  1. Teaching and explaining a topic is the best way to master it; and
  2. The ideals of a community are best handed down from individual to indivdual as they work toward a common goal.

Toward that end, on May 11th, the Portland Drupal Users Group will be using our monthly meeting to run code reviews.

As a side note, while this writeup uses Drupal as an example, the general principles will work across projects, or in training/educational contexts outside software development.

Peer review

Benefits

Code reviews can help grow the existing pool of talented Drupal developers by providing a documented, more structured way for developers new to Drupal to begin learning the Drupal codebase, and learning how to work within the community that maintains with that codebase. Code reviews can also help alleviate one of the more consistent bottlenecks for developers looking to contribute more to Drupal: the project review process.

Code reviews reinforce good habits. The process of reviewing someone else's code forces a few things to happen:

  • The reviewer hones their developer chops by seeing how other people have solved problems;
  • By reviewing code for security issues, developers get more familiar with the best practices for writing secure code, and security issues in exiting code can be addressed;
  • By reviewing code for proper and appropriate use of Drupal's APIs, developers get more familiar with Drupal's APIs, existing modules get more stable and less likely to break on upgrades, and more people become familiar with how core works;
  • By testing and reviewing code via the Coder module, and/or using Devel as needed, easy fixes get implemented more quickly;
  • Opportunities for documentation and better test coverage can be highlighted as part of the review, leading to more automated review and better documentation.

But, most importantly: the process of providing a review of someone else's code creates a dialogue within the community. Code review is contribution and connection, and these are key elements to working successfully in the Drupal community.

Additionally, code reviews provide a clear starting point for people asking how to begin in Drupal. Not many people are going to start reading api.drupal.org without a clear context or reason to do so. Code reviews provide that context, and the process of a code review provides a structure for people coming up to speed on Drupal development. So, when someone says, "I want to get started in Drupal, but I don't know where to be begin," we now have a simple answer:

Check out this page for some background on giving code reviews, and then review some code. The process of reviewing projects will get you up to speed on how to develop in Drupal.

To summarize, code reviews:

  1. Help new developers learn Drupal development best practices;
  2. Help new developers make contributions and connections within the community;
  3. Help reduce the bottleneck of getting new projects approved. And, it's worth noting that increasing the visibility of code reviews as a valued contribution within the community will likely increase the pool of reviewers into the future.

Getting Local

There are a large number of local user groups. While a lot of work can be done virtually, the value of face to face meetups should not be overlooked or underestimated. Local user groups provide an opportunity for more exerienced and less experienced developers to get together and share ideas. If user groups dedicated one to two meetings a year to code reviews - where more experienced and less experienced developers worked together on code reviews - the habit of code reviews could start to become a recognized norm. Once a developer has become proficient in code reviews, the practice of reviewing someone else's code can just as easily be applied to reviewing their own code.

Over time, code reviews should be as familiar and as recognized as Code Sprints and Documentation Sprints. These are held at every DrupalCon, and are regular occurrences at local Drupal Camps. Given the value of code reviews in developing new talent, increasing the consistency and quality of contrib, improving collaboration between developers, and strengthening the contributions of local user groups, code reviews have a role to play in helping the Drupal community continue to grow, evolve, and mature.

Getting Started

Fortunately, getting started is the easy part. The queue for project applications is open, and you can sort by date to see the oldest projects first.

The Code Review Group is getting up to speed, and you can indicate on your profile that you are actively reviewing code. This wiki page and this handbook page both provide instructions for diving in to a code review.

And, if you are in Portland this May 11, come to the Users Group meeting and get running with some reviews.

Image Credit: "Crystal peer-reviewing Mike's code" taken by Jason Crane, published under an Attribution Non-Commercial Share Alike license.

Syndicate content