Webpage design Tutorial

Huong dan thiet ke web Webpage design tutorial

Kha nang sieu pham

http://www.youtube.com/watch?v=0Nd_FnPGUVg&feature=player_embedded

We're entering the decade of the developer

Takeaway: IT professionals were the heroes of recent decades when they helped enable big productivity gains. The next decade will have a new set of heroes: Developers. Learn why.

The major productivity gains of late 1990s and early 2000s were powered by the spread of information technology throughout organizations of all sizes. And it made IT professionals invaluable. However, the technology world remains in the midst of a relentless transformation and the changes sweeping the industry over the next decade will make developers, not IT pros, the new superstars.

We shouldn’t forget that the innovations we now take for granted have streamlined business communications and commerce in big way. I’m talking about PCs on every desk, computer networks for file and printer sharing, email, shared calendars, and ultimately the Web . These innovations gave a turbo boost to existing companies and spawned the rise of nimble new companies that were able to run circles around the incumbents in many industries.

These 1990s innovations made nearly all organizations deeply dependent on new technologies and they hired IT professionals in droves in order to troubleshoot problems, train employees how to use the new digital tools, and to “keep the world running,” as it were.

But that revolution is over. The technologies are deployed. The users are trained. The data centers are built. In recent years, no new IT innovations have arisen that can transform businesses the way corporate networks or email groupware or the Web did a decade ago. Nearly everything IT is doing now is tweaking and incremental upgrades to existing technologies.

Worse, the new tech trends that are arising often adapt and iterate faster than traditional IT departments can handle. Take Web applications and smartphones for example. The product and upgrade life cycles are so short that IT’s time-tested procedures (test, harden, and deploy) leave IT in a position of rolling out stuff that is already outdated by the time they rubber-stamp it for employee use.

That’s why many employees have started using their own laptops, smartphones, and Web apps to get work done — sometimes clandestinely — and it’s why many companies have reduced the size of their IT departments. Some, such as author Nicholas Carr, have even predicted the demise of IT altogether.

TechRepublic recently asked its CIO Jury to weigh in on the future of the IT department and the verdict was mixed, with half thinking IT will continue to shrink and the other half thinking all boats will rise as technology becomes even more embedded in modern organizations.

I tend to side with the shrinkers, with the exception of a few industries such as health care that have traditionally lagged in IT innovation and are now quickly catching up (a phenomenon borne out in the comments from the CIO Jury poll). But, that won’t last forever.

Why? Many computer products have become so cheap that it’s often easier to replace than to repair. Plus, IT services have become highly commoditized. There are plenty of technicians and administrators to fill up the labor pool (unlike the IT labor shortage a decade ago), and there are plenty of consultants who can fill in the gaps when needed. The really good IT professionals will still cost you a pretty penny, but they’re worth it because they can make your organization more efficient or innovative, or both.

The other factor is expectations. Now that workers have been using this stuff for over a decade, they just expect it to work. There’s less tolerance than ever for downtime or buggy systems, especially when companies have outsourced it to service providers who promise best-of-breed experts on the clock 24/7/365. But, even when companies have an expensive in-house IT department that has been hired to make everything run like clockwork, they don’t tolerate interruptions.

IT is now a utility. And increasingly, it’s just a utility that gets you to your apps

Applications have always been king — to an extent. It was apps that decided the winner of the PC wars of the 1980s, empowering IBM and then Microsoft to victories over Apple.

But today’s app environment is different. It’s faster. It’s more incremental. It’s multi-platform. It’s more device-agnostic.  And it’s shifting more of the power in the tech industry away from those who deploy and support apps to those who build them. Oh, and did I mention that it’s easier to get started, so there’s also a lot more competition?

This new app model began in smartphones, with the App Store for Apple’s mobile OS, but it has spread to other mobile platforms such as Android and more recently to netbooks and tablets as well. And it’s only a matter of time before it spreads to desktop, Web, and enterprise apps, which will each get their own nuanced versions of app stores.

It will be especially interesting to see how well really big software packages can adapt and get more modular, and possibly embrace open standards so that data can flow more easily between best-of-breed apps and modules. But, however it plays out, the momentum behind this app model is too great for it not to affect traditional software packages and software implementation methods.

It’s a simple equation. When there’s less tech support, there’s a lot more emphasis on apps that just work. And the new app model forces developers to make apps that can deliver immediate value to users, otherwise they’ll get passed over for the next app.

This breeds a survival-of-the-fittest environment for developers, but make no mistake, there’s never been a better time to be a developer.

In this environment, developers have tremendous opportunities for independence and creativity. Individual developers and small teams of developers (sometimes in concert with designers and project managers) can now build mini empires for themselves, thanks to the micropayment systems that allow one developer with a PayPal account to have virtually all of the infrastructure needed to start a consulting business.

Industrious developers can even work for a big company or an app development team as a day job and then moonlight as an independent developer with a few of his or her own apps that can potentially generate residual income. Meanwhile, experienced app developers can freelance for multiple clients and build a small consultancy by helping businesses of all sizes get into the app game.

For these developers, location matters less than ever, too. A developer with email, a Skype account, and a half-decent Web portfolio can typically find pretty good work, even from clients in remote locations. Plus, the tools for team collaboration over the Web are getting better all the time and will continue to break down geographic barriers.

The demand for developers is increasing because everyone wants an app now — from Target to Allstate to Joe’s Garage down the street. They started with mobile but we should expect this to spread to tablets, desktop widgets, and eventually TVs (once platforms like Android and iOS get embedded in the living room experience). Having a multi-platform app strategy will become standard procedure for new companies the way having a website is today.

The sweeping changes in the tech industry will continue to have unpredictable consequences and will produce new sets of winners and losers. Traditional IT roles are not going to go away, but they will be under increased pressure and are likely to become more concentrated in service providers. At the same time, developers are about to step into the spotlight. This is going to be their decade.

The future of IT will be reduced to three kinds of jobs

There’s a general anxiety that has settled over much of the IT profession in recent years. It’s a stark contrast to the situation just over a decade ago. At the end of the 1990s, IT pros were the belles of the ball. The IT labor shortage regularly made headlines and IT pros were able to command excellent salaries by getting training and certification, job hopping, and, in many cases, being the only qualified candidate for a key position in a thinly-stretched job market. At the time, IT was held up as one of the professions of the future, where more and more of the best jobs would be migrating as computer-automated processes replaced manual ones.

Unfortunately, that idea of the future has disappeared, or at least morphed into something much different.

The glory days when IT pros could name their ticket evaporated when the Y2K crisis passed and then the dot com implosion happened. Suddenly, companies didn’t need as many coders on staff. Suddenly, there were a lot fewer startups buying servers and hiring sysadmins to run them.

Around the same time, there was also a general backlash against IT in corporate America. Many companies had been throwing nearly-endless amounts of money at IT projects in the belief that tech was the answer to all problems. Because IT had driven major productivity improvements during the 1990s, a lot of companies over-invested in IT and tried to take it too far too fast. As a result, there were a lot of very large, very expensive IT projects that crashed and burned.

When the recession of 2001 hit, these massively overbuilt IT departments were huge targets for budget cuts and many of them got hit hard. As the recession dragged out in 2002 and 2003, IT pros mostly told each other that they needed to ride out the storm and that things would bounce back. But, a strange thing happened. IT budgets remained flat year after year. The rebound never happened.

Fast forward to 2011. Most IT departments are a shadow of their former selves. They’ve drastically reduced the number of tech support professionals, or outsourced the help desk entirely. They have a lot fewer administrators running around to manage the network and the servers, or they’ve outsourced much of the data center altogether. These were the jobs that were at the center of the IT pro boom in 1999. Today, they haven’t totally disappeared, but there certainly isn’t a shortage of available workers or a high demand for those skill sets.

That’s because the IT environment has changed dramatically. More and more of traditional software has moved to the web, or at least to internal servers and served through a web browser. Many technophobic Baby Boomers have left the workforce and been replaced by Millennials who not only don’t need as much tech support, but often want to choose their own equipment and view the IT department as an obstacle to productivity. In other words, today’s users don’t need as much help as they used to. Cynical IT pros will argue this until they are blue in the face, but it’s true. Most workers have now been using technology for a decade or more and have become more proficient than they were a decade ago. Plus, the software itself has gotten better. It’s still horribly imperfect, but it’s better.

So where does that leave today’s IT professionals? Where will the IT jobs of the future be?

1. Consultants

Let’s face it, all but the largest enterprises would prefer to not to have any IT professionals on staff, or at least as few as possible. It’s nothing personal against geeks, it’s just that IT pros are expensive and when IT departments get too big and centralized they tend to become experts at saying, “No.” They block more progress than they enable. As a result, we’re going to see most of traditional IT administration and support functions outsourced to third-party consultants. This includes a wide range from huge multi-national consultancies to the one person consultancy who serves as the rented IT department for local SMBs. I’m also lumping in companies like IBM, HP, Amazon AWS, and Rackspace, who will rent out both data center capacity and IT professionals to help deploy, manage, and troubleshoot solutions. Many of the IT administrators and support professionals who currently work directly for corporations will transition to working for big vendors or consultancies in the future as companies switch to purchasing IT services on an as-needed basis in order to lower costs, get a higher level of expertise, and get 24/7/365 coverage.

2. Project managers

Most of the IT workers that survive and remain as employees in traditional companies will be project managers. They will not be part of a centralized IT department, but will be spread out in the various business units and departments. They will be business analysts who will help the company leaders and managers make good technology decisions. They will gather business requirements and communicate with stakeholders about the technology solutions they need, and will also be proactive in looking for new technologies that can transform the business. These project managers will also serve as the company’s point of contact with technology vendors and consultants. If you look closely, you can already see a lot of current IT managers morphing in this direction.

3. Developers

By far, the area where the largest number of IT jobs is going to move is into developer, programmer, and coder jobs. While IT used to be about managing and deploying hardware and software, it’s going to increasingly be about web-based applications that will be expected to work smoothly, be self-evident, and require very little training or intervention from tech support. The other piece of the pie will be mobile applications — both native apps and mobile web apps. As I wrote in my article, We’re entering the decade of the developer, the current changes in IT are “shifting more of the power in the tech industry away from those who deploy and support apps to those who build them.” This trend is already underway and it’s only going to accelerate over the next decade.

LAMP

Want to get a LAMP development environment fired up without the hassles of configuring everything from scratch? XAMPP makes it a breeze.

If you have ever had to set up a Linux, Apache, MySQL and PHP or Perl installed and running at the same time you know what hassle it can be. If you are new Linux it can be a rather daunting experience just trying to set everything up, nevermind learning scripting languages like PHP, Perl and a database like MySQL or SQL Lite.

XAMPP is a single packaged download from Apache Friends which provides all of the pieces of software needed, plus more you probably don't need, to make Apache installations with server-side scripting and a few database options ready to go in a testing or development environment.

In this article we will focus on getting XAMPP running on Linux, it will also work on Windows and a version for Sun's Solaris is also available. For our example we will use a Debian-based Linux distribution, but just about any flavour of Linux will work. To start, you will need to download the XAMPP package for Linux from the SourceForge Web site. The current version we downloaded was 1.4.9a.

The file is 34MB and according to the Apache Friends Web site includes the following software:

Apache 2 MySQL 4 PHP 5, 4 & PEAR SQLite 2.8.9 + multibyte (mbstring) support Perl 5 ProFTPD phpMyAdmin OpenSSL Freetype libjpeg, libpng gdbm zlib expat Sablotron libxml Ming

Webalizer pdf class ncurses mod_perl FreeTDS gettext IMAP C-Client 2002b OpenLDAP (client) mcrypt mhash Turck MMCache cURL libxslt phpSQLiteAdmin MD5 checsum: 4e853c535ced4e707cbfa6e59c0fc4e2

---

Security note
XAMPP is recommended to be only used in a development environment and not in production as the system has very loose security settings. The system can be tweaked to be more secure and we recommend following the steps here.

---

Once the package is downloaded you will need to extract it to a file. You can do this in two ways depending on which version of Linux you are using. You can use a file manager and extract the package into the /opt file.

To extract the files manually you can a console and type in the following:

tar xvfz xampp-linux-1.4.9a.tar.gz -C /opt

Make sure you are logged in as the system administrator. To do this manually type in su. It will then ask for your administration password. Type in the system's administration password.

Once this file has been extacted you will need open the file "lampp" in the /opt/lammp directory. If you open this using the file manager it will prompt a command shell with all the user options as shown in figure 1 below.

Firgure 1: The commands for XAMMP

If you need to do this manually, open a console and type the following command:

/opt/lampp/lampp start

The screen should show the same shell as shown in figure 1.After everything has started the next step is to test the Apache Server is running. The easiest way to do this is to open up a browser of your choice and type in the following:

http://localhost

XAMPP has a splash screen that will look something like in figure 2 with sample scripts ready for testing and use. Your LAMP environment is now ready to test your own Web applications.

10 programming habits that should be more common

You learn lots of things when you go to college and get a computer science degree or read a how-to-program book. Unfortunately, a number of good programming habits are either untaught or take a good amount of practice to turn into a way of life. Here are 10 such habits you should cultivate to become a better programmer.

1: Learn your source control process

You know that thing users like to do, where they pick up your application for the first time and get angry because it doesn’t do things exactly the way they want — and then they refuse to learn how the program works? You’re left scratching your head wondering why they didn’t bother to learn the application, which would have saved them all sorts of problems.

Well, a lot of developers do that too, when it comes to working with source control. Every source control system is a bit different and has a workflow that maximizes the value you get from it. Learn that workflow! It may take some time, research, and practice, but trying to fight it by making your source control repository look like the ugly mess you are used to creating on your local hard drive defeats the purpose. You might as well just have good backups for your local system and call it a day.

2: Go with obvious variable naming

This one comes up all the time: developers just give variables uninformative names and think it doesn’t matter. Well, it does matter any time someone else comes in to look at the code. I can’t speak for all developers, but I have yet to meet one who is typing for eight hours a day straight. Adding a few keystrokes for better variable names (especially when modern IDEs will autofill it for you) will make a measurable different in productivity. Stop making excuses and use better variable names.

3: Use interfaces, not classes when possible

I violate this one all the time, and I know it. Whenever possible, code to an interface instead of a class. For example, if your class needs to return an enumeration of Integers, there’s no need to return a List; return an IEnumerable. This allows recipients to do what they want without needing to recast or transform the results into a class that meets their needs.

4: Assume the worst from your peers

I’d love to think that everyone I worked with was as good, if not better than me at writing software. In some jobs, it was usually true; but in others, it wasn’t. I did learn, though, that you have to write your code as if someone with six months of experience (or someone with lots of experience who just is not very good) is going to be working on it next, because it may very well be true. What that means is that you can’t afford to write “fancy” or excessively “elegant” code. The next person to look at it could end up making a mess because he or she doesn’t understand it. I’ve discovered that writing code is like cooking: To please everyone, you can’t go for the escargot or liver pate; you need to be serving steak and potatoes. Keep your code basic and straightforward, and those coming behind you to maintain it will be able to do their job.

5: Assume the worst from your users

There is a bell curve of tech savvy with our users. We tend to miss the mark on usability and hit the lower end of the bell, but that still leaves about 10% - 20% of users in the dark. Aiming for the lowest common denominator means just that. With a few exceptions, you have to assume that the person using your application will never look at documentation, attend training, or otherwise seek out how to use your application.

6: Document the reason for a change

All too often, there will be a change in an application but no documentation of why the change was made. A few months later, someone will notice that the change conflicts with another requirement and demand to know why it was made, and no one will actually know. The next thing you know, everyone will be losing a lot of time trying to figure out where the change came from and why. By documenting the purpose of the change (and who the requester is), you’ll be saving everyone a big headache down the road.

7: Explain the purpose of algorithms

In the same vein, any algorithm should have a clear explanation of why it was chosen. For example, I support a CRM system that has a nonintuitive formula for applying discounts to purchases. No one can quite explain why this specific formula is in place, but it is not working in some scenarios. We are not quite sure how to change it, because the reason for its current form is unknown. All it would have taken was a simple comment that said, “We do it like this because of consideration CYZ,” and everything would be fine.

8: Provide contextual help

We all know that users tend to gloss over training materials. At the same time, it’s important to provide a variety of contextually available help in your application. While users won’t read the manual, they are likely to click the giant question mark next to the input control they don’t understand. Put your help access as close to the UI controls as possible with targeted text to make it easy for users to get the help they need. Also, remember to use terms and phrases your users will understand, not internal jargon.

9: Perform cross-platform testing

If you are writing Web applications, it is important to test them on a variety of platforms. You will want to check different browsers on different platforms. Sounds like a hassle, right? It is. Luckily, there are some tools to help with that. Check out the offerings from Sauce Labs to make it a bit easier to cross-platform test your Web applications.

10: Keep the users in mind

A lot of business requirements don’t help the users at all, and some may even annoy them. These requirements may be non-functional but are designed to satisfy someone in the marketing or sales departments. A great example is a registration page that asks for a lot more information (and makes it mandatory) than most users feel comfortable giving. While I understand the motivation (making their jobs easier), developers often underestimate how much users dislike it –while overestimating users’ desire to get the benefits of registration. Remember that there are few unique propositions in this industry, and you do not have the luxury of turning users away. Fight on behalf of your users to make the best application possible.

What would you add?

What other good practices do you think are underused? Do you have any pet peeves you’d add to this list?

Source: http://www.techrepublic.com

Tạo trường tự động tăng trong SQL Server 2000

Gia su co bang
Emp(emp_code,
emp_name,
emp_address)
create proc SerialNumber
as
create table #tem(
col0 int,
col1 varchar(50),
col2 varchar(50),
col3 varchar(50)
)

declare @var1 varchar(50)
declare @var2 varchar(50)
declare @var3 varchar(50)
declare @s int
set @s = 0

declare empcur cursor scroll
for select * from emp

open empcur
fetch next from empcur into @var1, @var2,@var3
while @@FETCH_STATUS = 0
begin
select @s = @s + 1
insert into #tem values(@s,@var1,@var2,@var3)
fetch next from empcur into @var1,@var2,@var3
end

close empcur
deallocate empcur

select * from #tem

exec SerialNumber

Lấy một số bản ghi ngẫu nhiên

Ví dụ này lấy ra một số bản ghi từ cơ sở dữ liệu theo một cách ngẫu nhiên.

Select top 10 percent * from Customers
ORDER BY NEWID()

Nếu lấy cố định số bản ghi thì bỏ mệnh đề PERCENT.

Các lỗi lớn nhất trong thiết kế web

1. Lạm dụng các trang Flash
Đôi khi đấy là những trang đầu tiên bạn nhìn thấy khi ghé thăm một website. Thông thường chúng có một hình ảnh sống động rực rỡ với những từ ngữ đón mời như “Chào bạn” hoặc “Nhấp chuột vào đây để đăng nhập”.

Dĩ nhiên bạn không muốn những người khách truy cập vào website của mình có một lý do nhấp chuột vào nút “quay lại”! Vì thế, bạn hãy cho họ thấy trước giá trị của website mà không cần dùng tới các kỹ xảo kiểu Flash.

2. Quá nhiều banner quảng cáo
Nói chung các banner quảng cáo thường giống nhau trên nhiều website, vì thế sẽ khiến những người truy cập không còn mấy hứng thú để tâm tới chúng nữa. Mặt khác chúng chiếm mất những diện tích lẽ ra có thể dành thêm cho các bài viết hoặc tin tức, thông báo cần đăng trên website.

Vậy thay vì quảng cáo, bạn hãy cung cấp những thông tin hoặc hình ảnh có giá trị hơn và các liên kết có liên quan với nội dung cũng như hãy để cho những người truy cập của bạn thấy rằng họ muốn đọc hơn là “bị đọc”.

3. Thiếu menu truy cập tự nhiên và dễ hiểu
Bạn phải cung cấp một thực đơn hay menu danh mục rất cụ thể và đơn giản đến mức một đứa trẻ cũng sẽ biết sử dụng nó ngay. Tránh dùng các kỹ xảo flash phức tạp dựa trên các thực đơn hoặc những thực đơn cuộn-thả nhiều lớp (multi-tiered dropdown), bởi vì những người truy cập sẽ rời bỏ trang web của bạn nếu họ không biết chọn hướng như thế nào và không được dẫn dắt nhanh chóng.

4. Không có một site map rõ ràng
Một sơ đồ hay mục lục của website bằng từ ngữ rõ ràng với khả năng hiển thị đường dẫn ngược về trang gốc sẽ giúp cho người sử dụng xác định được vị trí của họ trên trang website của bạn khi họ truy cập. Và bằng cách đó thì họ sẽ có khả năng duyệt được những thông tin liên quan hoặc chuyển hướng tới bất kỳ phần nào trên website của bạn một cách dễ dàng. Đừng làm cho những người truy cập bị rối mắt bởi điều đó có nghĩa là “chối bỏ cơ hội thu hút khách”.

5. Sử dụng audio, video bừa bãi
Nếu muốn người truy cập dừng lại trên website của bạn lâu hơn để đọc nội dung thì bạn luôn phải đảm bảo rằng họ không bị quấy rầy bởi một vài âm thanh hoặc phim ảnh lặp đi lặp lại trên website. Nếu bạn vẫn muốn kèm theo âm thanh hoặc phim ảnh cho website đó thì phải cung cấp cho người truy cập có quyền kiểm soát được chức năng audio, video bằng cách điều chỉnh âm lượng hoặc chặn tiếng, hình để họ có thể tập trung hơn vào trang web.

Source: web.dongtak.net

Ứng dụng CNTT trong giáo dục

Ứng dụng CNTT trong giáo dục cần quyết liệt hơn
Tất cả các trường học điều có Internet nhưng để tận dụng triệt để lợi thế này vẫn còn là vấn đề. Giáo dục mầm non hằng năm đều có những bài viết “ phụ huynh thức trắng đêm để đăng kí học cho con; nhiều trường tiểu học, trung học, phổ thông cũng đang hình thành những website “tự phát”.
Kính chào bạn đọc,

Năm học 2011 -2012 sắp được khai giảng, những chỉ thị ứng dụng CNTT vào giáo dục vẫn còn đó… Thế nhưng bản thân Tôi là người làm trong ngành giáo dục vẫn chưa thấy những chuyển biến rõ rệt nào, đặc biệt trong giáo dục mầm non và giáo dục phổ thông.

Tất cả các trường học điều có Internet nhưng để tận dụng triệt để lợi thế này vẫn còn là vấn đề. Xót xa cho giáo dục mầm non khi hằng năm (2010 và 2011) đều có những bài viết “ phụ huynh thức trắng đêm để đăng kí học cho con”. Nhiều đọc giả cũng đã gợi ý thành lập website để download hồ sơ, đăng kí học qua mạng…Rõ ràng chúng ta vẫn thấy thiếu một chút “quyết liệt” từ các nhà quản lý và các cấp lãnh đạo giáo dục. Không chỉ xây dựng website cho mầm non là cần thiết, bên cạnh đó trường tiểu học, trung học, phổ thông cũng đang hình thành những website “tự phát”:

