Website Design and Development Cycle

This is website design and development cycle of g2blue for my personal review.

Website Design Preparation

Appointment of a dedicated Account Manager

We at G2Blue always appoint a dedicated Account Manager. You will have a guaranteed point of contact to enable the efficient and smooth running of any website design or development project we carry out for you.

Understanding of the client's business needs and aspirations through research and one to one meetings

Before we even meet with you we will make every effort to gain an understanding of your business as a whole. What you provide, who you provide it for and how you provide it.

When we meet with you we take time to establish where you would like your business to be, when you want it to be there and what you believe is currently stopping you being there.

Analysis of your existing advertising and branding media resources

We need to bring together your business cards, sign writing, letterheads, newspaper advertising, exhibition stands and product packaging. All these things need to be taken into account when considering your website design and development.

Analysis of your immediate competition

With your help we will establish who competes along side you for business and ensure that we know and understand what your competitors are doing with their websites. This information will allow us to make sure that we provide you with a superior product.

Website Design Conception

Scrapbook design through meetings and examples

Website experiences and design examples are used to complete a rough picture of what you want the website design to look like, and what sort of user experience you expect. We will often ask you for examples of other websites you like the look of and enjoy using.

Multiple website design ideas, discussion and design decision

We will then take all the initial ideas together with your current branding and marketing material to formulate a group of ideas that articulate your company's objectives.

Anchor points discussed and created

We at G2Blue make a point of identifying key anchor points within your website. These areas form critical points of reference for the whole design process and are considered the premier traffic pages.

Refining these ideas will identify the strengths and weaknesses of your website and online strategy. Discussions will run parallel to our analysis of your online business policy, realising your target audience and their requirements.

Information architecture methodology

G2Blue applies 'Information Architecture' (IA) methods to your website design. This is the process of organising and presenting information to help the user find and manage information more successfully.

Please see our Information Architecture datasheet for more details.

The understanding of your information sets the foundations for a good user experience. We will use this to ensure that every user to your site can achieve their goals quickly and simply.

Search engine optimisation

We will optimise and build your website right from the conception phase with high search engine rankings in mind. As we are specialists in search engine optimisation, we will build your site so that it has the best possible chance of a strong presence on the major search engines and directories. Effective search engine optimisation strategies adopted at this early stage in website design and development can significantly result in lower search engine optimisation charges later on.

Specification, site maps and project plan

A written specification is drawn up detailing every page within the website. This helps us to determine the way users are guided and navigated throughout the site, and allows you to clearly see how each aspect of the website is connected to another. Once the specification has been agreed upon, sitemaps are drawn up showing paths through the site that the user might take.

These are comprehensive visual representations of the different features of your site. Quite often alterations are made to the specifications once you have a more visual image through viewing the site map.

Once the written specification and sitemaps have been finalised we can accurately judge the production timescales required to make the site.

G2Blue will produce a project plan that details each task and the time required for building & testing.

There will be milestones within the time line identifying important project dates to act as our progress guide throughout the lifecycle of the project.

Actual production time on the site will begin when all three of these documents have been mutually agreed upon and signed off.

Mutual responsibility, timescales and contract agreed

Contracts will be agreed and signed, they will identify each parties responsibilities from conception to the time when the website appears live on the World Wide Web.

Website Creation

Design update meetings and milestone signoff

Throughout the whole project we will hold regular update meetings. These will comprise of frank and honest discussions concerning the progress of your website design. It is our experience that website development time is significantly reduced by holding update meetings and we recommend that you allocate to us a Project Manager within your company who has responsibility over key decisions to avoid project slip.

Progression viewable online

Website Testing

Technology integration testing

Unlike other website development companies, we will make every effort to make sure that the website we create for you works in any Internet browser available.

This may increase the length of design time required but will ensure that the website has completely seamless online presence.

User interface testing

A comprehensive testing period is always allowed within a website project. We test your website page by page and also allow for at least a week for you to test the site independently.

Website Implementation & Launch

Website live

At a mutually convenient time we will upload your website to the agreed location. Please note that our in-house web servers provide a secure and fast hosting solution for your website.

Training

When we develop a website that requires interaction by your staff we will ensure that all employees concerned are trained properly. There needs to be total understanding and a way for all users to feel confident with the new website. In addition, we know from previous experience that a website needs to be continuously promoted by your employees on a regular basis and as such we recommend a quarterly meeting with your employees accordingly.

Website Review & Support

