Kedua, saya mengunjungi website mereka (www.teknologipendidikan.net),
dimana beragam informasi bisa didapat sehubungan dengan teknologi
pendidikan.
Selamat mengamati dan mengambil hikmahnya..
In past blogs, I've recommended that IT pros increase their (positive) web presence by writing technical articles. This can be done in a personal blog or by writing-for-pay for technical publications. In light of a recent event that has been making the blogosphere rounds, I feel the need to make you guys aware of one the caveats of writing for money on the web: People will steal your stuff. Sometimes they'll steal it without really knowing the concept of plagiarism. They'll run your piece and retain your byline but on their site and without asking your permission in advance. Basically they're getting the content someone else paid for, for free. This would be a great business model if it were, oh I don't know, LEGAL. Also, it harms the bottom line of the online business that actually paid for the content, since most of those businesses depend on Google traffic and incoming links. Sometimes they'll take your content without your byline and run it on their site, with the underlying assumption that they wrote it. Also illegal. And weaselly. I have learned that there are an alarming number of people out there who believe that anything on the Internet is public domain. Here's a case in point: One freelance writer found this out the hard way. Basically she had one of her articles reused without permission or compensation by an online magazine called "Cooks Source." (Let me first say that if this mag was going to steal something it should have swiped an apostrophe from somewhere.) Anyway, when the writer wrote to the "editor" to point this out, she got this in return:
Yes Monica, I have been doing this for 3 decades, having been an editor at The Voice, Housitonic Home and Connecticut Woman Magazine. I do know about copyright laws. It was "my bad" indeed, and, as the magazine is put together in long sessions, tired eyes and minds somethings forget to do these things. But honestly Monica, the web is considered "public domain" and you should be happy we just didn't "lift" your whole article and put someone else's name on it!
First of all, you cannot be an "editor" and not know about copyright laws. Just can't happen. Secondly, what's with the attitude? This copying and pasting stuff happens enough that we here at TechRepublic have to get our Legal department to issue cease and desist warnings about once a week. Never underestimate the motives of another party either. One of our editors here told me that she just heard about an instance of someone stealing another person's Twitter feed, including a tweet about a pet dog dying. (I'm still trying to figure out a possible motive on this one. Is creepy a motive?) So there are two lessons here: Don't take content from other sites without the express permission of the editor or writer. Second, if you write something, Google yourself often. And then Google some words from your article to see if it's showing up elsewhere. Our Programming and Development blogger, Justin James, has in fact created an app for finding thieves of content online. Called Rat Catcher, the app is free for a 30-day trial. Another way to protect yourself online!
posted by Toni Bowers
Powered by Telkomsel BlackBerry®
Are you thinking on moving your database from a SQL implementation to a
NoSQL one ?
Sometimes when you decide to move to a different approach lots of doubts
pop out of your mind, there are a couple of actions that can make your
decision more solid and secure. I'll try to provide some tips that would
help you to choose the right NoSQL implementation.
When do you need to think about NoSQL ?
Often web application start by being implemented on top of MySQL, the one
day your application got traction and performance issues start to be a
real pain due to high load of read/write queries on your system.
At this point you have 2 choices:
1. "Shard" your data to partition it across several sites
2. Go for a licensed SQL DBMS or move to a NoSQL DBMS
Basically, you need to scale with less amount of money spent possible.
Michael Stonebraker written a good article on this.
NoSQL use cases
1. Massive data volumes
2. Extreme query load
3. Schema mutation (often called as evolution)
NoSQL most popular pro's
* Scalability and Elasticity (at low cost)
* High Availability
* Flexible schemas (semi-structured data)
* Distributed (easily)
* Low Cost
NOSQL most popular con's
* Weak integrity models
* Consistency (called eventual consistency)
* Transactions (You can do it by code)
* Complex queries
* No standardization
* Messy access control (Some popular implementations already doing this)
Basically, NoSQL runs away from the ACID (atomicity, consistency,
isolation, durability) terminology.
NoSQL most popular implementations
As every topic, there are come popular and trendy implementations of
NoSQL: CouchDb, MongoDB , Cassandra, Memcache.
For a complete list, please refer to wikipedia.
Interesting to read articles/presentations on NoSQL.
1. "NoSQL Databases – Part 1 – Landscape" at VineetGupta.com
2. "Why Digg Digs Cassandra" by Om Malik at Gigaom
3. "NoSQL at Twitter (NoSQL EU 2010)" by Kwvin Weil at Slideshare
4. "NoSQL databases" by Marin Dimitrov at Slideshare
But the sky isn't always blue, you should read the voices that are against
NoSQL also:
1. I Can't Wait for NoSQL to Die by Ted Dziupa
2. NoSQL is Software Darwinism by Jeremy Zawodny
So how do you choose the right NoSQL implementation ?
I must answer with the magic sentence: It depends!
You must choose you database storage system based on the problem you are
trying to solve, but there is one thing that is universal to all of them,
you have to make tests with more than one and only by making results
analysis you will be able to take decisions, unless you are a guesser, i
am not.
My advice is, choose your most common use cases and perform small proof of
concepts, and only after having the numbers you should choose.
1. Policies & Procedure
• Have computer center operating policies and procedures been written?
• Are they sufficiently descriptive in detail to guide the
organization and operation?
• Do data center personnel aware to the policies and procedures?
• Are they kept up-to-date?
2. Personnel
• Are data control center personnel and operators' assignments rotated?
• Is an operating log maintained to record any significant events and
action taken by the operator?
• Is the operator log inspected daily by management?
3. Incident handling
• Do the computer room operators know exactly what to do when the
different types of fire emergencies occur?
• Do the other personnel know exactly what to do when fire emergencies occur?
4. Fire Alarm
• Are the fire alarm pull boxes and emergency power switches clearly
visible and unobstructed?
• Are clear and adequate fire instructions posted in all locations?
• Are there enough fire alarm pull boxes in the computer area?
• Are the operators trained periodically in fire fighting?
• Are the operators assigned individual responsibilities in case of fire?
• How frequently are fire drills held?
5. Fire extinguisher
• Sprinkler
• Halon
• FM200
6. Air Conditioner
• Is the power of Air Conditioner separated from main building power?
• How frequently the Air Conditioner checked
7. Environment Control
• Wiring and cable management
• Combustible goods should be removed
• Water and liquid good should be located outside data center
• How data center protected? Secure ID? Finger print? Lock?
"Establishing a systematic process to capitalize on creativity is an essential capability for enterprises operating in an accelerated business environment"
- Gartner Group, Focusing the Innovation Process
Idea Management has proven to be a powerful source of competitive advantage for companies. The rules for effective Idea Management are very different to the old-fashioned suggestion box, and many of the best practice methods that we have developed may appear counter-intuitive at first sight. However, studies by Imaginatik Research and others have found time and time again that there are several critical elements that make a successful program, and if these elements are not addressed satisfactorily, an Idea Management program is likely to wither on the vine and die.
Imaginatik's extensive experience has helped our clients understand the critical success factors, and ensure that their projects are highly successful in a short period of time.
In this section, we share some of the principles that deliver results. This document contains two sections: Key Principles of Successful Idea Management, and the Overview of an Idea Management Project.
Our experience shows that the following general principles are key to achieving the best results from an Idea Management system.
Focus initiatives on specific business issues: Targeted initiatives are most likely to result in suggestions that get implemented. People with particular expertise in an area are more easily motivated to participate, and the company can assign dedicated resources to drive promising ideas towards implementation.
Launch timely periodic campaigns: Open-ended initiatives with no clear deadlines are likely to fail, as participants' interest fades over time. To obtain high participation rates, Idea Management initiatives require defined deadlines that leverage the promotional effort and create a time pressure to contribute.
Selectively involve wide audiences: Many of the most valuable ideas can be found beyond the business functions that a collective intelligence initiative directly relates to. Extending participation across functions produces highly innovative results. Moreover, it is important to invite large audiences in order to ensure a steady flow of contributions, since only a fraction of all potential contributors will submit ideas.
Stimulate interaction: Ideas can be significantly improved through interaction among different participants. Getting people to share their ideas with others also fosters continuous learning and community building. A successful Idea Management system requires effective collaboration features.
Follow a structured review process: Reviewing ideas effectively and efficiently is as important as collecting them. It is key to follow a structured review process which ensures that good ideas are identified fast and decisions are taken promptly. A structured review process increases the value obtained from ideas and fosters motivation among contributors.
Foster user involvement: Capturing people's attention during the course of the whole initiative is critical to its success. Workflow features that automatically inform participants of relevant matters on an ongoing basis, as well as a user-friendly environment allow people to participate effortlessly. Easy access through the corporate intranet and integration with e-mail are important features of any Idea Management system.
Bridge inhibitions: Experience shows that timidity and political sensitivities are critical inhibitors that will stop many people from contributing. Features like an anonymity option increase trust, and help foster involvement of people that otherwise would not contribute.
Recognize contributions: Whether it is intrinsic or extrinsic, recognition of contributors is essential. Prizes for the best ideas as well as rewards for participation in general should be part of a company's Idea Management program.
Run Idea Management initiatives as projects: Project management principles should be applied to Idea Management. The next section outlines the main issues that need to be considered in an initiative.
There are many aspects to consider when implementing Idea Management in an organization. Poorly thought-through projects are likely to fail, and companies tend to have a long memory of failed projects. Our advice to companies is that they need to set out to be successful from day one, and that means establishing a quality process from the beginning.
Imaginatik has invested a significant amount of time and resources doing research with leading academics and customers to develop the Idea Management Process™, a business manual for implementing Idea Management initiatives. The methodology covers the major steps of planning and managing those projects, and offers recommendations on the best approach for your organization. Imaginatik, together with its partners around the world, provides you with the tools and the services you need to be successful with Idea Management. Below you find some of the issues that you need to consider in the different phases of an initiative.
