Menu Search
Jump to the content X

The Web Design Community Offers Advice To Beginners


At one time or another, we are all newbies. That’s right: you can deny it all you want, but not one of us got into this game with a full deck stacked in our favor. We entered as newbies, born fresh after the start screen loaded. However, unlike in a game, we are not immediately launched into a tutorial level to learn the ropes in this new world — what to avoid, how to progress, etc. And if we feel overwhelmed by our newbie status, we may not be able to find our way to the tutorials and guides that the community has put together to help us sort all of this out. So, feeling very alone in all this is easy.

Jumping in a new passion can be difficult and time-consuming at first. The support of the community can be extremely helpful in overcoming the learning curve and helping to find the right route for your career and your professional skills. Image credit1.

But this is the great thing about being part of the online development community — that you are never truly alone. Your experience may be unique in its details, but it’s not generally, which is great because the community is very open to sharing its experiences and offering guidance to help newbies navigate the twists and turns we are sure to face as we continue down the developer’s path. In most cases, all you have to do to get some helpful advice is to venture into the social media neighborhoods and ask the community at large. At times, the answers just pour in.

That is what we found when we went out on Twitter2 and on Facebook3 recently to poll our followers and fans. We asked “What is the single best tip from your experience that you would give to newbie developers?” This article is the result of all of the amazing responses we have received. Before we go any further, we would like to thank those who took the time to answer our query and who offered so much great advice to all the newbies out there in the development arena. As usual, the advice also serves as a nice refresher to all those seasoned veterans who have been in the game for a while.

Never Stop Learning Link

This answer, which we received repeatedly, is by far one of the best pieces of advice for newbies in the development field: never stop learning. This truly is one to keep in mind as you tread through this new world, because working in a field as dynamic and fluid as development, you can quickly fall behind if you do not actively strive to stay ahead of the curve. Without somewhat of a dedicated effort on your part, your progress could stall, and your skills and work could stagnate.


Once again, the online community and so many others have your back in this respect. So many wonderful books, blogs and other accessible resources are teeming with knowledge, just waiting to be absorbed and passed on. So, read. Implement and practice what you have learned. As noted in the replies below, trial and error is a fantastic method of self-teaching. You might even go so far as to schedule some kind of weekly assignment for yourself, to always keep your skill set growing.

  • Start with examples and muddle around with them. Change every line of code to see what it does. Then learn why those things work.
  • Be a sponge. Don’t let pride get in the way of learning from others.
  • Never stop learning.
  • Read. Oh god, read so many books on the subject that force you to practice things over and over again.
  • Learn how to learn for yourself.
  • Never think you’ve learned it all.
  • Don’t pretend you know all. Blogs and forums are your best teacher.
  • Read the docs. Don’t reinvent the wheel. Test. Learn.
  • Don’t copy and paste. Learn.
  • Always have a project on the go. It makes sure you keep learning.
  • Learn by putting as much as possible into practice.
  • Always learn more. You should never be 100% content, and always strive to constantly improve your skills.
  • Never stop developing their skills.

Take Criticism Constructively Link

… No matter how it is given. This is another important piece of advice that is both vital to learn and extremely difficult for some to do — especially because the anonymity of the Internet seems to give so many license to forget one half of the constructive criticism coin; they instead berate and belittle through their comments and their assessments of the developer’s talent. But no matter how harshly they come at you, find a way to distill the essence of their statements to see if you can gain anything from them. If they have no merit, let them go.


One thing to always remember, as pointed out in the advice below: never take criticism of your work personally — especially given that in this field we are never supposed to stop learning. We should always welcome feedback from others in the community that helps us improve. It is simply a means of keeping our skills sharp. Inviting open criticism allows others to help open our eyes to new approaches and even problems we are entrenched in. Also, thinking of it as feedback and not as “criticism” might soften the blow for you. After all, who doesn’t love feedback.

  • Be open to feedback as everything changes.
  • Learn to love criticism.
  • Test in every browser/OS config you can. And don’t take criticism of your work personally.

Be Patient Link

Here is another major tip to hold onto: be patient. If you can master this one, then you will have saved yourself many sleepless nights and hair-pulling-induced headaches along your journey to greatness as a developer. Remember that these skills do not develop overnight, no matter how much we wish they would. This journey is just that, a journey — not a direct flight to the final destination. Getting to where you want to be will take time.