Review meetings

G2Blue believes that what happens after the delivery of a website is equally as important to all that takes place beforehand. We will agree regular meetings with you to ensure complete satisfaction and understanding of ongoing needs.

Direct query logging with guaranteed response

All of our website designs incorporate a query logging facility that can be used by clients to log queries direct to our designers and developers. We will respond, guaranteed.

All of our account managers have direct telephone numbers that are issued to clients as well as the mandatory email address.

Software Development Life Cycle (SDLC)

Summary: As in any other engineering discipline, software engineering also has some structured models for software development. This document will provide you with a generic overview about different software development methodologies adopted by contemporary software firms. Read on to know more about the Software Development Life Cycle (SDLC) in detail.

Curtain Raiser

Like any other set of engineering products, software products are also oriented towards the customer. It is either market driven or it drives the market. Customer Satisfaction was the buzzword of the 80's. Customer Delight is today's buzzword and Customer Ecstasy is the buzzword of the new millennium. Products that are not customer or user friendly have no place in the market although they are engineered using the best technology. The interface of the product is as crucial as the internal technology of the product.

Market Research

A market study is made to identify a potential customer's need. This process is also known as market research. Here, the already existing need and the possible and potential needs that are available in a segment of the society are studied carefully. The market study is done based on a lot of assumptions. Assumptions are the crucial factors in the development or inception of a product's development. Unrealistic assumptions can cause a nosedive in the entire venture. Though assumptions are abstract, there should be a move to develop tangible assumptions to come up with a successful product.

Research and Development

Once the Market Research is carried out, the customer's need is given to the Research & Development division (R&D) to conceptualize a cost-effective system that could potentially solve the customer's needs in a manner that is better than the one adopted by the competitors at present. Once the conceptual system is developed and tested in a hypothetical environment, the development team takes control of it. The development team adopts one of the software development methodologies that is given below, develops the proposed system, and gives it to the customer.

The Sales & Marketing division starts selling the software to the available customers and simultaneously works to develop a niche segment that could potentially buy the software. In addition, the division also passes the feedback from the customers to the developers and the R&D division to make possible value additions to the product.

While developing a software, the company outsources the non-core activities to other companies who specialize in those activities. This accelerates the software development process largely. Some companies work on tie-ups to bring out a highly matured product in a short period.

Popular Software Development Models

The following are some basic popular models that are adopted by many software development firms

A. System Development Life Cycle (SDLC) Model
B. Prototyping Model
C. Rapid Application Development Model
D. Component Assembly Model

A. System Development Life Cycle (SDLC) Model

This is also known as Classic Life Cycle Model (or) Linear Sequential Model (or) Waterfall Method. This model has the following activities.

1. System/Information Engineering and Modeling

As software is always of a large system (or business), work begins by establishing the requirements for all system elements and then allocating some subset of these requirements to software. This system view is essential when the software must interface with other elements such as hardware, people and other resources. System is the basic and very critical requirement for the existence of software in any entity. So if the system is not in place, the system should be engineered and put in place. In some cases, to extract the maximum output, the system should be re-engineered and spruced up. Once the ideal system is engineered or tuned, the development team studies the software requirement for the system.

2. Software Requirement Analysis

This process is also known as feasibility study. In this phase, the development team visits the customer and studies their system. They investigate the need for possible software automation in the given system. By the end of the feasibility study, the team furnishes a document that holds the different specific recommendations for the candidate system. It also includes the personnel assignments, costs, project schedule, target dates etc.... The requirement gathering process is intensified and focussed specially on software. To understand the nature of the program(s) to be built, the system engineer or "Analyst" must understand the information domain for the software, as well as required function, behavior, performance and interfacing. The essential purpose of this phase is to find the need and to define the problem that needs to be solved .

3. System Analysis and Design

In this phase, the software development process, the software's overall structure and its nuances are defined. In terms of the client/server technology, the number of tiers needed for the package architecture, the database design, the data structure design etc... are all defined in this phase. A software development model is thus created. Analysis and Design are very crucial in the whole development cycle. Any glitch in the design phase could be very expensive to solve in the later stage of the software development. Much care is taken during this phase. The logical system of the product is developed in this phase.

4. Code Generation

The design must be translated into a machine-readable form. The code generation step performs this task. If the design is performed in a detailed manner, code generation can be accomplished without much complication. Programming tools like compilers, interpreters, debuggers etc... are used to generate the code. Different high level programming languages like C, C++, Pascal, Java are used for coding. With respect to the type of application, the right programming language is chosen.

5. Testing

Once the code is generated, the software program testing begins. Different testing methodologies are available to unravel the bugs that were committed during the previous phases. Different testing tools and methodologies are already available. Some companies build their own testing tools that are tailor made for their own development operations.

6. Maintenance

The software will definitely undergo change once it is delivered to the customer. There can be many reasons for this change to occur. Change could happen because of some unexpected input values into the system. In addition, the changes in the system could directly affect the software operations. The software should be developed to accommodate changes that could happen during the post implementation period.

B. Prototyping Model

This is a cyclic version of the linear model. In this model, once the requirement analysis is done and the design for a prototype is made, the development process gets started. Once the prototype is created, it is given to the customer for evaluation. The customer tests the package and gives his/her feed back to the developer who refines the product according to the customer's exact expectation. After a finite number of iterations, the final software package is given to the customer. In this methodology, the software is evolved as a result of periodic shuttling of information between the customer and developer. This is the most popular development model in the contemporary IT industry. Most of the successful software products have been developed using this model - as it is very difficult (even for a whiz kid!) to comprehend all the requirements of a customer in one shot. There are many variations of this model skewed with respect to the project management styles of the companies. New versions of a software product evolve as a result of prototyping.

C. Rapid Application Development (RAD) Model

The RAD modelis a linear sequential software development process that emphasizes an extremely short development cycle. The RAD model is a "high speed" adaptation of the linear sequential model in which rapid development is achieved by using a component-based construction approach. Used primarily for information systems applications, the RAD approach encompasses the following phases:

1. Business modeling

The information flow among business functions is modeled in a way that answers the following questions:

What information drives the business process?
What information is generated?
Who generates it?
Where does the information go?
Who processes it?

2. Data modeling

The information flow defined as part of the business modeling phase is refined into a set of data objects that are needed to support the business. The characteristic (called attributes) of each object is identified and the relationships between these objects are defined.

3. Process modeling

The data objects defined in the data-modeling phase are transformed to achieve the information flow necessary to implement a business function. Processing the descriptions are created for adding, modifying, deleting, or retrieving a data object.

4. Application generation

The RAD model assumes the use of the RAD tools like VB, VC++, Delphi etc... rather than creating software using conventional third generation programming languages. The RAD model works to reuse existing program components (when possible) or create reusable components (when necessary). In all cases, automated tools are used to facilitate construction of the software.

5. Testing and turnover

Since the RAD process emphasizes reuse, many of the program components have already been tested. This minimizes the testing and development time.

D. Component Assembly Model

Object technologies provide the technical framework for a component-based process model for software engineering. The object oriented paradigm emphasizes the creation of classes that encapsulate both data and the algorithm that are used to manipulate the data. If properly designed and implemented, object oriented classes are reusable across different applicationsand computer based system architectures. Component Assembly Model leads to software reusability. The integration/assembly of the already existing software components accelerate the development process. Nowadays many component libraries are available on the Internet. If the right components are chosen, the integration aspect is made much simpler.

Conclusion

All these different software development models have their own advantages and disadvantages. Nevertheless, in the contemporary commercial software evelopment world, the fusion of all these methodologies is incorporated. Timing is very crucial in software development. If a delay happens in the development phase, the market could be taken over by the competitor. Also if a 'bug' filled product is launched in a short period of time (quicker than the competitors), it may affect the reputation of the company. So, there should be a tradeoff between the development time and the quality of the product. Customers don't expect a bug free product but they expect a user-friendly product. That results in Customer Ecstasy!

Stylusinc.com

How to convert .bin to iso image, whithout having .cue file.

Sometimes you need to make an iso image out of a .bin file, where you usually use bchunk (binchunker).

To get binchunker, type the following command :

sudo apt-get install bchunk

now to use is it , either:

(1) You have the .cue file ,then you just type the following command :

bchunk filename.bin filename.cue filename

(2)Or, If you don’t have the .cue file, .cue file usually contains the track layout information, and it only contains the following lines :

FILE ”BinFileName.bin” BINARY
TRACK 01 MODE1/2352
INDEX 01 00:00:00

Where MODE1 , is the track mode when it is a computer cd, and MODE2 if it is a PlayStation cd.
you can write a one file of shell script to do all of this foe you , just make a new file :

gedit biniso &

