Deconstructing building a 3D city
Nice analysis of the tricks used in Mirror's Edge to create a great looking city with smooth gameplay
Nice analysis of the tricks used in Mirror's Edge to create a great looking city with smooth gameplay
Second Life introduced a new community platform last month as part of their ongoing restructuring in the face of losing so much of their community to OpenSim and so many opensimmers will end up moving onto Unity projects and then other fully fledged virtual world platforms like VastPark.
One of the best examples of an industry based community of practice
From Wikipedia, the free encyclopediaA community of practice (CoP) is, according to cognitive anthropologists Jean Lave and Etienne Wenger, a group of people who share an interest, a craft, and/or a profession. The group can evolve naturally because of the members' common interest in a particular domain or area, or it can be created specifically with the goal of gaining knowledge related to their field. It is through the process of sharing information and experiences with the group that the members learn from each other, and have an opportunity to develop themselves personally and professionally (Lave & Wenger 1991). CoPs can exist online, such as within discussion boards and newsgroups, or in real life, such as in a lunch room at work, in a field setting, on a factory floor, or elsewhere in the environment.
While Lave and Wenger coined the term in the 1990s, this type of learning practice has existed for as long as people have been learning and sharing their experiences through storytelling.
...
For Etienne Wenger, learning is central to human identity. A primary focus of Wenger’s more recent work is on learning as social participation – the individual as an active participant in the practices of social communities, and in the construction of his/her identity through these communities (Wenger et. al 2004). In this context, a community of practice is a group of individuals participating in communal activity, and experiencing/continuously creating their shared identity through engaging in and contributing to the practices of their communities.
The structural characteristics of a community of practice are again redefined to a domain of knowledge, a notion of community and a practice (Wenger et. al & 2004 pp 27 - 29).
- Domain
A domain of knowledge creates common ground, inspires members to participate, guides their learning and gives meaning to their actions.
- Community
The notion of a community creates the social fabric for that learning. A strong community fosters interactions and encourages a willingness to share ideas.
- Practice
While the domain provides the general area of interest for the community, the practice is the specific focus around which the community develops, shares and maintains its core of knowledge.
In many organizations, communities of practice have become an integral part of the organization structure (McDermott & Archibald 2010). These communities take on knowledge stewarding tasks that were formerly covered by more formal organizational structures. In some organizations there are both formal and informal communities of practice. There is a great deal of interest within organizations to encourage, support, and sponsor communities of practice in order to benefit from shared knowledge that may lead to higher productivity (Wenger 2004). Communities of practice are now viewed by many in the business setting as a means to capturing the tacit knowledge, or the know-how that is not so easily articulated.
An important aspect and function of communities of practice is increasing organization performance. Lesser & Storck (2001, p. 836) identify four areas of organizational performance that can be affected by communities of practice:
- Decreasing the learning curve of new employees
- Responding more rapidly to customer needs and inquiries
- Reducing rework and preventing "reinvention of the wheel"
- Spawning new ideas for products and services
Examples of communities of practice
The communities Lave and Wenger studied were naturally forming as practitioners of craft and skill-based activities met to share experiences and insights (Lave & Wenger 1991).
Lave and Wenger observed situated learning within a community of practice among Yucatán midwives, native tailors, navy quartermasters and meat cutters (Lave & Wenger 1991) as well as insurance claims processors. (Wenger 1998). Other fields have made use of the concept of CoPs. Examples include education (Grossman 2001), sociolinguistics, material anthropology, and second language acquisition (Kimble, Hildreth & Bourdon 2008).
A famous example of a community of practice within an organization is that which developed around the Xerox customer service representatives who repaired the machines in the field (Brown & Duguid 2000). The Xerox reps began exchanging tips and tricks over informal meetings over breakfast or lunch and eventually Xerox saw the value of these interactions and created the Eureka project to allow these interactions to be shared across the global network of representatives. The Eureka database has been estimated to have saved the corporation 100$ million.
Communities of practice compared to functional or project teams
- A project team differs from a community of practice in several significant ways (McDermott, 1999).
- A project team is driven by deliverables with shared goals, milestones and results.
- A project team meets to share and exchange information and experiences just as the community of practice does, but team membership is defined by task.
- A project team typically has designated members who remain consistent in their roles during the project.
- A project team is dissolved once its mission is accomplished.
By contrast,
- A community of practice is often organically created, with as many objectives as members of that community.
- Community membership is defined by the knowledge of the members. CoP membership changes and members may take on new roles within the community as interests and needs arise.
- A community of practice can exist as long as the members believe they have something to contribute to it, or gain from it.
Communities of Practice versus Communities of Interest
In addition to the distinction between CoP and other types of organizational groupings found in the workplace, in some cases it is useful to differentiate CoP from Communities of Interest (CoI).
Community of Interest
- A group of people interested in sharing information and discussing a particular topic that interests them.
- Members are not necessarily experts or practitioners of the topic around which the CoI has formed.
- The purpose of the CoI is to provide a place where people who share a common interest can go and exchange information, ask questions, and express their opinions about the topic.
- Membership in a CoI is not dependent upon expertise - one only needs to be interested in the subject.
Community of Practice
- A CoP, in contrast, is a group of people who are active practitioners.
- CoP participation is not appropriate for non-practitioners.
- The purpose of a CoP, as discussed above, is to provide a way for practitioners to share tips and best practices, ask questions of their colleagues, and provide support for each other.
- Membership is dependent on expertise - one should have at least some recent experience performing in the role or subject area of the CoP.
- Example: Someone who is interested in photography and has some background/training in it finds an online CoP for working photojournalists, who use it to discuss various aspects of their work. Since this community is focused on working photojournalists, it would not be appropriate for an amateur photographer to contribute to the CoP discussions there. Depending on the CoPs structure non-CoP members may have access to reading the discussions and accessing other materials of the community.
Communities of practice and knowledge management
Wasko and Faraj (2000) describe three kinds of knowledge: "knowledge as object", "knowledge embedded within individuals", and "knowledge embedded in a community". Communities of Practice have become associated with finding, sharing, transferring, and archiving knowledge, as well as making explicit "expertise", or tacit knowledge. Tacit knowledge is considered to be those valuable context-based experiences that can not easily be captured, codified and stored (Davenport & Prusak 2000), also (Hildreth & Kimble 2002).
Because knowledge management is seen "primarily as a problem of capturing, organizing, and retrieving information, evoking notions of databases, documents, query languages, and data mining" (Thomas, Kellogg & Erickson 2001), the community of practice, collectively and individually, is considered a rich potential source of helpful information in the form of actual experiences; in other words, best practices.
Thus, for knowledge management, a community of practice is one source of content and context that if codified, documented and archived can be accessed for later use.
Benefit of community of practice
Social capital
Social capital is said to be a multi-dimensional concept, with both public and private facets (Putnam 2001). That is, acquiring social capital gives value to both the individual and the group as a whole, in which the social capital is generated. Through informal connections that participants make in their community of practice, and in the formal process of sharing their expertise, learning from others, and participating in the group, members are said to be acquiring social capital - or a trust that members build between themselves and others that can lead to better communication. Thus, CoPs are considered a way to gain social capital, especially to those members who demonstrate expertise and experience.
Factors of a successful community of practice
Individuals in communities of practice
Members of communities of practice are thought to be more efficient and effective conduits of information and experiences. While organizations tend to provide manuals to meet the training needs of their employees, CoP's help foster the process of storytelling among colleagues which, in turn, helps them strengthen their skills on the job. (Seely Brown & Duguid 1991)
Studies have shown that workers spend a third of their time looking for information and are five times more likely to turn to a co-worker rather than an explicit source of information (book, manual, or database) (Davenport & Prusak 2000). Time is saved by conferring with members of a CoP. Members of the community have tacit knowledge, which can be difficult to store and retrieve outside. For example, one person can share the best way to handle a situation based on his experiences, which may enable the other person to avoid mistakes and shorten the learning curve. In a CoP, members can openly discuss and brainstorm about a project, which can lead to new capabilities. The type of information that is shared and learned in a CoP is boundless (Dalkir 2005). Duguid (2005) clarifies the difference between tacit knowledge, or knowing how, and explicit knowledge, or knowing what. Performing optimally in a job requires being able to convert theory into practice. Communities of practice help the individual bridge the gap between knowing what and knowing how. (Duguid 2005)
As members of communities of practice, individuals report increased communication with people (professionals, interested parties, hobbyists), less dependence on geographic proximity, and the generation of new knowledge. (Ardichvilli, Page & Wentling 2003)
Social presence
Communicating with others in a community of practice involves creating social presence. Tu (2002) defines social presence as "the degree of salience of another person in an interaction and the consequent salience of an interpersonal relationship" (p. 38). It is believed that social presence affects how likely an individual is of participating in a COP (especially in online environments). (Tu 2002) Management of a community of practice often faces many barriers that inhibit individuals from engaging in knowledge exchange. Some of the reasons for these barriers are egos and personal attacks, large overwhelming COP's, and time constraints (Wasko & Faraj 2000)
Motivation
Motivation to share knowledge is critical to success in communities of practice. Studies show that members are motivated to become active participants in a CoP when they view knowledge as meant for the public good, a moral obligation and/or as a community interest (Ardichvilli, Page & Wentling 2003). Members of a community of practice can also be motivated to participate by using methods such as tangible returns (promotion, raises or bonuses), intangible returns (reputation, self-esteem) and community interest (exchange of practice related knowledge, interaction).
Collaboration
Collaboration is essential to ensuring that communities of practice thrive. Research has found that certain factors can indicate a higher level of collaboration in knowledge exchange in a business network (Sveiby & Simon 2002). Sveiby and Simons found that more seasoned colleagues tend to foster a more collaborative culture. Additionally they noted that a higher educational level also predicts a tendency to favor collaboration.
Actions to cultivate a successful community of practice
See also: Online participationWhat makes a community of practice succeed depends on the purpose and objective of the community as well as the interests and resources of the members of that community. Wenger identified seven actions that could be taken in order to cultivate communities of practice:
- Design the community to evolve naturally - Because the nature of a Community of Practice is dynamic, in that the interests, goals, and members are subject to change, CoP forums should be designed to support shifts in focus.
- Create opportunities for open dialog within and with outside perspectives - While the members and their knowledge are the CoP's most valuable resource, it is also beneficial to look outside of the CoP to understand the different possibilities for achieving their learning goals.
- Welcome and allow different levels of participation - Wenger identifies 3 main levels of participation. 1) The core group who participate intensely in the community through discussions and projects. This group typically takes on leadership roles in guiding the group 2) The active group who attend and participate regularly, but not to the level of the leaders. 3) The peripheral group who, while they are passive participants in the community, still learn from their level of involvement. Wenger notes the third group typically represents the majority of the community.
- Develop both public and private community spaces - While CoP's typically operate in public spaces where all members share, discuss and explore ideas, they should also offer private exchanges. Different members of the CoP could coordinate relationships among members and resources in an individualized approach based on specific needs.
- Focus on the value of the community - CoP's should create opportunities for participants to explicitly discuss the value and productivity of their participation in the group.
- Combine familiarity and excitement - CoP's should offer the expected learning opportunities as part of their structure, and opportunities for members to shape their learning experience together by brainstorming and examining the conventional and radical wisdom related to their topic.
- Find and nurture a regular rhythm for the community - CoP's should coordinate a thriving cycle of activities and events that allow for the members to regularly meet, reflect, and evolve. The rhythm, or pace, should maintain an anticipated level of engagement to sustain the vibrancy of the community, yet not be so fast-paced that it becomes unwieldy and overwhelming in its intensity. (Wenger, McDermott & Snyder 2002)
Wikipedia article on communities of practice.
In my opinion, the difference between a Community of Interest and a Community of Practice is more subjective than the article suggests, otherwise it provides a great framework for the subject.
I believe Communities of Practise will come to dominate business thinking as knowledge generation and sharing becomes transparent and regarded as a continuous work in progress across all industries.
A good example of a community of practice in action.
Future of B2C is to develop trust based relationship. Facebook is the weak tie relationship that is suitable for marketing but real relationships will spawn from Facebook "likes" and people will come to the brand website and expect more than what they're getting. They will want an even closer relationship than the get via Facebook. They certainly don't want corporate guff like we all offer today.
Get it at http://tweetcraft.codeplex.com/
From John Sword’s blog.
The following is a hands-on review of my recent experience moving from traditional managed dedicated LAMP hosting to Amazon Web Services (AWS). If you are a weekend warrior Linux admin like me and have been eyeing up AWS for hosting your projects but are still uninitiated, this is written for you. If not, you may want to overt your eyes as its about to get a little nerdy in here.
Introduction
I have been administrating LAMP web servers in some form or another for more than a decade either in support of a business or for personal use. I seem to never have so few projects that shared hosting made sense. So instead, solutions like virtual private servers, managed dedicated hosting and, in some cases, my own rack of equipment have served up my projects over the years.
Most recently I had been using dedicated managed servers on Rackspace and GoDaddy to host a few dozen sites. Because I no longer run my own DNS or mail servers, it made my migration focused on making MySQL and Apache work on AWS. (I no longer host DNS or mail because as I have found services like EveryDNS and Gmail to be far superior.)
Why and What is AWS
There are many advantages to using AWS (or any elastic/cloud computing platform) over a traditional dedicated server solution including cost, speed and flexibility. For example, a basic AWS configuration including metered usage charges will cost most people in a similar situation to mine less than $100 per month. The same solution on a dedicated server would be two to five times the cost, significantly slower in performance, and be at risk of bottlenecking under heavy traffic.
AWS consists of a group of services that represent what is essentially a deconstructed web server. If you are new to virtualization, this is a very different way to think about running a server. (I’m sure you’ll figure out somewhere else to put your Tux sticker now that your server is in the cloud.)
Here is a summary of the core AWS services:
Elastic Compute Cloud (EC2) - EC2 is Amazon’s version of a virtual server but with one major caveat — it has a forgetful hard drive. EC2 instances have ephemeral memory which means that any changes made to its file system are lost on cold restart or because of AWS system failure. If you want permanent storage, you must use EBS or S3 (both defined below) to store files that must change over time.
Simple Storage Service (S3) - S3 is Amazon’s file serving solution which is managed much like an old school FTP server. You setup a bucket, toss files into it and then reference them with a URL. You can also use S3 to store private data such as backups.
CloudFront - (What? No cool alpha-numeric acronym? Come on guys!) When linked to an S3 bucket, CloudFront acts as an affordable and fast content delivery network (CDN). Pricing starts at 17 cents per GB without a contract which is roughly half of what most well established CDNs charge new customers under contract.
Elastic Block Storage (EBS) - Remember how EC2 storage is temporary? EBS is Amazon’s attached storage solution for EC2 instances. You can format an EBS volume with any file system you want and mount it just like a hard drive.
Getting Started
The first step in migrating to AWS is getting a virtual server running and configured. But first, if you have not already, sign up for an AWS account here. Once that is taken care of you will want to head over to the Management Console where you will want to launch an EC2 instance.
Before you can start up an instance, you’ll need to click on the Key Pairs menu option and generate a private key file (.pem extension). Keep this file secure (and chmod 400 its permissions). You will reference this key pair when starting your instance and the private key fie will be needed to log into the instance.
You will need to choose which stock, off-the-shelf Amazon Machine Image (AMI) to use. Once you have done this once and have an image you like, you can bundle and back it up to one of your S3 buckets for future provisioning. For purposes of this review, I’m assuming you chose a base Fedora Linux server on a standard size instance.
Once the instance is online, which can take up to a few minutes, go to the EBS tab of the Management Console and create an volume and attach it to your EC2 instance. I chose 20 GB and chose to reference it as /dev/sdh.
EC2 instances have dynamic IP addresses so you will want to configure an elastic IP address in the Management Console to point to your EC2 instance so your DNS is guaranteed to always resolve.
SSH into the Instance
You will need to download a .pem file which you’ll use to authenticate with SSH into the server.
>ssh -i filename.pem root@address-of-your-server.amazonaws.com
Preparing the EBS Volume
The next step is to prepare the EBS volume so that you have a permanent storage location for MySQL and Apache.
I read quite a few conflicting blog posts about what file system to use on the EBS on a general purpose web server. I found some consensus that XFS is a good choice because it more cleanly handles backup snapshots of the MySQL data, so I went with that.
Fedora does not by default have XFS support, so you’ll need to add it:
>yum install xfsprogs
Now you are ready to format the EBS, create a mount point for it, mount it, and make sure it mounts on restart:
>mkfs.xfs /dev/sdh
>mkdir /mnt/ebs1
>mount -t xfs /dev/sdh /mnt/ebs1
>echo “/dev/sdh /mnt/ebs1 xfs noatime 0 0″ >> /etc/fstab
Install Apache, PHP and MySQL
Let’s start out by grabbing the packages and installing them to their default locations:
>yum -y install httpd php mysql mysql-server php-mysql
Confirm both services will start:
>/etc/init.d/httpd start
>/etc/init.d/mysqld start
Move MySQL to the EBS
Before we move it, let’s do some basic MySQL house cleaning:
>mysqladmin -u root password ‘newpassword’
>mysql -u root -p password
>DELETE FROM mysql.user WHERE user = ‘’;
>FLUSH PRIVILEGES;
>quit
Now let’s stop the service, move the MySQL directory to the EBS volume and setup a symbolic link to the new location:
>/etc/init.d/mysqld stop
>mv /var/lib/mysql /mnt/ebs1/mysql
>ln -s /mnt/ebs1/mysql /var/lib
>/etc/init.d/mysqld start
Move Apache to the EBS
It’s a similar process for Apache. We stop the service, move the configuration and web directories to the EBS, setup symbolic links to the new location and bring the service back up:
>/etc/init.d/httpd stop
>mv /etc/httpd /mnt/ebs1/httpd
>ln -s /mnt/ebs1/httpd /etc/
>mv /var/www /mnt/ebs1/www
>ln -s /mnt/ebs1/www /var/
>/etc/init.d/httpd start
Depending on your configuration, you may need to set these symbolic links:
>ln -s /var/run /mnt/ebs1/httpd
>ln -s /usr/lib/httpd/modules /mnt/ebs1/httpd
Next Steps
You are ready to rock and roll at this point. Before you begin migrating your live projects over to the EC2 instance, I recommend doing the following:
- Obsess over customers
- Invent on behalf of customers
- Think long term (be willing to be misunderstood)
- It's always Day 1 (Repeat the first 3 points)
Oh my god Posterous is preposterously easy to use.
Check out it’s FAQ for more features.
I love what we’re now doing on VastPark with expressive avatars: