I am a web developer working for multiple companies and each requires a different mindset and approach to solve problems.

In my regular day-to-day activities, I am often approached by marketing or business managers if the sales are down for the day to check if everything is working properly on the technical side. In the majority of cases, the issue is usually not on the technical side of things.

Other than checking if everything is working properly, the next thing I usually deal with is planning tasks to implement new features or automation. I will usually get on a call with business or project managers to come up with the best solution for automating various tasks that our employees have to do manually right now. Things such as following up with customers, processing refunds, and so on.

I really enjoy doing these automations because you can directly calculate how much time and money you save by implementing these smart solutions.

The worst part about being a web developer is that people always expect things to be done faster and easier. Most people don’t understand that even adding a small feature could take a lot longer because we always have to test to make sure it works properly and that it doesn’t break anything else.

It’s even worse when people expect you to change something in high-risk areas such as the shopping cart page or checkout page quickly and without testing. Of course, if you did that and it broke something major, you would probably be the one to blame. That’s why it’s super important not to give in to pressure to expeditiously deploy new code without sufficient testing.

Some days it’s pretty mellow and everything is working exactly as planned, other days are hectic and everything is seemingly falling apart before your eyes. As a web developer, there are always things to do: create, fix, or diagnose. Perhaps the worst part is that you might need to work at any given hour if you’re on call and things go wrong. And let’s be honest, things always go wrong when you’re on call and everything runs perfectly all the other times.

Senior QA Software Engineer – Hannah Quinn

Flowlens

I work as a QA Software Engineer but I also cover some of the support that comes in so it’s important that I ensure that all our customers are happy. … Read More

Web Developer – Sue Malomo

Happy Cog

Each morning I look at the tickets that are assigned to me to determine what I’ll be working on for that day. Home workspace During our daily Dev Stan … Read More

Senior Software Engineer – Vadim Atamanenko

My main job as a Senior Software Engineer is as follows: Discussion of new ideas and plans with Product / Project managers Discussion of the success o … Read More