Take your time. Don’t rush through the learning process too quickly, or you will likely burn out and get frustrated. Take the slow route, making sure you completely grasp one area before moving on to the next. If you hurry, chances are something important will slip past you. And as you work with others in the community, be patient with those both behind and ahead of you on the learning curve.

  • Have patience… a lot of patience. And if you have to get IE6 to work, start a pot of tea or something to calm yourself. :P
  • Have patience: with yourself, others and especially the code. :)
  • Take all the time you need to learn the basics. They are fundamental.
  • Prepare for frustration.
  • No matter how stupid what your client just said was, think before you reply.

Comment Your Code Link

Another pearl we found in the plethora of replies is a wonderful coder’s mantra (or at least it should be): comment your code. Comments are a powerful aid to new developers for many reasons, the main one being that learning through repetition is a fantastic way to make information stick. If you constantly comment on why you used a particular bit of code or how another bit works, then each time you return to it, you will be further cementing it in your brain.


Also, comments can provide just as much benefit to others who will be interacting with your code. Remember, it is not always about you. Comments are a way for others to learn from your work, just as you have learned from the code of those who came before you (if in fact they did think to leave comments). If you work with other developers on a project, this is an easy way to keep each other informed on why someone coded their part the way they did. It demonstrates professionalism, too, so keep up the comments.

  • Thoroughly comment your code! It will help infinitely in the long run.
  • Always use detailed comments. At some point, someone else will look at your code. Do them a favor and comment like mad.
  • When commenting: describe why not just how.

Be A Helpful Member Of The Community Link

This next bit of advice ranks quite high for many developers, not just because of its obvious benefits but because of the reward one feels from doing it: be a helpful member of the development community. It could prove to be an invaluable asset in your arsenal, not only because the lines of communication that you open will create great learning opportunities, but because you are building lasting relationships that you can call upon later when you find yourself in need of assistance.


Those of us who have gradually moved through the ranks have especially relied on these resourceful posts and helpful guidance to make the most of our skills and code. We should really stay active in the community and give back when and where we can. Paying it forward for all of those who have paved the way for us is not only an obligation; we really should want to help this community of ours thrive and grow. Reaching out through social media outlets, blogs, forums and more can really improve one’s skill set and viability.

  • Get involved in the design and Web community as quickly as possible.
  • Peer code reviews!
  • Set aside time to help other developers. It could be in online forums. It really helps you reflect on what you know and don’t know.

Learn The Business Link

Learn all aspects of the business side of the industry, especially if you are freelancing. We got a few responses about this. And it makes sense. If you want any kind of sustainability in your career, then having a solid grasp of the business side of things is important.


Knowing how the business operates and what clients generally expect will prepare you well for a freelance career… and will also keep you from being taken advantage of. If you learn the general pay scale and expectations of players in the field (including those of clients and other developers), then you’ll be well prepared to set your own rates and expectations. It also teaches you how to handle paperwork, which can be cumbersome and potentially overwhelming if you are unfamiliar with this side of the business.

  • You can only make so much money coding. Learn the business.
  • Quadruple your hourly estimate.
  • Make a careful and detailed estimate. Now triple it. You’re probably close to the truth.
  • Your estimates will suck for a long time, so be as conservative as you can, and offer discounts on overage.
  • IE6 is a bitch!
  • Choose your clients wisely. Bad clients end up costing you time and money.

If You Don’t Love It, Leave It Link

Some other words of wisdom that were passed along can be summed up like this: if you don’t love it, then this is not the right work for you. Developing is more than a job; it is a career — beyond that, even a way of life. Coding changes the way you see and interact with the world around you. It challenges you every day with something new to conquer or sort out. The hours seem to keep piling up, and your brain becomes harder and harder to switch off, continuing to solve problems long after you have bidden it to rest.


This holds especially true for freelancer developers. As a freelancer, you are so much more than the person behind the code: you are the person behind it all. This is where your love of code comes into play ten-fold. Passion goes a long way in development. True passion for what you do comes only from loving it. You can’t fake it, either. A lack of passion not only will reflect in your work but will impede your progress.

  • If it is just a job for you and you do not look forward to breaking nights, find another job.
  • Love what you do, and remember those who taught you.

Make Time For Yourself Link

