Notes from: “How to become A Web Design Expert” article
Just read an article at smashingmagazine.com. The subject is: ”How to become A Web Design Expert”
What I’ve learned from this article is:
- All the experts are not very well known
- Being an expert is more then about getting people to listen
- Being perceived as an expert can be helpful when working with clients, and it does create the potential to attract better-quality work.
- To become an expert, you need time and experience
- Proficient at overcoming problems
- Without passion, you have no desire to learn new things or push boundaries.
- I believe that an almost obsessive passion for Web design is required to be a true expert.
- Experimenting and making mistakes are crucial if experts are to establish their credibility.
- I have to make mistakes, not hundreds or thousands. Billions of them.
- Success is going from failure to failure with no loss of enthusiasm. - Winston Churchill
- The definition of an expert is someone who knows what not to do. - Charles Willson
- We need to learn to face our failures
- stop insisting that you are an expert
- Not that context is everything. It’s also about what you say and how you say it.
- Have your own books, presentations, blogs and podcast about your experties
- If you want to be perceived as an expert, know yourself, be relaxed and present with confidence.
- present evidence/reference to support your positions
- Your expertise should always be about serving others
- You become an expert so that you can do a better job for your clients, provide more value to your organization and help others establish best practice in your industry
Understanding “semantic markup”
<h1>A heading at peace with itself</h1>
In short, your HTML should do everything it can to convey the meaning, or semantics of the content in the page, while steering clear of describing how it should look. Web standards geeks call HTML code that does this semantic markup.
Writing semantic markup allows your HTML files to stand on their own as meaningful documents. People who, for whatever reason, cannot read these documents by viewing them in a typical desktop web browser will be better able to make sense of them this way. Visually impaired users, for example, will be able to use assistive software like screen readers to listen to the page as it’s read aloud, and the more clearly your HTML code describes the content’s meaning, the more sense tools like these will be able to make of it.
Best of all, however, semantic markup lets you apply new styles (presentation) and interactive features (behavior) without having to make many (or, in some cases, any!) changes to your HTML code.
From SitepointÂ