I don’t do Angular, is that OK?
I’ve never been one to care for job titles. One or two words can’t adequately explain the extent of our roles. I try to avoid giving myself a strict title on this website.
On my homepage:
“I design, build & write all things web”
Then I list:
These pages are a delicate balance of an intelligent, thoughtful, and succinct description of my ‘craft’, and some SEO bingo because that’s an unfortunate reality. In my sidebar-slash-footer: “I freelance for small businesses, start-ups, individuals, and fellow web agencies.” — i.e. pretty much anyone willing to pay me.
I try to emphasis web design first because it’s what I enjoy most. Though really, design & build are part of the same package. Figuring out clean and sometimes clever CSS for a responsive layout is a lot of fun.
All of this, and more, is what I think of when I read “Front-end Developer”.
Nowadays the definition is significantly different for others.
Sure, I’ve dabbled, and trepidations aside, I even think I might like where these frameworks are going (Jeremy Keith has recently summed up the concerns). But after some pondering it struct me, do I want to be doing this work? It’s not what I’m best at. I don’t really enjoy it.
Is that simply because I haven’t taken the time to learn this stuff to a professional level? I’ve spent a good amount of time playing with these technologies. I understand the concepts, certainly enough to consider, and doubt, whether I can realistically stretch my range of services so broadly.
I want to be content knowing there are some roles I don’t need to fulfil, regardless of job title definitions. But I can’t help feeling in limbo right now. I don’t want to limit myself either. It’s OK that I don’t do Angular, but maybe one day I will.