Coding comes into many aspects of our day to day lives. Some of the things that rely on code in order to work are showers, cars and mobile phones; all of which many of us take for granted.
As many of you know, my fiance Jacob is a web developer and without him my blog would not be as it is today! So for coding week 2019, I decided to interview him about what it is like to create websites for clients and work with code.
Q1. How much time and effort goes into making a single website?
This depends on the type of website that we have been asked to make. For example, a website could have multiple features and purposes with external links, sign up forms, contact forms, multiple pages and so on, these would take more time to make in comparison to a website that is designed to simply showcase some of the clients work.
Q2. What is it like to create websites for clients and working with code in order to achieve their desired features?
It is good to see people’s ideas come to life and how happy they are when they see the completed project. Although, sometimes it can be frustrating as some features take longer than others in order to be perfected and the smallest of mistakes within the code, even just a punctuation mark being in the wrong place, can cause the entire website not to function correctly.
The project managers also play an important role as communication is key. Before any code can be written, project managers will communicate with the clients to ensure their project is well planned out and so they can create a plan for the developers and designers to follow. If a project is well planned out, then there will be less chance of the project exceeding the deadline and going out of scope. This means that there is less chance of the client asking to change aspects of the project that were not in the original plans as this can lead to their budget being altered as well as the timeline that was initially put into place.
Q3. How many people does it take to design, create and publish a website?
A website can be designed, created and published by one singular person, however, this could be very time-consuming. In my current place of work, we have a team who split the project into multiple sections. We have designers who create blueprints of the client’s ideas, often using programs such as Photoshop, which they will pass on to the front-end developers.
Front-end developers use code to create everything that you see on your screens (the layout, writing and colours for example). Then we have back-end developers (this is my position in the team), they work on the important things that you cannot see, such as linking the website to a database (such as sign up forms which require the user to enter an email address and password; ensuring that their data is sent to a database and that it is stored and protected correctly), they may also use code to ensure any buttons or external links take you to the place that you need to be. Then we have quality assurance testers who test the project thoroughly before it is published to the public. And of course the project managers who communicate with the clients to ensure that their ideas are doable and that they are 100% happy with the plans that are put into place; they then continuously communicate with each team member to make sure that they know what they need to aim for and set individual deadlines to keep the project flowing.
Q4. Are there any aspects of the job that you find difficult or frustrating?
Some tasks are harder than others and if you were to encounter a bug and the system was unable to pinpoint any errors within the code, it could take hours or even days to find the mistake and correct it, which can be very frustrating. But overall it is an enjoyable job to have and I enjoy watching peoples projects being built up from scratch and coming together piece by piece.