There’s epic amounts of stuff that I’ve not touched. People will say to me, “What do you think about this?” “I don’t really have an opinion. I’ll let you know once I have a chance to look at it.” I think coming from where I’ve come from, I’ve got the confidence to say that. If you’re in that place where you’re feeling terrified that the world is racing past you, if a client says, “Why aren’t you using this?” or “I’ve heard that you need to use that.” What do you say? You don’t come from a place of being very confident about it. Because you’re not sure yourself if you’re doing the right thing. – from my conversation on The Web Ahead
Last week I had a chat with Jen Simmons for her podcast The Web Ahead, the episode was published today. We talked about the “everyday developer”. The person who builds sites for clients, perhaps works alone or with a small team. The person who isn’t usually found on stage at a web conference or featured in industry magazines.
Due to supporting users of Perch, our product very much aimed at people who build great sites for clients, I know a lot about the things that a whole range of designers and developers struggle with. We’re being asked to implement things in our product to help them, or we just hear about them when discussing things in support or face to face.
A lot of folk feel overwhelmed right now. Things seem to be changing so quickly. It doesn’t seem enough to be a good designer, or to know HTML and CSS well. Do we need to learn all of those frameworks? Are we “doing it wrong” if we don’t adopt that methodology and toolkit we were told is the way to do things by that big name speaker at the conference we attended?
I don’t think I had really voiced this thought before, however in the conversation I kept coming back to the word confidence.
I’m not the smartest person in the room. I don’t have any qualifications to do what I do. Yet I have confidence to be able to assert my opinions, and also to be happy to say when I don’t have an answer. If you ask me about a technology I’ve not used, I’ll tell you it’s something I’ve not used. I won’t feel bad about that, or as if I’m a lesser developer due to not having used a certain tool.
Where does confidence in your ability come from?
Learn your core skills well. Understand HTML and CSS, be able to build a layout without leaning on a framework. Get a solid understanding of how a website actually gets from the server to a browser, an understanding of security and accessibility. These are the basics, the constants. These things change slowly. These things sit underneath all the complexity and the tooling, the CMSs and the noise of thousands of people all trying to make their mark on this industry.
With solid core skills you have a basis to assess the things you are being told. You can build a website. You don’t need some tool to build a website, if you are going to adopt something, it has to do something helpful for you or your clients. Filter the advice, check whether the speaker so passionate about a certain technique, works on projects like yours. Read widely, but don’t feel you have to know everything. Follow people on Twitter who seem to be the known expert in a subject area, they will do a lot of filtering for you. Put time aside, even a little, for learning and pick those things that interest you, or where you feel you could make a big difference to your own workflow.
As you are doing this don’t forget to share what you know. I have confidence in what I know, and much of that has come from teaching other people. As I fill in the gaps in my knowledge to write an article, I learn. When someone with more or different experience leaves a comment, or shares their point of view with me, I learn. And perhaps much of my confidence and lack of fear of this fast-changing web is because I know I can learn. Whatever the next thing is, I’ve got the ability to learn about it. If it’s relevant and when I need it, I’ll learn about it. You can too.