Lợi ích xây dựng website mầm non, tiểu học :

• Phụ huynh muốn tìm hiểu chương trình dạy học, cơ sở vật chất trường ra sao, thực đơn cho bé, các thông báo của giáo viên, ban giám hiệu.

• Các ý kiến đánh giá của phụ huynh về trường, chi phí hàng tháng, các mẫu đơn đăng kí nhập học.

• Người chưa phải là phụ huynh thì muốn tham khảo về trường để cho con em mình theo học.

• Nhà trường thì đưa lên web những chứng chỉ (trường điểm, trường quốc gia) để phụ huynh dễ lựa chọn.

Lợi ích xây dựng website trung học :

• Là nơi cung cấp những thông tin lịch sử về trường, thành tựu dạy và học, cơ sở vật chất.

• Các sự kiện của trường, hoạt động đoàn đội.

• Là kênh trao đổi giữa nhà trường và phụ huynh, giáo viên và học sinh.

• Góp phần cạnh tranh với các trường khác nhằm mục đích không ngừng nâng cao chất lượng giáo dục.

Lợi ích xây dựng website phổ thông :

• Là kênh thông báo chính thức cho học sinh về lịch thi cử, môn thi từng học kì, công bố điểm thi.

• Tích hợp hệ thống tra cứu điểm và quản lí hồ sơ học sinh các cấp.

• Người muốn tiếp xúc với trường thì tìm số điện thoại để liên lạc với các phòng ban hoặc giáo viên nào đó.

• Ở bậc phổ thông nhiều trường đã ý thức được việc thành lập website nhưng đa phần mang tính tự phát. Nhiều trường học đã ý thức xây dựng hoàn chỉnh website của trường mình, tuy nhiên còn nhiều lãnh đạo vẫn chưa có nhận thức về xây dựng “bộ mặt nhà trường” trên không gian số.

Nhưng đó chỉ là nhận thức của người quản lí, còn nhận thức của một số giáo viên học sinh thì ngược lại. Do điều kiện tiếp xúc với Internet, diễn đàn… nhiều cá nhân đã háo hức xây dựng website cho trường mình. Nhưng mỗi người mỗi kiểu các nhóm học sinh khác nhau đã lập ra website, forum khác nhau với cùng một tên trường (với những tên miền khác nhau .com, .info, . com.vn, .edu.vn..). Vấn đề là Hiệu trưởng thì không biết rằng trường mình lại có nhiều website đến vậy. Những website này nghiêng nặng về giải trí, chat, âm nhạc.

Nếu website hoạt động tốt thì không sao, nếu website bị tấn công để đăng lên những thông tin xấu, hoặc có người cố tình thay đổi thông tin nhà trường, hình ảnh, video phản cảm thì cần phải xử lí ra sao? Nhà trường phải đi giãi bày với ai?

Với lợi thế Internet, tôi nghĩ sẽ rất dễ dàng xây dựng các hệ thống quản lí giáo dục trên web. Giáo viên/ giảng viên có thể giao tiếp với ban giám hiệu về việc lên các kế hoạch giảng dạy, lịch tuần, tháng, họp hội đồng, lịch công tác, các văn bản mẫu, giao nhận việc..

Hẳn các lãnh đạo giáo dục đã thấy được tính cấp thiết đó nhưng nền giáo dục Việt Nam có trở nên hiện đại hay không, vẫn còn phụ thuộc nhiều vào những hành động mang tính quyết liệt của quý lãnh đạo.

Trên là những ý kiến đóng góp cho nền giáo dục nước nhà hi vọng có thể góp một phần nhỏ để nền giáo dục Việt Nam có thể sánh bước với bạn bè quốc tế.

Nguồn: vnexpress.net