I know enough web design and development to land clients and get paid. But client work has stunted my growth.
Over the next eight weeks, I want to significantly beef up my best practices and arsenal of skills, specific to front-end development and UI design.
Here are things I know well enough to teach them:
Please point me in a direction that will mature my ability to create efficient, fast code and mockup UI designs more effectively. I am open to new schools of thought, technologies, best practices, etc.
All I’d like to clarify is that I’d prefer to focus on learning skills that are already proven in a real-world production environment vs. early-adopted methods and technologies.
I hope this helps some of you out there as well. Thanks in advance.
For anyone interested, I found a great article that covers this question here: //rmurphey.com/blog/2012/04/12/a-baseline-for-front-end-developers/
I would check out //www.codecademy.com/. Their courses will by no means make you an expert in anything but it will give you a solid foundation to build on. If nothing else, you will know more about a language and what it’s good for.
Plus… it’s FREE!
I know you said you want to focus on “front end” but I think at least a working knowledge of PHP is a good thing. It will allow you to more effectively leverage what you already know.
> For anyone interested, I found a great article that covers this question here: //rmurphey.com/blog/2012/04/12/a-baseline-for-front-end-developers/
I think this article is a bit intimidating. There is a lot to master there. However, I think it does a good job in pointing people in the right direction.
I am a proponent of the command line/terminal/shell. If you are interested in learning that, here are some great resources:
When I was in high school I was working as a gas station/convenience store attendant. And every single shift I used to take (steal) one soft drink out of the cooler. My boss knew about it and never said anything ever. Why?
Because all the other things I was doing right–that made him money, he could care less for 5 drinks he lost per week. Now if you apply same logic to web awesomeness. Why do you think they’re hiring you? To give you money? No! To make money on YOU. It’s that simple. So whenever I’m interviewing I’ll ask about the specific issues they’re facing and explain how I would solve these issues. And you always want to present the information with thinking of “How will I make money for this company”, because essentially that’s what they care about.
All in all, I totally disagree with the article linked. Our industry in fragmented enough that you don’t need to know all those things to have a decent paying job. The baseline is whatever the employers requirements are. You don’t necessarily have to be expert in each area, however you should strive to have working knowledge in things that are required when working within a team. For example, you might not need to know all Git commands, learn only the necessary ones to make a commit, if you need to do something more advanced like merge a branch or rollback changes, someone can help within your team, and by working like this, you gain the knowledge over time.
I hate articles like that, because it takes years of experience to master any sort of skill. Article sound like, “hey look at me I know all these things and if you don’t get the fuck out”. No wonder it’s intimidating.
You must be logged in to reply to this topic.