    
|
|
|
|
|
|
|
|
|
 |
Just over four years ago, I decided to take a part-time position teaching website design and front-end development at a local university, the University of Rhode Island. My time in the classroom has been one of the most challenging as well as one of the most rewarding experiences in my career, and I believe that other Web professionals would greatly benefit from spending some time in an educational setting teaching others their craft.
In this article, we will look at some of the challenges to prepare for if you are considering taking on a teaching position. I will also present some of my personal experiences and insights, including the benefits and rewards I’ve enjoyed as a teacher, to help you consider such a move for your own career.
Let’s start by looking at some of those aforementioned challenges as well as the solutions I’ve used to meet them over the years.
Where you teach, as well as the variety of students in your classroom, will have a dramatic impact on your overall experience. Over the years, students from all walks of life, age groups and experience levels have taken my course. The only constant is that every one of them is completely different — which poses quite a challenge when preparing materials and exercises for the class.
Ultimately, your job is to do what you feel would help the students understand the concepts best. Yet, no matter how well you prepare, the reality is that your materials will work great for some students and not so well for others. You will not be able to reach all students equally because everyone learns differently.
Everyone learns differently, and your responsibility as the teacher is to respond to those different needs. (Image credit: opensourceway)
As you receive feedback from students and realize which ones get it and which ones are lost, you will need to adjust your lesson plans to make sure that you reach all students, not just best and brightest who understood the concepts right away. Of course, part of the challenge is that you must strike a balance here. You’ve spent time carefully considering and building your lesson plans, and you don’t want to blow it up and redo everything because a particular student did not respond well to them. Instead, find ways to get those slower-paced learners up to speed.
I had one student a few years ago who found it difficult to keep up. He was always falling behind, and he felt bad about asking too many questions and holding up the rest of the class — but by asking fewer questions, he fell further behind, and the problem just worsened. Eventually, I suggested that he bring in a digital camera to record the lessons so that he could go over them again later at his own pace. I wasn’t thrilled about the idea of being recorded, but I felt it would help him, so I was open to the idea.
The change was immediate. Watching the recordings at home and going through the lab exercises for a second time at his own pace, he found that the lessons began to make sense and that he was able to keep up in class. His final project ended up being one of the best of the group — a dramatic turnaround from where he started in the course.
That being said, the reality is that some students, no matter how much extra attention you give them or how responsive you are to their learning needs, will just never get the material. Unfortunately, I’ve had to drop a number of students from my class over the years. Despite my best efforts, including extra materials developed specifically for these students and extra class time to answer their questions and tutor them, they simply didn’t understand the concepts being taught.
In most cases, these students tried incredibly hard. They put in the effort required, but the results weren’t there and the rest of the class was held up because of their struggle. Having to sit down with those students and explain that I didn’t think they were right for the class is easily the most uncomfortable thing I have had to do as a teacher.
Failing to get through to a student does not necessarily mean that your material or teaching approach is bad. In many cases, it’s not you, it’s the student. (Image credit: D Sharon Pruitt)
If you are going to take on a teaching role, be prepared to make difficult decisions. As uncomfortable as these conversations are, they are sometimes necessary for the good of the class.
The Web is constantly changing. Lesson plans and exercises that were relevant one semester may be woefully outdated the next. As the Web evolves, so too must your lesson plans.
When I began teaching over four years ago, responsive design hadn’t yet become the best practice it is today. Now, it is one of the most important aspects of my course. Despite all of the work I had put into the class materials, I had to pretty much start from scratch when I decided to introduce responsive Web design into the lessons.
Make sure to teach skills that are relevant to the industry today, revisiting your lessons after each semester and making changes as needed. Most of the time, I need to make only minor changes to course materials; I rarely have to start from scratch. Either way, though, prepare to revise your lesson plans regularly if you hope to keep the course relevant and up to date. Furthermore, understand that your time in the classroom is just a fraction of the time you will have to spend preparing for the class.
Speaking of time, another challenge is that you have only so much time with the students. So, you need to pick and choose exactly what to present according to what you feel will serve them best. If your classes are like mine and many of your students have no previous experience with Web design, HTML or CSS, then you’ll need to start with the basics. Giving students an understanding of basic design principles and introducing HTML and CSS all the way up to the most current best practices is a tall order. In the end, you have to leave some things out and accept that you can’t teach students everything.
Take support for Internet Explorer (IE) 6. Finding ways to support that old browser has consumed countless hours for those of us who have been in the industry for years, but we don’t struggle with it much these days because use of IE 6 is now so low. Among most of the websites I have worked on lately, IE 6 does not even factor in the user base. Because of this, I have decided not to discuss the challenges of IE 6 because I do not feel it is relevant to the work the students will do once they leave the classroom. If we covered IE 6 support, it would mean we have that much less time to cover something else. The challenge is to decide what is more (and most) important and to make the best use of the time available to present those concepts.
As a side note, websites like Smashing Magazine and other online sources that have built an archive of articles about Web design topics over the years are an invaluable resource for those of us who are teaching the next generation of designers and developers. So much of what we do today is built on the practices of the past. The history of our industry is important, but finding time to present all of that history in the classroom is hard. So, referring students to topics and articles to read is an important strategy for teachers. This is why these archives of articles, which might not seem relevant to today’s best practices, are so important and why decisions like .NET Magazine’s to drop thousands of old articles when it resigned its website is such a problem.
As Andy Clarke states in his article “Preserving the History of Web Design,” we need to ensure that new professionals in our industry learn this history, “to learn about the progress we made so they don’t undo it.” Unfortunately, we cannot cover all of that history in the classroom, so the challenge is to figure out how much of it to present and how much to refer them to for review outside of the classroom.
You will be the first Web professional who most of your students have ever met or been able to speak with at length. To them, you represent the industry. The stories you tell and the opinions you share will shape their own understanding and opinions of the industry. That is a pretty big responsibility.
Always keep in mind that you play a major role in shaping your students’ understanding and opinions of the Web industry. (Image credit: Dell Inc.)
We all have bad days, but taking negativity from the office into the classroom will absolutely affect how your students see the industry. You don’t have to present the job as being all rainbows and gumdrops, but be mindful of what you say to students and avoid using the classroom as a place to blow off steam, regardless of how bad your day is or how frustrating an exchange with a client has been. Complaining about clients is never productive or appropriate, and too many in our industry relish the opportunity to share bad stories. Doing this with students gives them the wrong impression and trains them not to respect clients.
You have an opportunity to set these new Web professionals off on the right path. By maintaining a positive outlook and by exposing the students to the best parts of our industry, you can help to cultivate designers and developers who will help our industry continue to grow, instead of hold it back.
Building on this theme of responsibility, you are absolutely responsible for what you put into the world. I have heard many Web designers echo this sentiment as they look to do work that has meaning and that makes a difference. The projects and clients we take on and the websites we launch into the world are our responsibility — and that responsibility is multiplied many times over when you decide to become a teacher.
As a teacher, you are at least partially responsible for the work your students will do. When your students go on to do great things, it is awesome. One of my students a few years ago took a position with an important non-profit organization in our area. Seeing her work make a difference for that organization and the people it helps was extremely gratifying.
Unfortunately, not all interactions with former students end as positively as this one did. Other former students of mine have done really bad work as freelancers. I remember one former student contacting me and asking me to look at the most recent website he had designed and developed for a client. There is no way to sugarcoat it — the website was bad. The design was unattractive, the user experience confusing, and the code sloppy and poorly written. This put me in an uncomfortable position.
He was obviously very excited about his work and was asking for feedback, but any feedback I could give would be negative. In the end, I told him that I was happy to see him working on the skills we had covered in class, and I suggested a few improvements to the website. The student thanked me for my input and made a few changes to the website. Since that time, I have followed his work and seen other mediocre websites that he has designed for clients, but he never again asked for my feedback, nor have I offered it.
This experience was not confined to this one student. Over the years, other former students have taken on freelance work and subsequently launched poor websites into the world. I would be lying if I told you I didn’t feel some responsibility for these poorly done websites, but in the end, you cannot police every student once they leave the class. All you can do is give them the best information and show them the right way to design and develop a website. What they do with that information, for better or for worse, is something you have no real control over.
So far, we’ve looked only at the challenges of teaching in this industry. Those challenges are real and substantial, but if you can meet them, then you’ll also find a number of rewards and benefits from taking on this responsibility. Let’s now turn to some of those rewards.
Helping others can be a powerful experience. Spending time in the classroom to teach others your craft is one way to use the knowledge you have gained to improve the lives of others.
Many of the students I teach are unemployed or underemployed. Their tuition for my class is paid for by a grant set up to give them skills relevant to today’s workforce. Helping these unemployed individuals to better themselves and learn new skills is important work, and seeing students go on to find good entry-level jobs in the industry is incredibly rewarding. Hearing from those students later on that the lessons and conversations in the class helped to prepare them for success really makes all of my hard work worthwhile.
I have always loved the giving, collaborative nature of the Web industry. Teaching students is one way to contribute to the Web community while having a real impact on the lives of others.
One of the best ways to truly understand something is by teaching it to others. While my time in the classroom is dedicated to teaching website design, I would be lying if I said that I didn’t learn quite a bit from the experience as well.
Try to explain the CSS box model or the difference between relative and absolute positioning to a new student, and I guarantee you will understand the concept better than before. This greater understanding and the experience of explaining these technical concepts to students will also help you speak with clients.
Teaching forces you to find ways to explain concepts in a way that others who do not have the benefit of your experience will grasp. (Image credit: opensourceway)
Being able to communicate with clients without being too technical or intimidating, and in a way that helps them to grasp the concepts enough to be able to make informed decisions about their business and their website, is an important skill. The lessons you prepare and your conversations with students can and will equip you for these client interactions and make you better at what you do.
Speaking of clients, I wouldn’t have expected this when I began teaching, but my time in the classroom has led to a number of projects outside of the classroom. Multiple students have passed along solid leads to me because they could not handle the projects themselves with their level of experience. Former students have also invited the agency I work for to bid on projects initiated by the organizations they’ve joined.
Over the years, a number of people have asked me whether I realize that, by being a teacher, I am training professionals who will one day replace me or, at the very least, take work away from me. I’ve honestly never felt that way. I’ve always felt that there is more than enough work to go around. And, as my experience shows, being a teacher and making a positive impression on your students will not only not lose you clients, but could actually generate business for you and your agency.
Hopefully, this article has given you some points to think about as you consider whether a teaching position is right for you at this point in your career. If you’d like to explore this possibility, how should you begin?
My opportunity came when I began telling others of my desire to speak more about our industry and the work that I do. A fellow Web developer who had taught at the university for many years heard me one day and, knowing of an opening at the school, referred me. Within a few weeks, I was in front of my first group of students.
While my experience might not be typical, there is a lesson in it. Spreading the word about your interest in a teaching position could open doors. Do not be shy to let others know that you’d like to explore this move.
Other strategies are to contact your local universities, colleges, and business centers to see whether they have any openings. Sometimes, a little outreach turns up an amazing opportunity.
If you can’t find an opening at an institution of higher education or you feel you are not yet ready for that level and would like to start smaller, consider giving small workshops or classes at a local library or even as a private tutor.
Whatever path you choose to get started, consider what you can offer to students who are interested in learning more about our industry. I assure you that the students will not be the only ones who get something positive from the experience.
(al, il)
© Jeremy Girard for Smashing Magazine, 2014.
]]>
When I was around 16, I got into freelancing for graphic design through a small non-profit. They needed some posters and book covers and I figured I could do that pretty easily. I handled things well for my age and made a couple bucks so I could buy shoes for the first days of school. As I continued to do this, I realized I really liked the work and was even interested in doing some web design. It couldn’t be much different, right?
Boy, was I wrong. I set up shop online and went looking for clients. I got a few in and I immediately realized I wasn’t going to handle this as easily as my print work. There were so many things I had to do and so much information I needed to know about the web in general. I was obviously ill-prepared. Up until about 3 years ago, I was really off-and-on with web design just because it was so taxing.
Fast forward to today and I have a new outlook on web design. Many of the struggles I went through with my web design clients, I figured could be taken care of in a variety of ways. I look back today on my mistakes and notice what I could’ve done better. Here are 7 huge mistakes I made then that I try not to make now.
We are creatives and we tend to do things creatively. Unfortunately, that means some of us forget about contracts, briefs, proposals, etc. However, this is one of the most important things you could have as a designer of any kind. Your paperwork allows you a point of reference with clients when things start to go awry.
Contracts are hard to really I up if you don’t have a lawyer. Briefs are typically something the client comes up with and you follow it. Because I work with smaller businesses, I typically write up proposals (much like bids). In these proposals I go over my entire process from start to finish. I also include any design features I’d like to implement and any other recommendations.
At the end of my proposals, I also include a list of prices. I give options for items as well (for example, web design only and web design with WordPress development). The idea is to be as clear and concise as possible. Once, we agree, we move forward and I have an invoice.
All these things allow me to stay on track, it clarifies the project and allows me the opportunity to go back over things if there any discrepancies. This is extremely important in web design, especially if you are attempting to run this as a lucrative business.
I’ve done this before and it does nothing but set me back. There are times when my first draft’s deadline is due or I’m just dragging my feet about a project. I open up Photoshop and just throw stuff around. I don’t name my layers, make a grid, or even make swatches. I just wing it.
This is a huge mistake. Many times I assume that the client may dislike and want another design. Rarely does that happen — they almost always want minor changes. The issue is when it’s time to make these changes, nothing is in order and I end up adding even more time redesigning and fixing things.
Even if you are close to a deadline, I’d recommend taking your time even on the first drafts. They are important. I’d also tell you to make sure every piece of your work and project is organized, especially if you hand off the editable deliverables. Name your layers, create swatches and keep it clear and concise.
After a certain time you start to believe in yourself as a web designer. Sometimes you might even start to think you don’t need to sketch out your ideas. You’ll just open Photoshop or even your code editor and dive right in. You may be good, but that’s just a bad idea.
Sketching allows you to make mistakes and figure out your solutions as you go. Going right into your first draft doesn’t necessarily allow you that. Sketching out your draft also allows you to beat any type of creative block. Sometimes you just don’t see it on the screen as well as you do on paper, where you can erase and edit as you go — you know it doesn’t have to be perfect there.
Aside from creatively, sketching your ideas down allows you to figure out how you can see this web design responsively. Many times I’ve just created a regular desktop site and hoped for the best. When drawing your ideas out, you can really get an ideas as to how you want your work to be seen in all sizes. Sketching isn’t just a thing for artists, but it’s a great way to gather thoughts.
One of my least favorite parts of designing and developing is the testing phase. It is an easy step to want to skip because it’s almost always the part where the most things go wrong. It’s still amazing to me how a website can look perfect in one browser and awful in the next. Because of this, we’ve got to do extensive testing to make sure it works everywhere.
There are many short cuts for this step including patches and websites that act as different browsers. However, I’ve found most of these don’t work and can end up making the situation worlds worse.
Whether you’re testing for responsiveness or just across browsers, try to make sure you have many of these readily available. To avoid lots of testing make sure your design and your code are perfect beforehand. Good clean design and code can go a long way.
It’s happened to us all. We need to implement some new thing into our design that we’ve never done before. So, we research it and it seems like it can’t be that hard to do. Right?
Wrong. Learning on the fly is never the best idea especially if you are working on something with a deadline, for a client and/or with a partner. The reason is because most times we don’t have a great understanding of it. Sure we can copy and paste code, but when it doesn’t work or messes with something else in a design, we probably aren’t all that skilled at fixing it.
Obviously, I’m not saying you shouldn’t learn new skills. Learn as much as you want, but in your free time. When you need to do something on the fly, try to find someone who knows what they’re doing. They’ll get it done quicker and much more effectively than you may be able to. And when everything is all done and perfect, you can even ask that person to teach you a few things.
Designers like to think of themselves as problem solvers. Design is our method of trying to fix things. For example, if a client’s website isn’t converting like it should, we’ll take a look around and recommend some changes. That’s how we (should) operate.
How we fix the problem is what makes us all different. We strive to find the correct solutions in an innovative way. However, many designers make the mistake of trying to be too innovative and creative by trying to reinvent the wheel or come up with brand new solutions.
Of course this is not absolute, but the point is there are solutions to all problems out there, we just have to find them. If the website isn’t converting, you don’t have to make a new script or piece of code. It could be as simple as a sticky button or call to action.
We can show our creativity through the execution of the ideas. Apple didn’t invent the MP3 player but they executed it better than anyone else.
With your execution, it’s important that you don’t over-design. What I mean by this is cluttering your pages, having way too many colors and making things confusing.
While designers solve problems, we want to do them in a way that’s still aesthetically pleasing. The task is to always make sure our designs are legible, readable and easy to use. As I say time and time again, you want to design in a way that’s intuitive; pretend like someone has never seen a website before and design for that person.
It seems like there are a lot of rules to designing for the web. However, it’s just about being smart with your workflow and your designing. It’s rare to get a web design project where things go smoothly as that’s just the nature of the industry. However, these are just ways to make sure you can do everything humanly possible on your end.
What mistakes have you made in the past that you try to avoid? What mistakes do you see others making? Let us know in the comments.
| Trickster for Mac: Quick access to your latest files – only $4.97! |  |
|
|
|
|
Gizmox’s new WebGui v7 was built for Microsoft Visual Studio developers building business apps.
]]>|
|