Business experience: Web application developer

Elizaveta Naletova shares her experience in the profession about virtual Lego for adults and other aspects of working as a web developer.

Photo by olia danilevich/pexels

Follow us on Facebook, Telegram, Twitter, Instagramso you don't miss anything interesting!

– Lisa, what exactly does a web application developer do? What are their responsibilities?

– As with any other IT profession, the list of responsibilities is quite long – from design and creation of web applications to troubleshooting, resolving issues that arise during the initial stages of use, and ongoing updates to the application. Of course, all of these are general responsibilities, and, as practice shows, this list will vary depending on the project. For example, in large projects, a single person is responsible for the design, while several developers may be involved in the actual creation of the application. There are also "universal" – or full-stack – developers who independently complete the entire work from start to finish.

– In simple terms, what is a web application?

A web application is a program that displays and transmits information using a browser. If you've sent emails, ordered pizza online, or even used Google Docs, you've encountered web applications. While websites typically contain completely static content—text, images, and video—web applications allow users to interact with the page. Information is transmitted from the user to the application, and the page content is updated accordingly. For example, if you search for "weather forecast" in Google, you'll see a web application with the forecast right on the homepage.

How did you come to this specialty? What initially interested you?

I graduated with a degree in international relations, so I didn't get into IT right away. Initially, I had no specific interest in web development—and, frankly, no understanding of what a "web application" was. I'd been interested in IT as a holistic field for a while, and I decided to give it a try. Like many in IT, I started by learning very basic programming languages ​​like HTML, CSS, and JavaScript, then explored various frameworks, while simultaneously creating my own educational projects. Even at this stage, I was very interested in the field, so I started investing more time in learning. For the past six months, I've been working exclusively on web applications and related projects. But I don't plan to limit myself to just this; I want to develop in related fields.

– Having experience in this industry, what aspect of the job do you find most appealing?

"For me, the presence of creative solutions and the space to make them are crucial in any job. And even though IT is a technical field, working in it gives me the freedom I need. I like to call this "systemic creativity"—any code has a list of rules, a so-called system, that must be followed, but from these rules you can build and create anything your heart desires. A kind of virtual Lego for adults."

– How to become a web application developer?

"The simplest answer would probably be to get a relevant higher education, but I don't have that experience, so I won't talk about that. For me, the process started with watching YouTube videos and learning the basics of programming through free video courses. Then came more in-depth courses, numerous practical training projects, and hours of reading forums and documentation to figure out some very specific problem that was arising."

However, as practice shows, the problem most often turns out to be not so specific.

– Freelancing or working for a company?

"I've had experience with both, but I can only say that it's different for everyone. I prefer working for a company, because finding clients is far from my favorite part of the job. Of course, working for a company offers less freedom than freelancing, and that's worth considering. If you're unsure, try both options and choose the one that suits you best."

– What is your workday like? How long does it last?

– It depends on my workload. The company I work for has a “flexible schedule, but the work must be completed on time” approach. This approach has become increasingly popular lately, and I'm very happy about it. There are days when I only have to work a few hours, and I manage to finish everything I need to before lunch. Other times, I'm stuck at the computer for 10 hours – a flexible schedule doesn't negate the freedom to code all night. But of course, you shouldn't do that – in most cases, proper time management and self-assessment are enough to avoid working overtime.

– You said you had some freelance experience. How did you find job offers at that time?

– Usually on Upwork. I don't see the point in reinventing the wheel when there are well-known sites with a large number of both specialists and – conveniently – clients.

Plus, on this site you can work with clients from different countries. This adds variety.

– Knowledge of English is essential for working with international clients. How necessary is it if you only accept orders from Ukrainian companies?

– Knowledge of English is practically mandatory for the IT field. As a freelancer, you can still get around it, although it will only hurt you. And during a company interview, this part of your biography will significantly reduce your chances of getting through. English influences not only the quality of communication and your client base, but also the overall routine work.

– What personal qualities are important in your business?

"Firstly, as I've already mentioned, the ability to manage your time wisely and assess your abilities. At work, there's no call to end a lesson, so it's very easy to misjudge your abilities, especially at the beginning. But don't worry about it; everyone faces this. It's important to have both analytical skills—to quickly identify problems—and creativity—to solve the problem and find alternative solutions. And, of course, many other qualities that are important in almost every field of work—patience, self-discipline, self-confidence and self-confidence, as well as the ability to accept and learn from failures."

– What advice would you give to colleagues new to the profession?

"First, don't be afraid to take the first step in IT. I, too, was haunted for a long time by the fear that everything here is difficult, and that people know more and better. Believe me, this is not true. Yes, IT is competitive—but no more and no less than any other, so there will definitely be a place for you."

Secondly, don't stop learning. Even after you've become a good specialist or gained commercial experience, don't forget about developing and learning new things in your own or related fields. This will not only give you freedom and a better understanding of what you do, but will also simplify the entire project process. Even excellent specialists encounter things they don't yet know or can't do. So don't be afraid to keep learning.