Paste the following lines,(you can always use the ampersand at the end of your command to keep the acess to your command line , you don’t need to open a new shell. It is very useful when you run programs from the terminal like “sudo nautilus”, or “mathematica” ):

echo FILE ”$1.bin” BINARY >> $1.cue
echo TRACK 01 MODE1/2352 >> $1.cue
echo INDEX 01 00:00:00 >> $1.cue
bchunk $1.bin $1.cue $1_
rm $1.cue

Where the first three lines are to write the .cue file, the fourth line is the bchunk conversion command ,and the last line is to remove the .cue file.
Save and close , make it executable:

sudo chmod a+x biniso

Now all what you need to do is to run the following command:
./biniso binfilename

You can also place your biniso file in the /usr/local/bin, in the following way :

sudo mv biniso /usr/local/bin

where if you do so you can access it from any path , but the run command is a little different :

biniso binfilename

By now , most probably you have your iso image, you can either burn it , or mount it.

To mount it, first make a directory for the iso image to be mounted to :

sudo mkdir /media/iso

Then you mount the image :
sudo mount -t iso9660 isofilename /media/iso -o loop

To unmount it :

sudo umount /media/iso

(http://linuxexpert.wordpress.com)


Alkaline Foods to Help Raise your pH Level

Proper pH levels are essential to good health. If our blood is too acidic or too alkaline, it can trigger defense mechanisms that may compensate for the problem at hand, but could potentially cause other problems. We can protect ourselves, and possibly turn these problems around, by eating foods with the proper pH.

Acidosis occurs when our blood pH is too low. It is associated with fatigue, and it is also found in sufferers of many chronic diseases, including cancer. Here are some alkaline foods that can help raise your pH level and restore good health.

Slightly Alkaline Foods

These foods are only slightly alkaline, and can be used when your pH is only slightly low:

* Peas
* Watermelons
* Apples
* Blueberries
* Pears
* Grapes
* Onions
* Bananas
* Raspberries
* Peaches
* Tomatoes
* Oranges
* Lemons
* Apricots
* Grapefruits
* Potatoes (sweet or white)
* Strawberries
* Tangerines

Medium Alkaline Foods

* Cherries
* Limes
* Green Beans
* Dried Dates
* Raisins
* Avocado
* Pineapple
* Cauliflower
* Mushrooms
* Rutabagas
* Radishes
* Cucumbers
* Green Soy Beans
* Brussels Sprouts
* Beets

High Alkaline Foods

These foods have the highest alkalinity you can find in natural food sources. They can be helpful if your pH level is extremely low. If it’s not very low, consider trying some of the lower alkaline foods first.

* Broccoli
* Cabbage
* Rhubarb
* Lima Beans
* Lettuce
* Sauerkraut
* Watercress
* Chard
* Dried Beans
* Carrots
* Dried Figs
* Celery
* Molasses
* Beet Greens
* Raw Spinach

Eating foods that help raise pH levels can be beneficial to those with low energy levels. They can also help patients with a variety of diseases, including cancer, diabetes, gall stones and more. These and most other diseases are dependent on an acidic, low oxygen environment for survival.

If you are suffering from alkalosis, the foods in the above lists are best avoided until your pH is restored to normal levels. There are plenty of other healthy foods you can eat that will help lower your pH.

For initial pH level testing, it’s best to consult your doctor. He (or she) may give you a blood test called an electrolyte panel, which will tell him, among other things, the pH level of your blood. Once he has determined where your pH levels stand, you can use litmus paper to test your pH levels at home. The reason that it’s important to get an official test first is because home pH tests are not as accurate. But if used properly, they can give you a general idea of which direction your levels are moving in.

http://www.fitwatch.com/

20 ways to Secure your Apache Configuration

Some useful tips for securing apache thanks to http://www.petefreitag.com/item/505.cfm

Here are 20 things you can do to make your apache configuration more secure.

Disclaimer: The thing about security is that there are no guarantees or absolutes. These suggestions should make your server a bit tighter, but don't think your server is necessarily secure after following these suggestions.

Additionally some of these suggestions may decrease performance, or cause problems due to your environment. It is up to you to determine if any of the changes I suggest are not compatible with your requirements. In other words proceed at your own risk.

First, make sure you've installed latest security patches

There is no sense in putting locks on the windows, if your door is wide open. As such, if you're not patched up there isn't really much point in continuing any longer on this list. Go ahead and bookmark this page so you can come back later, and patch your server.

Hide the Apache Version number, and other sensitive information.

By default many Apache installations tell the world what version of Apache you're running, what operating system/version you're running, and even what Apache Modules are installed on the server. Attackers can use this information to their advantage when performing an attack. It also sends the message that you have left most defaults alone.

There are two directives that you need to add, or edit in your httpd.conf file:

ServerSignature Off
ServerTokens Prod

The ServerSignature appears on the bottom of pages generated by apache such as 404 pages, directory listings, etc.

The ServerTokens directive is used to determine what Apache will put in the Server HTTP response header. By setting it to Prod it sets the HTTP response header as follows:

Server: Apache

If you're super paranoid you could change this to something other than "Apache" by editing the source code, or by using mod_security (see below).

Make sure apache is running under its own user account and group

Several apache installations have it run as the user nobody. So suppose both Apache, and your mail server were running as nobody an attack through Apache may allow the mail server to also be compromised, and vise versa.

User apache
Group apache

Ensure that files outside the web root are not served

We don't want apache to be able to access any files out side of its web root. So assuming all your web sites are placed under one directory (we will call this /web), you would set it up as follows:

 Order Deny,Allow
 Deny from all
 Options None
 AllowOverride None


 Order Allow,Deny
 Allow from all

Note that because we set Options None and AllowOverride None this will turn off all options and overrides for the server. You now have to add them explicitly for each directory that requires an Option or Override.

Turn off directory browsing

You can do this with an Options directive inside a Directory tag. Set Options to either None or -Indexes

Options -Indexes

Turn off server side includes

This is also done with the Options directive inside a Directory tag. Set Options to either None or -Includes

Options -Includes

Turn off CGI execution

If you're not using CGI turn it off with the Options directive inside a Directory tag. Set Options to either None or -ExecCGI

Options -ExecCGI

Don't allow apache to follow symbolic links

This can again can be done using the Options directive inside a Directory tag. Set Options to either None or -FollowSymLinks

Options -FollowSymLinks

Turning off multiple Options

If you want to turn off all Options simply use:

Options None

If you only want to turn off some separate each option with a space in your Options directive:

Options -ExecCGI -FollowSymLinks -Indexes

Turn off support for .htaccess files

This is done in a Directory tag but with the AllowOverride directive. Set it to None.

AllowOverride None

If you require Overrides ensure that they cannot be downloaded, and/or change the name to something other than .htaccess. For example we could change it to .httpdoverride, and block all files that start with .ht from being downloaded as follows:

AccessFileName .httpdoverride

   Order allow,deny
   Deny from all
   Satisfy All

Run mod_security

mod_security is a super handy Apache module written by Ivan Ristic, the author of Apache Security from O'Reilly press.

You can do the following with mod_security:

• Simple filtering
• Regular Expression based filtering
• URL Encoding Validation
• Unicode Encoding Validation
• Auditing
• Null byte attack prevention
• Upload memory limits
• Server identity masking
• Built in Chroot support
• And more

Disable any unnecessary modules

Apache typically comes with several modules installed. Go through the apache module documentation and learn what each module you have enabled actually does. Many times you will find that you don't need to have the said module enabled.

Look for lines in your httpd.conf that contain LoadModule. To disable the module you can typically just add a # at the beginning of the line. To search for modules run:

grep LoadModule httpd.conf

Here are some modules that are typically enabled but often not needed: mod_imap, mod_include, mod_info, mod_userdir, mod_status, mod_cgi, mod_autoindex.

Make sure only root has read access to apache's config and binaries

This can be done assuming your apache installation is located at /usr/local/apache as follows:

chown -R root:root /usr/local/apache
chmod -R o-rwx /usr/local/apache

Lower the Timeout value

By default the Timeout directive is set to 300 seconds. You can decrease help mitigate the potential effects of a denial of service attack.

Timeout 45

Limiting large requests

Apache has several directives that allow you to limit the size of a request, this can also be useful for mitigating the effects of a denial of service attack.

A good place to start is the LimitRequestBody directive. This directive is set to unlimited by default. If you are allowing file uploads of no larger than 1MB, you could set this setting to something like:

LimitRequestBody 1048576

If you're not allowing file uploads you can set it even smaller.

Some other directives to look at are LimitRequestFields, LimitRequestFieldSize and LimitRequestLine. These directives are set to a reasonable defaults for most servers, but you may want to tweak them to best fit your needs. See the documentation for more info.

Limiting the size of an XML Body

If you're running mod_dav (typically used with subversion) then you may want to limit the max size of an XML request body. The LimitXMLRequestBody directive is only available on Apache 2, and its default value is 1 million bytes (approx 1mb). Many tutorials will have you set this value to 0 which means files of any size may be uploaded, which may be necessary if you're using WebDAV to upload large files, but if you're simply using it for source control, you can probably get away with setting an upper bound, such as 10mb:

LimitXMLRequestBody 10485760

Limiting Concurrency

Apache has several configuration settings that can be used to adjust handling of concurrent requests. The MaxClients is the maximum number of child processes that will be created to serve requests. This may be set too high if your server doesn't have enough memory to handle a large number of concurrent requests.

Other directives such as MaxSpareServers, MaxRequestsPerChild, and on Apache2 ThreadsPerChild, ServerLimit, and MaxSpareThreads are important to adjust to match your operating system, and hardware.

Restricting Access by IP

If you have a resource that should only by accessed by a certain network, or IP address you can enforce this in your apache configuration. For instance if you want to restrict access to your intranet to allow only the 176.16 network:

Order Deny,Allow
Deny from all
Allow from 176.16.0.0/16
 

Or by IP:

Order Deny,Allow
Deny from all
Allow from 127.0.0.1

Adjusting KeepAlive settings

According to the Apache documentation using HTTP Keep Alive's can improve client performance by as much as 50%, so be careful before changing these settings, you will be trading performance for a slight denial of service mitigation.

KeepAlive's are turned on by default and you should leave them on, but you may consider changing the MaxKeepAliveRequests which defaults to 100, and the KeepAliveTimeout which defaults to 15. Analyze your log files to determine the appropriate values.

Run Apache in a Chroot environment

chroot allows you to run a program in its own isolated jail. This prevents a break in on one service from being able to effect anything else on the server.

It can be fairly tricky to set this up using chroot due to library dependencies. I mentioned above that the mod_security module has built in chroot support. It makes the process as simple as adding a mod_security directive to your configuration:

SecChrootDir /chroot/apache

There are however some caveats however, so check out the docs for more info.

Acknowledgments

I have found the book Apache Security to be a highly valuable resource for securing an apache web server. Some of the suggestions listed above were inspired by this book.

Lỗi tiếng Việt windows vista và những suy nghĩ

Trở ngại trong việc gõ tiếng Việt ở Windows Vista một lần nữa cho thấy việc xử lý tiếng Việt trong môi trường Windows và cả trong các hệ điều hành khác (Linux) cần phải được thực hiện một cách sâu rộng hơn.



Sơ đồ bàn phím tiếng Việt trong windows
Còn nhớ mấy năm trước khi lần đầu tiên tôi gõ được tiếng Việt có dấu trên Yahoo Messenger, lúc đó tôi thấy rất vui và chia sẻ thông tin với bạn bè. Sau đó mới biết là ở các hệ điều hành Windows tiếng khác như Nhật, Hàn, Trung, họ đã xử lý vấn đề ngôn ngữ của họ đến tận gốc hệ thống, từ setup trong BIOS đến môi trường Window như chúng ta vẫn dùng bằng tiếng Anh. Tôi thấy chúng ta chậm tiến. Nhưng tôi không phải là "dân Tin" nên chỉ biết bức xúc và trong lòng cũng tự hỏi: "Tại sao Microsoft không quan tâm đến hệ điều hành windows tiếng Việt nhỉ?". Nhưng sau thì thấy câu hỏi đáng hỏi hơn là: "Tại sao không có người Việt Nam làm việc đấy?" .

Trái với người Hàn và người Trung có vẻ "sợ" dùng Windows tiếng Anh thì người Việt lại "giỏi" dùng Windows phiên bản tiếng Anh. Thậm chí, qua kinh nghiệm sử dụng một số phần mềm nước ngoài được nội địa hóa, tôi lại thấy dùng bản tiếng Anh còn dễ hiểu hơn :D. Vấn đề là ở đâu? Chất lượng bản dịch, tiếng Việt không thích hợp để diễn đạt, hay chúng ta chưa có sự quan tâm đầy đủ?

Trên thực tế, chưa thấy nước nội địa hóa các hệ điều hành và các phần mềm tin học yếu như trường hợp Việt nam. Đó là do trình độ và quy mô còn thấp của một nền tin học cả trên phương diện đại chúng lẫn chuyên môn, hay là do chúng ta chưa có nhu cầu?