Personal growth is important, knowledge and experience only come from a couple of ways: -
1. You spend a lot of your own time learning and broadening your horizons.
2. You are placed into an environment (or environments) whereby you can learn from others and the experiences around you.
If a company really wants to keep someone they can just throw cash at them until the person wanting to leave is left with a Hobson's Choice.
I realized some time ago (check out my 2006 review post coming in the next few days) that the only real way for me to grow at a rate I was happy with, was to leave my current employer and attack work on my own, to pick and choose the projects which excited me and made me enthusiastic again.
It's a real shame when I see talent being wasted because of the selfishness of others. Good people should be allowed to explore all the avenues that are open to them, and a company should not hold people back from doing that, personal growth is massively important to morale and personal wellbeing of the individual and of a team more generally.
Every company has "churn" (the turnover of development staff) and this is a good thing, bringing in new ideas and a new perspective pushes developments forward (with the right management (that's a whole different post!)), there's also great benefit from getting rid of the old, the dead wood in some circumstances. There are those people who have been in the company for years and their answer to many questions is "Well, we've always done it that way.".
That same churn is good for the individual within companies, people come in with new fangled ideas like ohh I don't know, testing applications before shipping them for example, that's a good for everyone. We learn from each other, I love spending time with other MVP's and ASP Insiders, I learn so much, I feel challenged and it pushes me to new unexplored areas of my own technology theatre. The same should apply to the workplace.
When children in school are identified as being gifted in any area it's important that their potential is pursued, this same argument should be the place in the work place, and if a company cannot fulfill the potential of an employee they should not block the progression of someone by holding them back through any means of bribery (be it offering more money to stay, imaginary promotions or false promises). The companies who do that are wrong, very wrong in my opinion.
I hope this post helps two types of people: -
Bosses who are about to bribe someone to stay.
Employees who are about to be bribed to stay.
I'm going to be judging the Imagine Cup this year in the Web Development arena. The job seems daunting as we're expecting over 3000 teams to enter the Web Development competition alone.
The theme this year is all around Education and by that, it's a really broad definition of Education, it's not necessarily academic education so applications could be anything from Video Learning through to web based Recipe Books.
So what's important when you're thinking about building a web site? Reach, Accessibility, Innovation, Usability and Maintainability are the five main factors I'd be looking to make the best web sites.
When you're working with web applications 'reach' is a very important aspect of the development. Reach is all about how many people can see and use your application. With Web applications it's very much a matter of can people use the same application on lots of different browsers. Internet Explorer, Firefox and Safari are the big three at the moment, with Opera being next on the list in terms of popularity.
As well as the number of browsers, Reach also covers some other areas, such as geographic. Geographical Reach is about making applications available to people who are in different places, Web applications are very good at this because they run on browsers and work over the web, so all a user needs is a browser and an Internet connection.
Cultural Reach is all about making sure the users of different backgrounds and skill levels can access and use the site. I'll cover Cultural Reach a little further on in this post when I discuss usability.
Expressing dates and times is another huge issue when we're talking about Reach. People around the planet are in all sorts of timezones and webservers are rarely running in the timezone that the user is in. Ensuring you clearly communicate times to users is a very important aspect of applications where there is any kind of concept of "live" data. For example, when looking at the datetimes of a list of blog posts which are values like "10 Jan 2007 10:00" it's impossible for users to know what time zone that relates to, but placing in text which tells the user the blog was posted to "Three Hours, Twenty minutes ago" is very clear regardless of timezone.
There's another big thing with Dates that's important to understand and that's international date formats. In the UK for example we use the dd/mm/yyyy date format, whereas in America the standard is mm/dd/yyyy, this can be very confusing if you look at a date such as 07/10/2006 as it's impossible to know which date format the date is following, so it's always important to be clear about the date format, the safest way is to use the dd MMM yyyy format which is 01 Jan 2007, simple but very effective.
Mike Taulty created a fantastic diagram (below) which shows how the Microsoft current technology offerings all fit together in relation to their "Reach".
A massively important area in education is the need to deliver material and services to all. People with disabilities can have a really rough ride on the internet. Accessibility is very important and it's something which has already been massively documented by the W3C in their Web Accessibility Initiative web site.
"Web accessibility means that people with disabilities can use the Web. More specifically, Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with the Web, and that they can contribute to the Web. Web accessibility also benefits others, including older people with changing abilities due to aging."
When building a web site it should be made accessible. It doesn't matter what it is, it should be accessible to all, there are no excuses, and it's even become a legal obligation in many places.
There are a few guidelines to follow which will ensure accessibility, this isn't an exhaustive list and should be combined with the advice in the usability section.
- Provide equivalent alternatives to auditory and visual content.
- Don't rely on color alone.
- Use markup and style sheets and do so properly.
- Clarify natural language usage.
- Create tables that transform gracefully.
- Ensure that pages featuring new technologies transform gracefully.
- Ensure user control of time-sensitive content changes.
- Ensure direct accessibility of embedded user interfaces.
- Design for device-independence.
- Use interim solutions.
- Use W3C technologies and guidelines.
- Provide context and orientation information.
- Provide clear navigation mechanisms.
- Ensure that documents are clear and simple.
When you follow the guidelines you'll find that your applications are easier to use by everyone, not just those who have disabilities or learning difficulties.
Again there is an Accessibility tradeoff, sometimes you need to sacrifice accessibility to provide a richer interface or deliver content in the format you require. This isn't always a bad thing, but you should think in depth about this topic, again, no rules, just use common sense.
On the web it's very important to make sure your site is innovative without being too wacky. Flickr is innovative in how it handles images. Google was innovative with GMail and it's search based navigation. Microsoft is innovative with their 3D mapping on Live.com. Innovation is about making people go "ohhhh" and "ahhhh".
I think the best definition of what innovation is comes from the British Government's Department of Trade and Industry. They say: -
"[innovation is] the successful exploitation of new ideas"
So how do you innovate? Well it's a simple matter of coming up with a great idea and implementing it well. That's what will differentiate applications between.
Your web site should be very much like Marmite, people should love it (or hate it). If it falls inbetween those two it's in the Zone of Expendibility. Getting noticed is all about innovation so think long and hard about that when designing your applications.
How easy is something to use? Does something irritate you, make you irate when you use it? Usability is all about making sure people find your software a breeze to use.
So how do you know if something is usable? Well, take a look through This Is Broken, which i a site that covers all the stupid decisions people make and how it impacts users. There's a video of Seth ranting at what's broken in the world which is fantastic.
The United States department of Health and Human Services publishes a Usability book online which covers many great topics in and around Usability.
To me, usability is about one thing and one thing alone, me (not me but you), it's a very personal thing, which makes it very hard to understand usability because what you have in your head is what you see as right, and so it can be dangerous if you're looking at your applications and developments with rose tinted glasses.
What actually makes something usable isn't a set of rules I can outline, all I would say is: keep asking yourself Could this be easier?, Could this be more obvious?.
The web moves quickly, so it's vitally important that your applications are easy to change and update. The art of maintainability come from experience in having to maintain both your own and others applications.
One area that most people ignore is the naming of items within their applications, this can be anything from variables through to naming of tables and columns in databases.
Dim i As Integer
What is i? Is it the number of sheep on a farm, or the count of iterations a loop has been through? NumberOfSheep would be a better name, it tells you everything you would ever need to know and means when reading the code people can instantaneously work out what the variable is and what it's for.
There are lot's of different types of coding conventions, the one you choose is down to you, just ensure you're consistent in what you're doing.
How about databases? Well they have their own rules and advice on what makes them maintainable, I wrote about this in Professional ADO.NET 2 (Chapter two). Again, there is not a "right way" just better ways and worse ways, it's all about personal preference, just be consistent.
Encapsulating commonly used functionality is a great way of quickly achieving maintainability.
Breaking up your applications into defined tiers is a great way of improving their maintainability. Why though? Well, the more decoupled each of the parts of your application are, the easier it is to swap out those parts thus improving the maintainability of your applications.
The common three-tier architecture has a Presentation, Logic and Data tier; each controlling their own areas, this is a good model to follow and you will reap the benefits from going down this route.
One last point on maintainability; if you have an unmaintainable application then it's important for you to look into refactoring, that will enable you to take your spaghetti code and make it beautiful.