Looking to try something new? Front End Development is an in-demand field within Software Development. Front End roles today require much more than just User experience design skills. There is a high level of programming required to develop intuitive interfaces. There is new frameworks and concepts which companies are introducing, making the job market increasingly more complex. In this post, we will highlight the primary skills needed as a Front End Developer in 2019.
Computer Science Knowledge
Basic CS knowledge is recommended to navigate the role. This would assume knowledge of the web, coding, networks, algorithms, and fundamental problem solving skills - these skills seem to be a baseline when developing on the Front End. This knowledge can be obtained through a college CS degree or it can be self-taught. Another popular option is learning CS through Bootcamps.
REST, or Represential State Transfer is another way of implementing a Web Service. It is the ideology of everything is a resource. Every resource is identified by a unique uniform resource indicator (URI), for example take the following two URIs,
http://mywebservice.com/Australia/ which returns a big list of all the states, cities and suburbs in Australia. And another URI
http://mywebservice.com/Australia/Queensland/, which returns a filtered version, only showing the cities and suburbs in the state of Queensland.
One more example
Another important point to note with REST is that it is stateless. This means that when you access that earthquake data linked above, it is the most current state of the resource (ie. most recent data available). You might go for a quick walk, come back and there has been an earthquake in that time. Now the data has been updated and you will no longer be able to access the previous data before you went to go for that walk.
Some Benefits of REST?
- Lightweight baby!
- Scalable - Supports large numbers of requests
- Reliable - No single point of failure
Simple Object Access Protocol. It’s a protocol specification exchanging XML a.k.a “structured information” in web services. It relies on the use of application protocols for transmission (as the message content is independent of the method of transport). Take for example, a web service provider wanted to publish a service to make a simple “note” accessible to the whole world, what would they do? Well they would transfer this note into XML format, maybe something like the below…
But this is just XML… we need to SOAP-ify it, A SOAP message consists of:
- An envelope element - this identifies the XML document as a SOAP message
- A header element - header information
- A body element - which is where the call and response information is contained
- A fault element - which is used error handling
Once they are added, the SOAP message is constructed, your service function is created eg.
getNote(), then it is ready to be published to the service repository. This is done by updating the Web Services Description Language, I like to think of it as a phone book and your updating the phone book with newly added phone numbers. Great, so now the WSDL has been updated, and the web service is now discoverable. A web service consumer can then consume the web service (ie. call
getNote() in their application) and they will receive a SOAP response back with the note they requested.
Some Benefits of SOAP?
- Platform, Language and Transport independent
- Built-in error handling
- Automation when using some products
Web server programming
Web Server programming is any programming on the server-side. A basic example of this typically involves making a HTTP request to the server, to then return some content to the user interface. Think about it as if all the action happens in the background.
Version Control (Git)
The code you will write as a Front End Developer will likely be a small part of a much broader project. Version control helps to maintain code in the project, so it does not break the entire project and other developers can continue to develop the project too. Most companies today recommend using
git as their primary version control system. For more information, you can read our post - Git is always a great start.
User Experience Design
I’m not going to tell you how to design a website, what colours you should use, how it should look. But what I will do is tell you what not to do.
The don’ts of Web Design
- Don’t use non-contrasting colours
- Don’t have your website be too busy
- Don’t have a slow website
- Don’t have random content example fitness content with on eg. a gardening blog
- Don’t stop improving
Simplicity equals speed
I will use Zero Equals False as an example, it only uses black text on a white background, and almost nothing else. Since the website is only text based – this makes the load time so much faster. It loads in under five seconds - which is also optimal for user experience.
This is an actual design principle to design for simplicity. Think about the company “Apple” and their products. Their entire brand is based on simplicity. Humans like simple, so why not go with what is - instead of reinventing the wheel.
Hope this helps! Thank you for taking the time to read this article.