Another bit of advice to keep you sane as you grow is to make time for yourself. The best way to do this is to keep some sort of side project going. There are many reasons to do this, your sanity being the main one. Staring at code for hours on end takes its toll, especially if your code is failing and a solution escapes you. One way to fight off this madness is to have something to work on that lets you unplug.


A side project gives you an outlet to recharge and sustain your interest in the field you have devoted yourself to. Make no mistake: this is a time-consuming career path, and without a side project to keep you engaged, you will quickly burn out. The work that once enthralled you will lose its appeal, and the passion that got you to where you are will fade. A side project also ensures that you constantly learn. You can choose projects that challenge you in ways that you don’t find in work for clients.

  • Keep sane with a side project of your own.
  • Work on a real project every day, even just a personal one.

Believe In And Be Yourself Link

Another powerful bit of advice offered by the collective that we polled was to always believe in and be yourself. Given people’s tendency to aim for the throat when “critiquing,” these words of wisdom are especially potent. Allowing negative words and disparaging character assessments to lower your opinion of yourself and your abilities will deflate your momentum.


Always be true to your personal voice. Don’t compromise it while finding your way. You want to carve out a truly individual path, and that includes your voice, too. So, don’t try to imitate others who have found success. As noted below, never try to be someone else, because that never works the way you hope. Being inspired by others is fine, but don’t lose your identity and voice in the process.

  • Believe in your qualities. Never try to be somebody else. Life is too short for that.
  • Don’t quit! Hang on! Everything will work out fine.

A Few More Words Of Wisdom Link

Below are other responses that we couldn’t just leave hanging in the Twitterverse:

  • Try everything yourself before asking someone else (trial and error to the max).
  • Find your niche and focus on it until you are an expert.
  • You could probably code it well, but there is a fair chance that there is a time-saving jQuery solution.
  • Think of the visitor who is trying to find out something. They need to understand what’s going on, not just be impressed.
  • Some bridges just have to be burned.
  • Web developer? Practice sleeping less.
  • Don’t scoff at new ways of doing things because you don’t initially get them, nor should you embrace them without honest evaluation.
  • Stay informed about the direction of the Web. There’s a lot to learn, and along the way you’ll pick up skills.
  • Google before you ask.
  • RTFM!
  • Use source control. After that, comment your code.
  • Never write anything but standards-compliant code: faster, more reliable, and you won’t have to fix it when new browsers come out.
  • Regression test.
  • Do not fall in love with the code you write.
  • Put functionality first. Beauty comes in second place.
  • Don’t be cocky.
  • Focus on one subject at a time. Start with CSS.
  • “Stay hungry, stay foolish.”
  • Learn to write and format your own code cleanly and in as few characters as possible.
  • Run away from clients with red flags.
  • Take the most pride in your team’s code, not your own. Don’t complain when people edit your code. Enjoy how it improves.
  • All the stuff you say about all the old code you read, someone will say about your code in 10 years. So, knock it off. :)
  • Stay organized. It’s the key to success.
  • It’s never a hardware problem.
  • Logical, step-by-step thinking will solve any problem you encounter. No doubt about it.
  • Find a good IDE (like Aptana4).
  • Appreciate the design in front of you, and design in general.
  • You don’t fully understand something until you can explain it succinctly to someone else. So, learn → do → teach.

Below are a few more articles and resources to help the newb start off on the right foot, armed and ready. If you have some time, we recommend checking them out.


Footnotes Link

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8
  9. 9
  10. 10

↑ Back to top Tweet itShare on Facebook

