Group items tagged

A classroom that has successfully integrated technology into the curriculum would be one where you would not really notice it because it would be so second nature. The teacher would not have to think up ways to use whatever tools were available, but would seamlessly use them to enhance the learning of whatever content was being covered. Technology [would be] used to assist in acquiring content knowledge, and the acquisition of technology skills [would be] secondary. Contrast this depiction with what the International Society for Technology in Education’s (ISTE) National Educational Technology Standards for Students (NETS-S; ISTE, 2002) say about technology integration: Curriculum integration with the use of technology involves the infusion of technology as a tool to enhance the learning in a content area or multidisciplinary setting….Effective integration of technology is achieved when students are able to select technology tools to help them obtain information in a timely manner, analyze and synthesize the information, and present it professionally. The technology should become an integral part of how the classroom functions—as accessible as all other classroom tools.

his urging to shift the focus from the learning tools to what is being learned and how that learning happens still needs to be heeded—almost 20 years later.

Integration is defined not by the amount or type of technology used, but by how and why it is used.

The Shadow Scholar The man who writes your students' papers tells his story Jonathan Barkat for The Chronicle Review Enlarge Image $().ready(function() { $('#enlarge-popup').jqm({onShow:chronShow, onHide:chronHide, trigger:'a.show-enlarge', modal: 'true'}); }); Jonathan Barkat for The Chronicle Review By Ed Dante Editor's note: Ed Dante is a pseudonym for a writer who lives on the East Coast. Through a literary agent, he approached The Chronicle wanting to tell the story of how he makes a living writing papers for a custom-essay company and to describe the extent of student cheating he has observed. In the course of editing his article, The Chronicle reviewed correspondence Dante had with clients and some of the papers he had been paid to write. In the article published here, some details of the assignment he describes have been altered to protect the identity of the student.

What do you think are the most important features a social network should have? How would you prioritize them? Do you plan to Build Less or go big? If building less, what is the minimal set of features you can get away with? We plan to “build less.” These are the features which we aim to complete first: 1. A good secure protocol, encrypted at every leg, including a specification for a lightweight, probably HTTPS, RESTful set of routes. We see all of this communication happening between two Diaspora servers, rather than strictly between peers. We realize there is the problem with polling with this model, but we think there are several tricks worth trying which all have their relative pros and cons: PubSub (fast and easy, requires some level of centralization), querying friends servers from the browser side and posting responses back (requires browser side decryption) to name a couple. Alternatively, we are considering going with XMPP altogether due to the ability to be able to push content between nodes, but we need to research it further to see if it is something we would want to implement. 2. A datastore and corresponding interface that can store all of your stuff in one place. MongoDB is what we are looking at for V1, but the redundancy of TahoeFS is intriguing(as well as serving a slightly different purpose). 3. A clear extension framework. Diaspora will be service-agnostic and we will need to make it easy to import from and export to any format/web service. It is also our goal to make Diaspora as content-agnostic as possible, by providing abstract data types and an easily extended UI so that whatever new content people want to store and share can be integrated without re-rewriting parts of the whole application stack. 4. Be your own OpenID provider. Having a single identity across lots of services is great, but why trust a web service to hold it? Once we are the keepers of our own data, we can also selectively allow services access to it through Oauth.