Rob Bowen is a staff writer for Web Hosting Geeks and Top Web Hosting, a longtime freelance designer, and burgeoning videographer and filmmaker whose creative voice and works can be heard and found around the web.

  1. 1

    Good job man. Will share this with nub friends lol

  2. 2

    I miss: learn to present your work. A good presentation does more than anything.

  3. 3

    “comment your code” is the one that lingered in my head after reading… beautiful, thanks!

  4. 4

    Great article, but was it really necessary to double up the title in a graphic?

    It just seems like they were thrown in there to break up the article :P

    • 5

      Matt, can you please be more specific? I am afraid I am not sure what you mean.

      • 6

        You’ve got the title “If You Don’t Love It, Leave It” and then one sentence below the title you have a graphic that says “If You Don’t Love It, Leave It”. Rinse, repeat.

        It’s just a tad redundant and seems unnecessary, but I may be the only one that thinks that. Just thought i’d speak up.

        • 7

          Ben @

          August 18, 2010 6:24 am

          Dont really see the problem with the images and titles repeating themselves, those images could have been done in CSS3 though, that would have been interesting :-)

          Nice article though.

        • 8

          Oh yes, I think that too. I think using appropriate image can better enhance the article rather than repeat the same words in the image just like the title.

        • 9

          My thoughts exactly… the images seem redundant…. a photograph (almost)depicting the title would have been a lot better!

        • 10

          I think so… another advice for designers: Don’t repeat text in titles and images (only for replacement in some special cases) :)

        • 11

          I totally agree that it’s redundant. But if it going to be done anyway, use CSS!.

  5. 12

    This article is a further example of how amazing the design community is. I’d add that IE8 is a bitch too!

  6. 13

    Thanks for the great article!!! Definitely will come in handy! It’s just what i needed as am a nub myself!! :) Thanks again!

  7. 14

    This post is making me smile right now. This may be one of the few “newbie-friendly” posts I’ve read recently.

    Best advice from the list: Never stop learning. Newbie or not, designer or not, it kind of is the best advice in life, isn’t it?

  8. 15

    Thanks for the great article! Learning is the key and stay motivated !

  9. 16

    nice article, once again.

  10. 17

    Great stuff Rob! While this article is geared towards developers it all holds true for designers as well!

  11. 18


    Great article, I wish there was such a post 10 years ago when I started.

  12. 19

    One martial art concept I recently learned probably is a good addition to this: Shu Ha Ri (Roughly translated as: Learn, Detach, and Transcend.)

    Those old martial art Sensei’s thought of everything… even when you’re coding…

  13. 20

    man oh man
    did I enjoy this post

    more of “Robert Bowen” please
    thanks :)

  14. 21

    You know what, I am not even half way through reading it and yet down here to comment ! Why ? Because I am just loving it !
    OK, now back to reading it full.
    Thanks Robert, thanks SM.

  15. 22

    Networking tip: Be selective about your role models and friends.
    Confidence is attractive but snarky, arrogant designers are not usually the best teachers, or designers, or business people …
    Seek out peers and mentors who still enjoy the field, can see merit in your ideas, and offer you constructive, honest feedback.
    Do the same in return.

  16. 23

    Quiet awesome article again guys! I love how the designer community helps each and every designer to be (more) professional. Surely this is one of the best communities in the world and I assume it’s because we realized that helping each other is worth more than hiding and selling our technologies and tricks as almost all the markets do. There’s no reason to keep anything in secret and don’t give tips for beginners. I’m coming from Hungary where there is a kind of common principle as “don’t give your tricks and tips away because you just help your competitors this way”. Well, I totally disagree with that approach and I’m so happy to see that I am a member of this community that is definitely thinking in an other (and so much human, intelligent and successful) way internationally. Robert thanks for this article! – aaron kato

  17. 24

    Great read Robert – this is great for all aspiring & novice designers / developers – myself included. Thanks for the post!

  18. 25

    Great points and guide, Robert! Mentoring people entering the field is a karmic effort and important to the industry itself. Our strength is in unified numbers working towards the same goal; a sound and professional industry.

  19. 26

    Good article, but I’d like to make a point on this quote:
    “Find a good IDE (like Aptana).”

    ~It’s less about one specific piece of software but more about our entire development environment (*coins EDE here*), find your most productive operating system, editor, figure out whether you prefer an IDE vs. bash-fu and text editors, etc…

  20. 28

    This is a good list which also doubles as a good reminder for more experienced designers, but the thing that struck me the most was the importance of commenting on code. It really does save time later and is a lifesaver if in the future someone else is working on the project.

  21. 29

    I have got to say…excellent article. Do what you love and love what you do. If you’re in this for the money you’re not going to stick around (well…the money is pretty good).

  22. 30

    Great job! I love it!

  23. 31

    If you have another career option; take it! :) That’s my advice hahaha.

  24. 32

    Comment your code is one of the best points I think new designers can take and apply right away.

    Code is at the heart of what we do as designers and commenting is essential to better understanding for yourself and others in the community. Those that comment also teach themselves and offer quick references for the future.

  25. 33

    “Some other words of wisdom that were passed along can be summed up like this: if you don’t love it, then this is not the right work for you. Developing is more than a job; it is a career — beyond that, even a way of life. ”

    I think this is poor advice. Many very talented developers do not necessarily “love” what they do. and most of the most skilled, and successful developers find a way to make it no more than a career. Life is too important to let it pass you by while you’re designing fleeting, ephemeral, and temporary things.

    I would advise aspiring developers to do the exact opposite. Remember, it is only a career. To embrace from the outset that what you’re doing will ultimately result in an existential crisis of sorts- that what you’re creating will change, fade, die and be gone. Whereas writers have their books, architects buildings, politicians make policies, doctors cure people, and old-school print designers have their magazines to remember their work, many of us are pouring our hearts and minds into things do not and are not meant to last. Basically being a web-designer for a career is to be at peace with the concept of creating nothing.

    I think that telling someone that they must “love it” or “leave it” sounds arrogant; akin to the scare tactics used by universities on orientation. An order to continue manufacturing the short-sighted workaholic mono-culture that dominates many development firms. To continue an environment where our work is undervalued because we expect passion, individuals devoted to a single-minded cause, so much so that they do not have other passions, wants or goals. I think its important that we as a profession begin to drop these notions of surveying people’s passion at interviews, or expecting web developers to work 60 hour work weeks or to “sleep less.” I think I’d rather work with well-rounded people who have not made their job their “way of life” than work with the overburdened expectations of someone for whom their career is their only life. I also think we’d be misguided to advise talented young developers/designers to turn away from our field just because they might have other interests or possibly even want just a career, and not a “way of life.”

    -Aaron / web developer >12 years, and counting…

    • 34

      I understand what you are saying, but I saw the “love it or leave comment” differently and have an experience to explain my understanding.

      My former career was in a different field of design – special events. Being an artist, eager to learn, and constantly improving, I moved up, way up, on the ladder (so to speak). But I did not LOVE what I did. Before I left, I tried every way I could to embrace the career – poured myself into the color theory, into the focal points, entered (and won) competitions. I pitched and designed million dollar events. People flew me places to design for them. The next steps in that career path were – my own studio, portfolio books, and set trends.

      The pay is terrible, the hours unbelievable (good luck with a dating life and keeping friends when you work every evening and all weekends), and no one outside the field respects what you do. When I realized that the ‘lifers’ truly, TRULY loved their careers, I felt horribly sad for the years of effort and realized I had to make a change out of respect for that industry and myself.

      A job pays the bills. A career is when the job defines you, and you, it.

      If you don’t love your career, you will come to loathe it, which is of no benefit to the others in the field who actually do love it. Staying with a career you don’t love just to pay the bills is like staying in a relationship with someone you don’t actually like just to avoid being alone.

      • 35

        Unfortunately, there are quite a few people out there who dislike work in general, and as soon as it gets beyond the “I’m just having fun with this, trying it out” aspect, they will abandon it.

        On the other side of the coin, there are people who work hard and enjoy their work but there are days when they get quite frustrated with the whole project because it’s giving them trouble and the solution isn’t apparent.

        I think the main point is, don’t just go by what you “feel like” any given day, because you won’t get far in that project or in life as a whole. However, it’s necessary to enjoy your career because you’ll be spending an incredible amount of time on it over your entire life! There are two aspects to recognize.

    • 36
  26. 37

    So many great advices there! Although I can’t really remember them all in practice. I’m learning a new programming language, currently frustrated, but then this article motivates me more. I can refer to those advices when trouble gets in my way.

    Many thanks to SM & Robert!

  27. 38

    Great post, enjoyed the humor. And everything was 100% accurate.

    I especially agreed with/laughed at…

    – IE6 is a bitch!

    – You could probably code it well, but there is a fair chance that there is a time-saving jQuery solution.

    – Google before you ask.

    – Run away from clients with red flags.

    – It’s never a hardware problem.

  28. 39

    Thanks for the kindness and critiques, everyone! Glad that the post was received so well. Thanks again to all who contributed and helped make the post come together. Also, loving the added advice.

  29. 40


  30. 41

    Nice article. TFS. I am going to post the same on my blog with credits to your site.

    I am really impressed with “A Few More Words Of Wisdom” section.

    Thanks Robert once again.


↑ Back to top